Decision room · SAP SD
Trace one customer order when the vendor ships directly and sales, purchasing and billing documents must remain aligned.
Start with the business or technical outcome
Third-party sales removes the company’s physical delivery step but increases the importance of SD–MM document integration. A confident choice requires more than a feature list: it requires constraints, evidence and a clear trade-off. A customer orders a specialised item that the company does not stock, so an external vendor fulfils it directly to the customer.
Use fictional parties and a training client. Exact billing relevance and goods-receipt or invoice-receipt design can differ by configuration. Document what your scenario uses rather than mixing variants.
The commercial company still owns the customer promise, pricing and billing even when the supplier performs physical delivery. Status visibility and vendor confirmation are therefore essential.
What to understand before opening the tool
Understand sales item category, schedule-line behavior, automatic purchase requisition, purchase order conversion, vendor and ship-to data, confirmation, invoice verification and customer billing relevance. Trace reference numbers across SD and MM.
A missing requisition may begin in material or item-category determination. A billing block may reflect missing supplier evidence or status rather than an SD pricing error.
Sales Order
Use it for: capture customer requirement, price and third-party item Keep as evidence: order and item-status evidence
Purchase Requisition
Use it for: hand demand from SD to purchasing automatically Keep as evidence: requisition account assignment and reference
Purchase Order
Use it for: commit supplier, delivery address and terms Keep as evidence: PO linked to sales item
Document Flow and Status
Use it for: connect sales, purchasing, invoice and billing milestones Keep as evidence: end-to-end trace
Use an end-to-end third-party document flow, partner and item-category checks, purchasing hand-off, billing trigger evidence and exception map as the decision test. Define the constraints before comparing options, then explain which factor carried the most weight. A sound recommendation can be conditional: one option may fit a small learning environment while another suits a regulated or high-volume workload.
Work through the decision sequence
Follow both relationships: supplier fulfilment and customer revenue, checking the integration reference at each hand-off.
- Prepare the scenarioValidate customer, vendor, material, pricing and third-party determination prerequisites.Checkpoint: Master and configuration checklist.
- Create the sales orderEnter the item and confirm third-party category, schedule line and procurement proposal.Checkpoint: Order plus generated requisition.
- Convert purchasing demandCreate the vendor PO with correct customer delivery address and references.Checkpoint: PO linked to requisition and sales order.
- Record supplier milestoneCapture confirmation, receipt or invoice evidence according to the configured variant.Checkpoint: Supplier-side document and status.
- Create customer billingVerify billing quantity and value basis, then generate the invoice only when prerequisites are met.Checkpoint: Billing document linked to order.
- Reconcile margin and exceptionsCompare customer revenue, vendor cost, quantities, cancellations and open statuses.Checkpoint: Order profitability and exception report.
Avoid scoring every criterion equally. Security, correctness and recoverability may be non-negotiable; convenience and speed can then be evaluated inside those boundaries.
Options worth comparing before you act
Status across SD and MM reveals which team owns the next action.
| Decision or signal | Action to take | Evidence to retain |
|---|---|---|
| No purchase requisition | Check item and schedule-line determination plus material data | Sales item status and configuration trace |
| Wrong ship-to on PO | Review partner transfer and purchasing address | Customer and PO partner data |
| Supplier delivery delayed | Update confirmation and customer communication | Confirmed date and status note |
| Customer billing blocked | Inspect configured billing relevance and required supplier milestone | Document flow and status |
| Quantity differs | Align supplier evidence, customer billing basis and approvals | Quantity reconciliation |
Trade-offs hidden by a quick answer
Because stock never enters the normal warehouse flow, weak status control can hide delays or margin errors.
- Using a normal stock item category: Third-party determination must match the business scenario.
- Losing the sales-order reference in purchasing: Traceability and account assignment depend on linked documents.
- Billing before required evidence: Follow the configured and approved trigger.
- Ignoring vendor cost changes: Compare purchase and sales values before claiming margin.
- Closing only the customer invoice: Open requisitions, POs or supplier invoices can remain.
Turn the exercise into credible portfolio evidence
Create one third-party order with a clean flow and one delayed supplier confirmation. Draw the customer-company-vendor relationship beside the SAP document chain.
Add a margin reconciliation and responsibility table showing what sales, purchasing and finance must verify. Use fictional prices and partners.
Explain it clearly in an interview
Trace the automatic requisition from the sales item, explain the purchasing conversion, identify the customer billing trigger and show where you investigate an open status.
Peer review before calling the work complete
Ask another learner to inspect the result without watching you build it. Give them the original scenario—a customer orders a specialised item that the company does not stock, so an external vendor fulfils it directly to the customer.—and the evidence pack, but not your intended conclusion. They should be able to trace the input, identify the main decision and locate the proof of the output. If they cannot, improve the labels, timestamps or explanation instead of adding decorative screenshots.
Use this acceptance condition during the review: Sales and purchasing documents share traceable references, the delivery address and quantities agree, billing follows the configured milestone and all open statuses are explained. Record one question the reviewer raised and the change you made in response. That small feedback loop makes the SAP SD third-party sales process exercise more credible, easier to maintain and easier to explain under interview questioning.
Questions learners ask
Does the company deliver goods in third-party sales?
The external supplier typically ships directly to the customer in the standard scenario, while the company manages sales and billing.
Why is a purchase requisition created?
It transfers the procurement requirement from the sales item into the purchasing process.
When is the customer billed?
That depends on configured billing relevance and the chosen process milestone; verify the landscape.
How does SD integrate with MM here?
The sales order creates purchasing demand and linked procurement documents provide fulfilment and cost context.
Use current product guidance
Menus, fields, permissions and service behavior can change between product versions or tenant configurations. Check the SAP Help Portal before applying version-sensitive steps in a live environment.
Build the complete skill path
Practise SAP SD master data, pricing, order management, delivery, billing, credit and integration through complete order-to-cash scenarios.
Final perspective
The real value of SAP SD third-party sales process is the ability to complete a controlled task and defend the result with evidence. A learner who can show the input, explain the decision, verify the output and describe one realistic exception demonstrates far more than someone who has only memorised a menu path or definition.