Explain Sales & Distribution (SD): Order-to-Cash Cycle in SAP

22 / 65

Functionalbeginner

Sales & Distribution (SD): Order-to-Cash Cycle

The end-to-end process from sales order creation through delivery, billing, and payment in SAP SD.

Order-to-cash is selling something: taking the order, shipping it, invoicing it, collecting the money. It mirrors procure-to-pay from the other side.

Order-to-cash is a relay race with three legs - the sales order is the starting handoff (what and how much), the delivery is the middle leg (getting it physically out the door), and billing is the anchor leg that crosses the finish line by turning the shipment into recognized revenue and a receivable.

Key Concepts

    sales order    VA01    what the customer wants, at what price
          |
    delivery       VL01N   pick, pack, and ship it
          |
    goods issue    PGI     stock leaves; cost of sales is posted
          |
    billing        VF01    the invoice; revenue and a receivable

The sales order does more than record a request. Two things happen while it is created.

Pricing runs through the pricing procedure — a sequence of condition types producing the net value:

    base price       1000
    customer discount -50
    freight           +20
    tax               +173
    net              1143

Availability check (ATP) asks whether the quantity can be delivered on the requested date, given stock and planned receipts. If not, it proposes a date or triggers backorder handling. This is why an order can be entered and immediately show a later delivery date.

Post goods issue is the financially significant step. Not the delivery, and not the billing:

    debit   cost of goods sold
    credit  inventory

Stock physically leaves at PGI, so that is when its value leaves the balance sheet. Before PGI the delivery exists but nothing has been posted.

Billing creates the revenue and the receivable.

    debit   customer (accounts receivable)
    credit  revenue

So revenue and cost of sales are posted by two different documents at two different moments. Reconciling them is routine month-end work, and the gap between PGI and billing is exactly why.

Copy control is the mechanism nobody notices until it breaks. It configures what carries from one document to the next — which fields, which quantities, and whether a document may be created with reference at all.

"Delivery cannot be created for this order" is nearly always copy control, not the order.

Credit management sits in front of the whole flow. A customer over their credit limit has the order blocked before delivery. The order exists, and nothing may ship until somebody releases it — which is the point: the check happens before the goods leave, not after the invoice goes unpaid.

The answer that lands in an interview is the three-document flow — order, delivery, billing — with what is posted where: nothing at order, cost of sales at goods issue, revenue at billing.

What the interviewer is probing.1. "Walk through order-to-cash." Probing: end-to-end understanding. Stalls: "You take an order." Moves up: inquiry, quotation, sales order, delivery, picking, post goods issue, billing, payment — with availability check and pricing along the way.

2. "What happens at post goods issue?" Probing: the integration point. Stalls: "Stock leaves." Moves up: stock is reduced and cost of goods sold posted, so this is the point revenue recognition becomes possible.

3. "What is the role of the item category?" Probing: the configuration lever. Stalls: "Nothing." Moves up: it controls whether an item is relevant for delivery, billing and pricing, which is how free goods and text items behave differently.

4. "Why would a delivery not be created?" Probing: troubleshooting. Stalls: "A bug." *Moves up:* an incomplete order, a credit block, no available stock on the requested date, or a delivery block on the customer or order.