Sales Documents and End-to-End Order-to-Cash
Parent overview of the Sales Documents and End-to-End Order-to-Cash (O2C) learning path. Covers the business purpose of the O2C cycle, the document flow from pre-sales through sales order, delivery, and billing, the master data and configuration determinants that drive document behavior, integration touchpoints with Finance and Materials Management, and how the process differs across ECC, S/4HANA on-premise/private cloud, and S/4HANA public cloud. This topic orients learners before they proceed into detailed child topics on pricing, availability, credit management, billing, and output/integration.
Overview
Parent overview of the Sales Documents and End-to-End Order-to-Cash (O2C) learning path. Covers the business purpose of the O2C cycle, the document flow from pre-sales through sales order, delivery, and billing, the master data and configuration determinants that drive document behavior, integration touchpoints with Finance and Materials Management, and how the process differs across ECC, S/4HANA on-premise/private cloud, and S/4HANA public cloud. This topic orients learners before they proceed into detailed child topics on pricing, availability, credit management, billing, and output/integration.
Lessons in this topic
- O2C Configuration Determinants and Cross-Module IntegrationHow document type, item category, and schedule line category configuration drive O2C behavior, and how the process integrates with Finance, Materials Management, and credit management, with production troubleshooting guidance.
- Order-to-Cash Foundations: Process, Documents, and Master DataAn orientation to why Order-to-Cash exists, the standard SAP SD document chain, and the master data that every downstream document depends on.
Interview questions covered
- What is the purpose of Transfer of Requirements (TOR) in SD, and how does it interact with MRP in materials planning?
- A returns order created via VA01 with reference to a make-to-order sales order is stuck incomplete, preventing return delivery creation. What incompletion procedure elements typically block this, and how does it tie to MTO integration?
- What is the fundamental difference between the availability check types used in ATP checking, and what determines which check happens when a sales order is created?
- For a rush order process spanning multiple plants with immediate delivery requirements, how would you architect ATP and requirements transfer to guarantee real-time stock confirmation while avoiding overselling across parallel rush order entry points?
- In a global MTO rollout, sales order items show a confirmed schedule line and TOR appears successful in VBBE, yet the production planner reports no planned/independent requirement visible in MD04 for that sales order's individual stock segment. As the architect, how would you systematically isolate whether this is a requirements class issue, special stock segregation issue, or MRP area configuration issue?
- In a third-party sales scenario where the vendor invoice significantly differs from the customer billing amount, how would the incompletion procedure and item category configuration typically prevent premature billing, and what integration touchpoint with MM/procurement should be verified?
- During month-end, a high-priority customer's open sales orders are stuck with unconfirmed schedule lines because stock was consumed by lower-priority orders created earlier. As the architect, how would you design a backorder processing approach to correct allocation without disrupting daily order entry?
- 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.
- A customer orders a make-to-order finished good, but the sales order line does not generate a corresponding planned/production order in PP. What item category and requirements configuration would you review to diagnose this?
- A sales rep creates a make-to-order sales order that saves successfully with only an incompletion log warning, but downstream production order creation later fails due to missing variant configuration characteristic values. Walk through how you would diagnose whether this is an incompletion procedure design gap versus a separate variant configuration/production integration issue.
- How do field-level substitutions using the substitution rule (transaction GGB1/OPSM equivalents) differ from incompletion procedures in ensuring sales order data quality, and when would you use each?