SAP ConsultingLogistics
SAP SD - Sales & Distribution
SAP SD runs the path from customer inquiry to quotation, sales order, delivery and invoice. Pricing, availability and credit checks fire on the sales order; goods issue reduces stock and billing posts the receivable and the revenue.
Part of these processes
Process
Order-to-cash in SAP SD
Each document is copied from the one before, so price, quantity and dates carry through the chain and show up in the document flow.
- 01QuotationVA21 · F1852
Priced with a validity date
- 02Sales orderVA01 · F1873
Price, ATP and credit checks
- 03Outbound deliveryVL01N · F0869A
Shipping point and route
- 04Picking and packingVL02N · F0868
Or EWM warehouse tasks
- 05Goods issueVL06G · movement 601
Triggers the e-Dispatch Note
- 06BillingVF04 · F0798
e-Invoice or e-Archive
Layers
Pricing with the condition technique
Every price, discount and freight charge on an order is found the same way: procedure, condition type, access sequence, record.
- 01
Pricing procedure
- Set by sales area
- Customer and document keys
- Sequence of conditions
- 02
Condition type
- Price, discount, freight
- Calculation and scale type
- Access sequence assigned
- 03
Access sequence
- Specific to general search
- Customer + material first
- Material alone last
- 04
Condition record
- Amount with validity dates
- Scale lines possible
- Maintained with VK11
- 05
Pricing result
- Condition lines per item
- Stored in PRCD_ELEMENTS
- May be copied to billing
Scope
What we build in SAP SD projects
Sales areas and document setup
Sales organizations, distribution channels and divisions; sales document types, item categories and copy control.
Pricing with condition technique
Pricing procedures, condition types, access sequences, condition tables and records in VK11 or F4111.
Availability check
Dates from stock and planned receipts; aATP adds product allocation, backorder processing and release for delivery.
Credit management
Limits, risk classes and check rules per business partner in SAP Credit Management, set up together with finance.
Shipping and billing
Shipping point and route determination, collective goods issue, billing due lists and revenue account determination.
Returns and special sales flows
Customer returns, intercompany sales and billing, and third-party orders that create purchase requisitions.
Current state
SAP SD under S/4HANA: the differences
- Credit management moved from FI-AR-CR to SAP Credit Management (FIN-FSCM-CR): the credit profile lives in UKM_BP, blocked documents in UKM_MY_DCDS, one risk class per business partner.
- SD rebates are gone and no new rebate agreement can be created. Rebates now run as condition contracts in Settlement Management; old agreements are closed with a final settlement.
- The VBUK and VBUP status tables were folded into the document tables, and pricing results moved from KONV to PRCD_ELEMENTS. Customers are maintained as Business Partners.
- NAST and the new output control coexist, with NAST as the billing default. On-premise, the LE-TRA shipment document can be used until the end of 2030; the target is SAP TM.
Localization
Turkish e-documents in sales
e-Invoice or e-Archive at billing
If the buyer is a registered e-Invoice user, the invoice goes out as an e-Invoice; otherwise as an e-Archive or paper invoice. SAP DRC refreshes the user list by report.
E-Invoicee-Dispatch Note at goods issue
An e-İrsaliye (e-Dispatch Note) follows goods issue, not billing, and reaches GİB before the truck leaves. The dispatch note number is mandatory on the invoice.
E-Dispatch NoteExport invoices
Export invoices under Article 11 of the Turkish VAT Law have been issued as e-Invoices by registered taxpayers since 1 July 2017.
Import and Export Package
From the field
What we see on SAP SD projects
- The pricing procedure has grown out of hand. Condition types get added and never retired, and manual price changes become routine. We take a condition inventory, switch off unused ones and limit manual changes by authorization.
- Credit data does not migrate by itself. In FI-AR-CR risk was kept per customer and credit control area; in S/4HANA it collapses into one risk class per business partner. Migrate with the tools SAP provides in the IMG, together with finance.
- Open rebate agreements go unplanned. No new rebate agreements can be created in S/4HANA; existing ones run to the end of their validity and close with a final settlement. We plan each closing before conversion and set up the next period as condition contracts.
- Some documents print from NAST, others BRF+. When the output framework varies by document, nobody is sure which channel triggers the e-document. Make one decision per document type and write it down.
FAQ
SAP SD questions we hear often
What is SAP SD?
SAP SD is the SAP logistics module for the sales cycle, from quotation and order to shipping and billing. On the order, the condition technique finds the price, the availability check gives a date and credit exposure is checked; the invoice posts to accounting automatically.
How does credit checking work in S/4HANA?
Credit limit, risk class and check rule are kept on the business partner's credit profile (UKM_BP). If the limit is exceeded, the order or delivery is blocked and a documented credit decision is created; a credit analyst approves or rejects it in Manage Documented Credit Decisions (F5587A) or UKM_MY_DCDS.
How are customer rebates handled in S/4HANA?
Through condition contracts in Settlement Management; Manage Condition Contracts - Sales Rebates (F6739) covers sales rebates. Classic SD rebate agreements cannot be created in S/4HANA, and existing ones are closed with a final settlement.
When is the e-Dispatch Note created in SAP SD?
At goods issue for the outbound delivery, and it must be sent to GİB before the goods physically leave; the actual shipment date with hour and minute is mandatory. e-Invoices and e-Archive invoices come from the billing document. A sales order on its own never triggers an e-document.
What is the difference between aATP and classic ATP?
Classic ATP gives a date based on stock and planned receipts. aATP adds product allocation, backorder processing (BOP), alternative-based confirmation across plants or materials, and release for delivery. Functions switched on with "Use Advanced ATP Functions" are not part of the S/4HANA Enterprise license.
Can we still use shipment documents (VT01N) in S/4HANA?
Yes, for now, but it is not the target architecture: under an on-premise license LE-TRA is one of three exceptions whose usage rights run to the end of 2030. The target is SAP TM; SAP plans no standard migration tool, so the move needs its own project. Routes stay in permanent scope.
Sources12 sourcesSAP Help Portal, SAP Learning, SAP Fiori Apps Library +2
SAP Help Portal
- Simplification List for SAP S/4HANA 2022 - Initial Shipment, Feature Pack Stack 1 & 2 help.sap.com (opens in a new tab)
- Example of Pricing Process help.sap.com (opens in a new tab)
- Pricing and Conditions help.sap.com (opens in a new tab)
- Copying Control (Billing) help.sap.com (opens in a new tab)
- Advanced Available-to-Promise Functions help.sap.com (opens in a new tab)
- Credit Block Release and Recheck help.sap.com (opens in a new tab)
- Retrieval of eInvoice User List (Turkey) help.sap.com (opens in a new tab)
- Customizing: Outgoing Delivery Notes (Turkey) help.sap.com (opens in a new tab)
SAP Learning
SAP Fiori Apps Library
SAP
GİB
Sources checked as of October 2026.
SAP Consulting
Review your sales flow with an SAP SD consultant
Pricing, credit or e-documents: we start with whichever is causing trouble.