SAP's sales and distribution module — quotation to delivery to invoice, and the pricing engine behind it.
SAP SD (Sales and Distribution) handles the customer-facing flow: enquiry, quotation, sales order, delivery, billing. It owns pricing determination, availability check, credit management against the customer, and the output that produces order confirmations and invoices. The pricing procedure is where most of its complexity concentrates.
SD is where customer promises are made, which is why availability check and credit management sit in it rather than elsewhere. It is also where pricing logic lives, and pricing is almost always more complicated than anyone admits at the start — customer-specific prices, volume breaks, freight conditions and surcharges all have to resolve to one number at order entry.
Enquiry, quotation, standard order, returns, credit memo request. Each has its own flow and its own configuration.
A sequence of condition types — base price, discounts, surcharges, freight, tax — evaluated in order to produce the net value.
Whether stock can be committed, considering existing allocations, planned receipts and replenishment lead time.
Outbound delivery, picking, packing and goods issue, which reduces stock and posts cost of sales.
Invoice created from the delivery or the order, with output determination producing the document and sending it.
A business accumulates 47 condition types in its pricing procedure over a decade. Each was added for a good reason by someone who has since left. A customer queries an invoice and nobody can explain how the price was arrived at.
The condition technique is powerful precisely because it is layered: base price, customer discount, material discount, volume rebate, freight, surcharge, each resolved through its own access sequence. Layered thoughtfully, it models real commercial arrangements. Layered without review, it becomes a system where the output is correct according to rules nobody holds in their head.
The cost is not usually wrong prices — it is the inability to answer questions, which becomes invoice disputes, which becomes DSO. A periodic review that documents each condition type's purpose, checks which are still used, and retires the dead ones is unglamorous and pays for itself the first time a customer asks why an invoice says what it says and somebody can answer in a sentence.
| Term | What it means |
|---|---|
| Sales order | The customer commitment, carrying pricing, dates and delivery requirements. |
| Delivery | The document representing the physical dispatch, created from the order. |
| Billing document | The invoice, created from the delivery or the order. |
| Condition technique | The pricing mechanism — a sequence of condition types resolved by access sequences. |
| Availability check | Determining whether stock can be promised for the requested date. |
Condition tables exist for this. Customer-specific pricing procedures proliferate and become unmaintainable.
Checking credit once goods have left means the decision has already been made.
A check that ignores planned receipts under-promises; one that ignores allocations over-promises.
Invoices not reaching customers because output was never configured is a recurring and avoidable problem.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Condition types in use vs configured | How much of the pricing procedure is live. Dead conditions are pure confusion. | |
| Manual price overrides | Where the configured pricing does not match commercial reality. | |
| Order-to-delivery lead time | Fulfilment responsiveness, from the customer's point of view. | |
| Invoice disputes by cause | Pricing disputes are usually a condition logic problem rather than a data entry one. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.