Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 36 ยท Logistics: MM/SD

Order-to-Cash in SAP SD

Understand the SAP Sales and Distribution cycle: inquiry, sales order, delivery, goods issue, billing and payment, with tcodes, document types and the document flow.

If procure-to-pay is how a company buys, order-to-cash (O2C) is how it sells. In SAP the Sales and Distribution (SD) module runs the process from the first customer inquiry to the moment the money arrives. It is closely tied to Materials Management (stock is issued when you ship) and Finance (revenue and receivables are posted when you bill), so a single sale touches three modules.

This lesson covers the standard cycle, key documents and codes, and the document flow that links everything. SAP itself cannot run on this site, so the code is a labelled JavaScript stand-in.

The cycle

flowchart LR
  A["Inquiry<br/>VA11"] --> B["Quotation<br/>VA21"]
  B --> C["Sales order<br/>VA01"]
  C --> D["Delivery<br/>VL01N"]
  D --> E["Goods issue<br/>movement 601"]
  E --> F["Billing<br/>VF01"]
  F --> G["Incoming payment<br/>F-28"]

Pre-sales documents (inquiry and quotation) are optional. The sales order, the delivery and the billing document are the core.

Sales organization structure

Before any order, SAP needs to know who sells what to whom:

  • Sales organization: the legal unit responsible for selling.
  • Distribution channel: how the goods reach the customer (wholesale, retail, online).
  • Division: a product line.

These three together form a sales area. A customer must be extended to a sales area (customer master, XD01 in ECC, or business partner BP in S/4HANA) before you can sell to them. Add the shipping point and plant, and you have the organizational picture of a sale.

The documents

Sales order (VA01). The order captures customer, material, quantity, requested date and pricing. It has an order type such as OR (standard order). Items have an item category (for example TAN for a standard item). SAP checks availability (ATP, available to promise) and splits quantities into schedule lines when stock arrives later. Header data is in VBAK, items in VBAP, schedule lines in VBEP.

Delivery (VL01N). The delivery tells the warehouse what to pick, pack and ship. Header LIKP, items LIPS. Steps: picking, packing, then post goods issue (PGI). PGI reduces stock (movement type 601) and posts the cost of goods sold: debit COGS, credit inventory.

Billing (VF01). The billing document (VBRK, VBRP; type F2 for an invoice) creates the customer invoice and posts the revenue: debit customer receivable (accounts receivable), credit revenue and tax. Because the SD billing document automatically creates an FI document, SD and FI never drift apart.

Payment. The customer pays, and Finance clears the open receivable against the bank posting (F-28, or automatically through bank statements).

Document flow

Every document stores which document it follows. In the order screen, Environment > Document flow lists the whole chain: order, delivery, goods issue, billing, accounting document. Technically this chain lives in table VBFA (sales document flow). It is how a billing clerk can start from an invoice number and find the original order.

JS Stand-in: document flow like table VBFA

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Copy control

When you create a delivery from an order, SAP copies data between documents. The rules for which fields are copied, and whether a quantity may be exceeded, are copy control, configured per source and target document type. A well-known consequence: if copy control does not allow it, you cannot bill more than you delivered.

Blocks and checks

Orders can be stopped by:

  • Credit checks: the customer's open items plus the new order exceed the credit limit (credit management is in Finance, FSCM).
  • Delivery blocks and billing blocks: set manually or automatically, for example for price checks.
  • Incompleteness: missing mandatory data, which the incompletion log reports.

A quick overview of the status of each sales document is in table VBUK/VBUP in ECC (status data is merged into VBAK/VBAP in S/4HANA).

Returns, credit and debit memos

Not every sale ends happily. A returns order (RE) takes goods back and leads to a credit memo (G2) that reduces the customer's receivable. A debit memo (L2) charges extra. A free-of-charge delivery ships goods without billing.

JS Stand-in: the accounting of one sale

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The most important piece of the order, its price, is built by a rule engine you meet in The Pricing Condition Technique.

Common mistakes

  • Selling to a customer that is not extended to the sales area.
  • Posting goods issue before picking is confirmed, which gives stock errors.
  • Treating billing as optional: no billing document means no revenue in FI.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which three organizational units form a sales area?

    A sales area combines sales organization, distribution channel and division.
  2. 2. What does post goods issue do in the standard flow?

    PGI uses movement type 601, lowers inventory and debits COGS.
  3. 3. Which table stores the sales document flow?

    VBFA links preceding and following sales documents.
  4. 4. Which tcode creates a billing document?

    VF01 creates billing documents. VA01 is the sales order, VL01N the delivery and MIRO is vendor invoice entry.

Summary

  • O2C runs inquiry, quotation, order, delivery, goods issue, billing and payment.
  • A sales area is sales organization + distribution channel + division.
  • Goods issue posts COGS; billing posts revenue and receivable.
  • The document flow (VBFA) links every document to its predecessor.
  • Copy control, credit checks and blocks govern what may move to the next step.

Next: The Pricing Condition Technique