ERPClimb logoERPClimb

SAP SD / O2C Sales Documents and End-to-End Order-to-Cash Interview Questions

Sales Documents and End-to-End Order-to-Cash comes up in SAP SD / O2C interviews because it is one of the few areas where an interviewer can tell, in two questions, whether you have worked with the process or only read about it.

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.

This page carries 11 reviewed SAP SD / O2C sales documents and end-to-end order-to-cash interview questions, each with a complete written answer and no sign-in required. The set breaks down into 2 foundational, 5 mid-level and 4 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

The fastest way to use this page is to read the question, answer it yourself, and only then read the answer. The gap between your version and the written one is your actual revision list for sales documents and end-to-end order-to-cash.

11 Sales Documents and End-to-End Order-to-Cash questions with answers

easySales Documents and End-to-End Order-to-Cash

1. What is the purpose of Transfer of Requirements (TOR) in SD, and how does it interact with MRP in materials planning?

TOR passes sales order/schedule line quantities to MM/PP so demand is visible for MRP planning runs, triggering procurement or production proposals. It's controlled by requirement class/type settings and availability check group at material master level. Without TOR active, sales orders don't create planning-relevant demand, causing supply shortfalls even though orders exist in SD.
easySales Documents and End-to-End Order-to-Cash

2. 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?

SAP offers checking rule/checking group combinations at material level: no check, ATP check (against unrestricted stock plus planned inflows minus outbound requirements), or check against product allocation. The checking group is set on the material master (MRP3/Sales: General/Plant view), and the checking rule comes from the transaction (e.g., order vs delivery). Together with the scope of check (OVZ9), they determine which stock/inflow/outflow categories are included in ATP.
mediumSales Documents and End-to-End Order-to-Cash

3. 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?

Common blockers include missing reason for return code, missing reference to original delivery/billing document required for MTO cost/revenue traceability, and missing valuated sales order stock information since MTO items are tied to a specific sales order stock segment. The incompletion procedure (VUA2) for returns order type (RE) often requires fields like order reason, reference document, and batch/valuated stock number for MTO. Complete these fields via VA02, checking incompletion log (edit>incompleteness log) before delivery.
mediumSales Documents and End-to-End Order-to-Cash

4. 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?

Item category TAS triggers a purchase requisition on order save, and billing relevance is normally set to invoice-receipt-related billing (billing plan or via billing relevance F), meaning invoicing is only possible after MM records the vendor invoice via MIRO. The incompletion procedure should flag missing purchase order/GR-based data before billing document creation is allowed. I would verify PR/PO creation account assignment, IR flag on the PO, and that copy control from invoice-relevant reference is pulling actual vendor cost.
mediumSales Documents and End-to-End Order-to-Cash

5. 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?

I would check the item category's requirement type assignment (via requirement type determination table using item category and MRP type/strategy group), confirm the requirements class flags 'Individual requirement' and requirements transfer as active, and verify the material's strategy group (e.g., 20) supports MTO. I'd also check schedule line category relevance for TOR and that the plant/checking group combination is not disabling requirements transfer.
mediumSales Documents and End-to-End Order-to-Cash

6. 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.

First check the document flow (VA03/document flow tab) to confirm whether the order truly reached production order creation or stalled earlier in requirements transfer. Then review the incompletion log status group for the item—configuration characteristics are often not assignable as standard incompletion fields since they're maintained via the configuration profile, not standard VBAP fields, so incompletion procedures typically cannot enforce them. The real gap is usually in the configuration profile's mandatory characteristic settings or class node dependencies, not the SD incompletion procedure, requiring PP/variant configuration review alongside SD.
mediumSales Documents and End-to-End Order-to-Cash

7. 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?

Substitution rules automatically derive or overwrite field values based on defined conditions (e.g., deriving a plant from a customer-material combination) without user intervention, ensuring consistency. Incompletion procedures instead flag missing mandatory fields and block subsequent processing (e.g., delivery) until the user manually completes them. Substitutions are proactive and automatic; incompletion is reactive and requires manual input. Use substitution for derivable, rule-based values, and incompletion for fields requiring human judgment or that cannot be reliably derived.
hardSales Documents and End-to-End Order-to-Cash

8. 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?

Design the rush order type (SO/RE variant, e.g., SR) with immediate delivery creation and synchronous ATP check against plant-specific stock, using availability check group with checking rule for immediate confirmation (no advance planning horizon). Ensure requirements transfer is set to 1 (individual requirements) rather than summarized, so each rush order consumes ATP in real time and updates VBBE immediately. For multi-plant, consider central ATP or advanced ATP (aATP in S/4HANA) with quantity reservation locking to prevent race conditions across simultaneous entry points, plus proper enqueue/lock handling on material master records.
hardSales Documents and End-to-End Order-to-Cash

9. 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?

Start by confirming the requirement class (via strategy group/requirements type) has 'MRP relevant' and correct special stock indicator (E) set; then verify the material's MRP type and strategy are consistent across the specific plant/MRP area used. Check if the plant is assigned to a separate MRP area not visible in the planner's MD04 selection, and confirm CO09/MD04 selection parameters include sales order stock. Finally validate VBBE and MDVM entries for consistency versus a live MRP run.
hardSales Documents and End-to-End Order-to-Cash

10. 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?

I would run rescheduling (V_RA) in a background job scheped outside peak hours, using a sort strategy (via rescheduling profile/sort sequence, e.g., by priority customer, order date) to reallocate confirmed quantities. I'd first execute in simulation/proposal mode to review changes and set a cutoff to exclude documents like deliveries already created. Blocking the affected order types during the run and communicating results to sales via output/exception list avoids double allocation confusion.
hardSales Documents and End-to-End Order-to-Cash

11. 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.

Cash sales use order type CS which is configured to automatically create the delivery and invoice at order save via output determination and a special billing type (BV), posting to a cash clearing GL account rather than customer receivables since payment is received immediately at point of sale. Architecturally, this bypasses the credit management check, dunning, and normal FI-AR open item processing; the invoice is printed immediately, and typically no dunning or credit exposure exists, requiring separate reconciliation account setup for the cash account.

Related lesson

O2C Configuration Determinants and Cross-Module Integration

Related topics

Advanced SD Scenarios, Integration and Production SupportS/4HANA SD Transformation, Migration, Public Cloud and ArchitecturePricingEnterprise StructureBillingCustomer and Business PartnerOutput ManagementSchedule Line CategoriesItem CategoriesCopy ControlCredit ManagementSales Documents

Next practice step

Practice with Interview AITake a mock test