SAP SD Order-to-Cash: Complete Process Guide
For SAP S/4HANA & ECC · Updated for 2026
Order-to-Cash (OTC) is the backbone of SAP SD — every sales transaction, from a customer inquiry to the money arriving in the bank, flows through this cycle. Understanding each step, the T-codes involved, the documents created, and where FI and CO integrations happen is the foundation of every SAP SD career.
This guide walks through all 6 steps of the OTC cycle with T-codes, document flow, troubleshooting tips, and S/4HANA-specific changes — written for both interview preparation and real project reference.
The OTC Cycle at a Glance
Step 1 — Pre-Sales Activities
Before a sales order is created, customers often request information or formal offers. SAP supports this with two pre-sales document types:
A non-binding customer request for information — price, availability, delivery lead time. Does not affect inventory or accounting.
A legally binding offer with price, quantity, and validity period. Typically created with reference to an Inquiry. Expires on the validity date.
Both feed the Sales Information System (SIS) for pipeline and conversion reporting — useful for sales managers forecasting future revenue.
Step 2 — Sales Order Creation
The Sales Order is the customer's formal commitment to buy. Transaction VA01 creates a sales order — typically with reference to a quotation, but can also be created standalone.
Key events triggered when a sales order is saved:
- • Pricing determination — the configured pricing procedure calculates base price, discounts, taxes, freight
- • Partner determination — Sold-to, Ship-to, Bill-to, and Payer partners are resolved
- • Availability check (ATP) — confirmed quantity and delivery date set on schedule lines
- • Transfer of Requirements — demand flows to MRP for production/procurement planning
- • Credit check — if applicable, blocks the order if customer exceeds limit
Key table: VBAK (header) and VBAP (items).
Step 3 — Availability Check (ATP) & Transfer of Requirements
The Availability Check (ATP — Available-to-Promise) runs automatically when a sales order is saved. It verifies whether the requested quantity can be confirmed for the requested delivery date by considering:
- • Current stock (unrestricted-use)
- • Incoming supply (purchase orders, production orders, planned orders)
- • Existing demand (other sales orders, reservations)
Configuration: Checking Group (material master) + Checking Rule (transaction-specific) + Scope of Check (OVZ2). In S/4HANA, Advanced ATP (aATP) replaces classic ATP with much richer features — back-order processing, alternative-based confirmation, product allocation, and more.
Transfer of Requirements (TOR) sends the confirmed quantity to MRP as an independent requirement, enabling production planners to see customer demand in the next planning run.
Step 4 — Delivery Creation & Picking
Once stock is available, the warehouse creates an outbound delivery via VL01N (or en masse via VL10A/VL10C for the delivery due list). Key activities in this step:
- • Shipping point determination based on plant + shipping conditions + loading group
- • Route determination based on shipping point + ship-to country + shipping conditions
- • Picking — assigning warehouse operators to physically retrieve goods (WM-integrated)
- • Packing — optional grouping of items into shipping units (handling units in SAP)
Key table: LIKP (header) and LIPS (items). Use VL06O to monitor deliveries by status.
Step 5 — Post Goods Issue (PGI) — The Revenue Recognition Moment
Post Goods Issue (PGI), executed in VL02N, is the critical moment when goods are considered handed over to the customer. Five things happen in parallel:
Stock in the plant is reduced by the delivered quantity using movement type 601.
Cost of Goods Sold is debited and inventory account credited. In S/4HANA, posts directly to ACDOCA.
Header and item statuses change to "Goods Issue Posted" — visible in VBUK/VBUP (ECC) or directly in VBAK/VBAP (S/4HANA).
The delivery becomes eligible for billing, appearing in VF04 for the next billing run.
Transfer of Requirements is cancelled — the demand is fulfilled, so it no longer shows in MRP planning.
Important: PGI is irreversible without a cancellation posting (movement type 602 via VL09). The PGI date is the key reference for revenue recognition timing.
Step 6 — Billing & Revenue Posting
Billing is the final step where the customer receives a formal invoice and revenue is posted to FI. Transaction VF01 creates a billing document — usually with reference to a delivery (delivery-related billing) or a sales order (order-related billing).
Three things happen when the billing document is saved:
- • Billing document created — with all pricing, tax, and account determination
- • Accounting document posted — debit customer receivable, credit revenue, credit tax (if applicable) via VKOA
- • Output triggered — invoice printed, emailed, or sent via EDI based on output determination
Key tables: VBRK (header) and VBRP (items). Use VF04 to view the billing due list and process invoices in batch.
Document Flow — The Link Between It All
Every document in the OTC chain is linked to its predecessor through table VBFA (Sales Document Flow). This linkage is what enables end-to-end traceability.
View the complete document flow: VA03 → Environment → Document Flow. You'll see the full chain from inquiry to accounting document, with status indicators showing where each step stands.
OTC Integration with Other SAP Modules
| Module | Integration Point | When It Happens |
|---|---|---|
| MM | Material master, inventory, goods movement | Throughout OTC — master data and inventory |
| WM / EWM | Picking, packing, warehouse task creation | Delivery step (Step 4) |
| PP | Production demand from sales order | Via Transfer of Requirements (Step 2) |
| QM | Quality inspection before delivery | Between delivery and PGI (Step 4-5) |
| FI | Receivables, revenue, tax postings via VKOA | At PGI (COGS) and Billing (revenue) |
| CO-PA | Profitability analysis by segment | At Billing — characteristics passed to CO-PA |
What Changed in S/4HANA
VBUK and VBUP status tables are replaced — status is stored directly in VBAK / VBAP. Reduces data redundancy and improves query performance.
Classic ATP is replaced with aATP — richer confirmation logic, product allocation, back-order processing (BOP), and alternative-based confirmation.
FI and CO postings from PGI and Billing merge into a single line-item table. Real-time profitability analysis without extracting to BW.
Customer master in XD01 is replaced by BP with role FLCU01 (SD Customer) and FLCU00 (FI Customer). Unified data model for all business relationships.
Every core transaction has a Fiori equivalent: Create Sales Order, Manage Outbound Deliveries, Create Billing Documents, Sales Order Fulfillment Monitor, and more.
Frequently Asked Questions
What is the Order-to-Cash (OTC) process in SAP SD?
Order-to-Cash (OTC) is the end-to-end process in SAP SD that starts with a customer inquiry or order and ends with cash collection. It typically involves six steps: (1) Pre-sales activities (inquiry, quotation), (2) Sales order creation (VA01), (3) Availability check and transfer of requirements to MRP, (4) Delivery processing including picking and packing (VL01N), (5) Goods issue posting which reduces inventory and posts COGS (VL02N), (6) Billing document creation and revenue posting to FI (VF01). Each step creates a document linked via document flow (VBFA).
What are the key T-codes in the SAP Order-to-Cash cycle?
Core OTC T-codes: VA11 (Create Inquiry), VA21 (Create Quotation), VA01/VA02/VA03 (Create/Change/Display Sales Order), VL01N (Create Delivery), VL02N (Change Delivery & Post Goods Issue), VL06O (Outbound Delivery Monitor), VF01/VF02/VF03 (Create/Change/Display Billing), VF04 (Billing Due List), VA05 (List Sales Orders), MB51 (Material Document List), FBL5N (Customer Line Items in FI). In S/4HANA, many of these are also available as Fiori apps.
How does document flow work in SAP SD?
Document flow in SAP SD creates a chain of linked documents through the OTC cycle. Each subsequent document references its predecessor — a delivery references a sales order, a billing document references a delivery. The linkage is stored in table VBFA (Sales Document Flow). You can view the complete document flow from VA03 → Environment → Document Flow, which shows the full history: inquiry → quotation → sales order → delivery → goods issue → invoice → accounting document.
What happens during Post Goods Issue (PGI) in SAP?
Post Goods Issue (PGI) in VL02N is the critical revenue recognition moment. When executed, five things happen simultaneously: (1) Inventory reduces by the delivered quantity (movement type 601); (2) COGS account is debited and inventory credited in FI; (3) Delivery status changes to "Goods Issue Posted"; (4) The delivery becomes eligible for billing in the due list; (5) Transfer of Requirements is reversed in MRP. PGI is irreversible without a cancellation posting. In S/4HANA, these postings go directly to ACDOCA.
What is the difference between Inquiry and Quotation in SAP SD?
An Inquiry (document type IN, T-code VA11) is a non-binding customer request for information about products, prices, or availability. A Quotation (document type QT, T-code VA21) is a legally binding offer from the company to the customer, specifying price, quantity, and validity period. Quotations are typically created with reference to an Inquiry and carry a validity date after which they expire. Neither affects inventory or accounting. Both feed the Sales Information System for pipeline reporting.
How does SAP SD integrate with other modules in the OTC cycle?
OTC integrates with multiple SAP modules: MM (Materials Management) for inventory and material master; WM (Warehouse Management) for picking and packing strategies; PP (Production Planning) when sales demand triggers production; QM (Quality Management) when inspection is required before delivery; FI (Financial Accounting) for receivables, revenue, and tax postings via VKOA; CO (Controlling) for profitability analysis via CO-PA. In S/4HANA, FI and CO integration is simplified through the Universal Journal (ACDOCA).
Master every OTC scenario — hands-on.
Order-to-Cash is the foundation — inside The SD Vault you'll find configuration scenarios for every step, plus 230+ interview questions and a Ready Reckoner for fast on-the-job reference.
Get Lifetime Access →Also see our Pricing Procedure, Credit Management, and Interview Questions guides.