Sales Documents and End-to-End Order-to-Cash
SD / O2Cbeginner

SAP SD Order to Cash Part 1: The O2C Process End to End

Key takeaway

The complete order-to-cash process in SAP: inquiry and quotation, sales order, availability and credit checks, delivery, picking, packing, goods issue, billing, accounting, and payment — the documents created, the modules involved and how document flow links them.

What this complete series covers

A practical SAP SD Order-to-Cash course that follows one process from sales order through delivery, PGI, billing, FI integration and production troubleshooting.

Who it is for
Best for SAP SD consultants, ABAP developers supporting SD, and learners who want to understand the complete O2C flow instead of isolated transactions.
Prerequisites
Basic SAP navigation and customer/material master-data concepts help. Start with Part 1; each later part builds on the document flow.
Final outcome
By the end, you should be able to explain the complete O2C process, understand the main configuration determinants, follow accounting integration, and troubleshoot the first broken step in production.
  1. Part 1: SAP SD Order to Cash Part 1: The O2C Process End to End

    An orientation to why Order-to-Cash exists, the standard SAP SD document chain, and the master data that every downstream document depends on.

  2. Part 2: SAP SD Order to Cash Part 2: The Sales Order — Order Type, Item Category, Pricing and ATP

    Understand sales-order controls, item and schedule-line behavior, pricing, partner determination and availability check.

  3. Part 3: SAP SD Order to Cash Part 3: Delivery, Picking, Packing and Goods Issue

    Follow the order into outbound delivery, warehouse execution, picking, packing and post goods issue.

  4. Part 4: SAP SD Order to Cash Part 4: Billing and Accounting

    Understand billing relevance, copy control, billing split, FI posting and revenue account determination.

  5. Part 5: SAP SD Order to Cash Part 5: Configuration and Integration with MM and FI

    Understand the configuration rules behind O2C: item category, schedule line, copy control, pricing behavior and FI/MM integration.

  6. Part 6: SAP SD Order to Cash Part 6: Troubleshooting Document Flow, Blocks and Common Errors

    Troubleshoot O2C from document flow and status, separating data, configuration, authorization, integration and custom-code causes.

System and release assumptions: Examples are written for SAP S/4HANA-oriented SD. Exact Fiori apps, transaction codes, Advanced ATP capabilities and configuration paths can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ O2C: (inquiry/quotation) → sales order → delivery → picking/packing → goods issue → billing → payment.

✅ Each step creates a document linked in document flow.

✅ Goods issue posts inventory and COGS; billing posts receivable, revenue and tax; payment clears the receivable.

✅ Checks along the way: availability (ATP), credit, incompletion, blocks.

⚠️ Most O2C issues are visible in document flow and status — always start there.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: The O2C process end to end

Part 2: The sales order

Part 3: Delivery, picking, packing and PGI

Part 4: Billing and accounting

Part 5: Configuration and integration

Part 6: Troubleshooting

━━━━━━━━━━━━━━━━━━━━
▶ 1. PRE-SALES

  • Inquiry (IN), quotation (QT) with validity.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SALES ORDER

  • Order type, customer, materials, pricing, ATP, credit.

━━━━━━━━━━━━━━━━━━━━
▶ 3. SHIPPING

  • Outbound delivery, picking, packing, PGI (601).

━━━━━━━━━━━━━━━━━━━━
▶ 4. BILLING

  • Invoice (F2) → accounting document.

━━━━━━━━━━━━━━━━━━━━
▶ 5. PAYMENT

  • Incoming payment in FI clears the open item.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. VA01 order → VL01N delivery → pick/PGI → VF01 invoice.
  2. Check accounting documents.
  3. Post payment (F-28) and check document flow.

✅ CHECKPOINT: document flow shows order → delivery → goods issue → invoice → accounting → payment clearing.

Code example

ABAP Code
===== STEP 1: transactions =====VA11 inquiry | VA21 quotation | VA01 order | VL01N delivery | LT03/EWM picking | VL02N PGI | VF01 invoice | F-28 payment ===== STEP 2: postings =====PGI 601: Dr COGS Cr inventory | Invoice: Dr customer Cr revenue Cr tax | Payment: Dr bank Cr customer ===== STEP 3: document flow =====VA03 > Display document flow: order → delivery → material doc → invoice → accounting doc

Real project scenario

A newly onboarded consultant was asked why some orders never got invoiced. Document flow showed deliveries without goods issue, blocked by picking not completed in the warehouse. Aligning warehouse confirmations and monitoring deliveries due for PGI resolved the backlog.

Common mistakes

  • Ignoring document flow.
  • Confusing delivery with goods issue.
  • Billing before PGI in delivery-related processes.
  • Not checking blocks.
  • Forgetting payment clearing.

Best practices

  • Start analysis with document flow.
  • Monitor due lists (delivery, billing).
  • Understand postings per step.
  • Use the detailed tracks for depth.
  • Test full cycles.

Interview angle

Questions: "Explain O2C in SAP", "Which documents are created?", "What postings happen at PGI and billing?"
Strong answer: inquiry/quotation, order, delivery, picking/packing, PGI (COGS), billing (AR/revenue/tax), payment; document flow; checks and blocks.

Practice this lesson

Quick check

1. Which O2C step posts the customer receivable?

2. What is the correct sequence of the standard O2C documents?

3. Some orders are never invoiced. Where do you start?

Interview questions

1. Explain the end-to-end document and accounting flow for a cash sale transaction and identify the key differences from a standard order-to-cash cycle that a solution architect must design for.

Answer it in your own words first, then compare.

2. A newly onboarded consultant must explain the O2C process and its documents to business users. How would you explain it?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics