Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

What is SAP SD?

SAP's sales and distribution module — quotation to delivery to invoice, and the pricing engine behind it.

In short

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.

Why It Matters

Why this matters in practice

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.

Runs order to cash through to billing
Pricing procedure resolves conditions into the final price
Availability check decides what can be promised and when
Credit management blocks before commitment, not after
How It Works

How it works in practice

Sales document types

Enquiry, quotation, standard order, returns, credit memo request. Each has its own flow and its own configuration.

Pricing procedure

A sequence of condition types — base price, discounts, surcharges, freight, tax — evaluated in order to produce the net value.

Availability check and ATP

Whether stock can be committed, considering existing allocations, planned receipts and replenishment lead time.

Delivery and picking

Outbound delivery, picking, packing and goods issue, which reduces stock and posts cost of sales.

Billing and output

Invoice created from the delivery or the order, with output determination producing the document and sending it.

Worked example

A worked example: a pricing procedure nobody could read

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Pricing built as a special case per customer

Condition tables exist for this. Customer-specific pricing procedures proliferate and become unmaintainable.

Credit check after delivery

Checking credit once goods have left means the decision has already been made.

Availability check not configured to the business

A check that ignores planned receipts under-promises; one that ignores allocations over-promises.

Output determination left to defaults

Invoices not reaching customers because output was never configured is a recurring and avoidable problem.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

An ordered list of condition types that SAP evaluates to arrive at the final price. It determines which discounts apply, in what sequence, and what is calculated on what base.
SD sells and MM buys. They meet at inventory: SD's goods issue reduces the stock MM's goods receipt increased, and both post through the same valuation configuration.
It compares requested quantity and date against stock, planned receipts and existing commitments, according to a configured scope that decides what counts as available. The configuration matters enormously: including planned orders in the scope will promise stock that does not yet exist, while excluding goods in transit will refuse orders you could actually fulfil. Both errors are common and both come from the scope being set once and never revisited.
Delivery-based billing invoices what actually shipped, so what you billed and what left the building cannot diverge — this is the right default for physical goods. Order-based billing invoices what was ordered, which suits services, licences and anything without a physical delivery. Using order-based billing for goods means part deliveries create billing problems immediately.
Through a return order referencing the original sale, then a return delivery bringing goods back into stock, then a credit memo. Keeping the reference to the original document is what makes the credit traceable and what lets you analyse return reasons properly. Processing credits as standalone documents without reference is faster at the time and makes return analysis impossible afterwards.
Yes, and it is a standard requirement. The condition technique resolves prices through access sequences that can consider customer, sales organisation, distribution channel, material group and more, so channel-specific pricing is configuration rather than customisation. The discipline worth applying is to model channels as distribution channels rather than as separate customer records, otherwise reporting by channel becomes manual.
Related

Where to read next

What is order to cash?

Read more

What is SAP MM?

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.