Order Confirmation, Goods Movements, and Status Management

Explanation

Confirmation is the operational heartbeat of production order execution. When a shop floor operator or supervisor confirms an operation or the full order, SAP records actual quantities produced, actual activity consumption (machine hours, labor hours), and actual dates/times against the order. This single transaction typically triggers a chain of downstream postings: automatic goods receipt of the finished or semi-finished material (if configured), automatic goods issue of backflushed components, and updates to the order's system status. Confirmation can happen at the operation level (partial confirmation of individual routing steps) or at the order level (final confirmation, CNF). Time tickets record actual setup, machine, and labor time per operation, which feeds activity type consumption for costing. The confirmation process reads the routing/master recipe operation control keys to determine which operations require confirmation, which allow milestone confirmation (confirming a downstream operation automatically confirms upstream operations), and which components are backflush-relevant based on the backflush indicator on the BOM item or work center. Goods movement integration is critical: backflushed components use movement type 261 (goods issue for order) automatically at confirmation time, drawing from the storage location specified on the BOM item, order header, or work center. Non-backflush components require manual goods issue via a separate transaction before or during production. Goods receipt of the order's output material typically uses movement type 101, either automatically triggered by final confirmation (if the 'automatic GR' indicator is set at the order or work center level) or performed as a separate manual GR step. System status progresses through a defined sequence: Created (CRTD), Released (REL), Partially Confirmed (PCNF), Confirmed (CNF), Technically Completed (TECO), and Closed (CLSD). Each status enables or blocks specific business transactions—for example, you cannot post a goods receipt against a technically completed order without reversing the TECO status first. User statuses can supplement system statuses to enforce site-specific approval workflows, such as requiring quality release before allowing confirmation. A frequent operational challenge is negative stock or missing component stock at backflush time. If a backflush component lacks sufficient stock, the confirmation can fail outright or post the goods issue with a negative or blocked stock indicator, depending on configuration in the plant's negative stock settings. Reversing a confirmation (CORS or equivalent) reverses both the confirmation record and any automatically triggered goods movements, but only in the correct sequence—reversing an interim confirmation when later confirmations exist requires careful analysis to avoid inconsistent order quantities. In S/4HANA, the confirmation process is functionally similar, but the Manufacturing Execution integration (with SAP Digital Manufacturing or MES connectors) increasingly automates confirmations from shop floor devices, reducing manual entry errors. The underlying database simplification does not change the business logic, but performance for querying confirmation history via order document flow is significantly faster on HANA due to elimination of aggregate tables.

Code example

* Example: reviewing order confirmation and goods movement history* Order document flow check (functional steps, not literal code) 1. Display production order (e.g., via order master data transaction)   -> Check header status: REL, PCNF, or CNF2. Review operation overview   -> Confirm operation 0010 (Setup) with actual setup time = 0.5 hr   -> Confirm operation 0020 (Machining) with actual machine time = 2.0 hr,      yield quantity = 100 EA, scrap quantity = 2 EA3. System automatically posts:   - Movement type 261: backflush component consumption     (from BOM items flagged as backflush-relevant)   - Movement type 101: goods receipt of yield quantity (if auto-GR active)4. Check order status after confirmation:   - If all operations confirmed -> status changes to CNF   - If only some operations confirmed -> status remains PCNF5. If reversal needed:   - Cancel confirmation (reverses time postings and triggers reversal     of movement types 262/102 for backflush and GR respectively)   - Sequence matters: reverse latest confirmation first

Real project scenario

A discrete manufacturing client implementing S/4HANA experienced frequent confirmation failures because component backflushing pointed to a storage location that had zero available stock due to a delayed inbound shipment. The project team resolved this by adding a stock availability check step in the shop floor confirmation screen (via a custom Fiori app) that warned operators before confirmation, and by working with the planning team to tighten reorder point parameters for high-usage backflush components, reducing failed confirmations by over 80% within two months of go-live.

Common mistakes

• Confirming an operation without recording scrap quantity, leading to inaccurate yield and cost variance reporting • Reversing a final confirmation without reversing subsequent settlement runs first, creating cost object inconsistencies • Assuming backflush always uses the order's default storage location when the work center or BOM item overrides it • Not distinguishing between operation confirmation and order confirmation when troubleshooting partial status issues • Ignoring negative stock settings and being surprised when backflush postings succeed with negative stock silently • Failing to educate shop floor users on milestone confirmation behavior, causing confusion when upstream operations show as confirmed unexpectedly

Best practices

• Configure milestone confirmation only for genuinely sequential operations to avoid masking incomplete work • Always capture scrap and rework quantities at confirmation for accurate yield and variance reporting • Review negative stock configuration per plant/storage location before go-live to prevent silent stock discrepancies • Use operation-level confirmation for long-running or complex routings to give visibility into work-in-process • Train users on the correct reversal sequence and restrict reversal authorization to avoid uncontrolled use • Monitor confirmation exception reports regularly during hypercare to catch backflush failures early

Interview angle

Interviewers often probe whether a candidate understands the difference between milestone and normal confirmation, and how backflushing interacts with storage location determination. Be ready to explain the sequence of status changes (REL to PCNF to CNF to TECO) and the business impact of each, plus how to safely reverse a confirmation without leaving orphaned goods movements or cost postings.