Production Order Execution: Release, Confirmations, Goods Movements, and Cost Flow

Explanation

Once a production order is released (status REL), it becomes executable: components can be issued from stock, operations can be confirmed as work progresses, and actual costs begin accumulating against the order. This lesson focuses on the runtime document flow that a consultant must understand to support manufacturing operations and to troubleshoot discrepancies between plan and actual. Goods issue of components can happen in two main modes: manual goods issue against the order's reservations (using movement type 261, typically via MIGO or MB1A referencing the order number), or backflushing, where components are automatically issued at the time of operation or order confirmation based on a backflush indicator set on the material master or work center. Backflushing simplifies shop floor data entry but requires accurate BOM quantities and stock accuracy, since discrepancies are only caught later during physical inventory or variance review, not at the point of issue. Operation confirmations record actual progress: yield quantity, scrap quantity, and actual times (setup, machine, labor) against each operation, typically via CO11N for individual confirmation or mass confirmation transactions for high-volume environments. Confirmations drive several downstream effects: they update the order's status (partially confirmed, confirmed), they can trigger automatic goods receipt of the finished product if configured, they can trigger backflush of components and activity postings to controlling, and they feed capacity actuals back for comparison against planned capacity. Goods receipt of the finished product (movement type 101, typically via MIGO referencing the order) increases warehouse stock and, depending on configuration, can happen automatically from the final confirmation or be a separate manual step. Quality management integration is significant here: if the material is quality-inspection relevant, goods receipt can post stock to quality inspection stock rather than unrestricted, and usage decision in QM determines final stock disposition. Cost-wise, the order accumulates actual costs from component consumption (valuated at the material's price control - standard or moving average) and from activity confirmations (valuated using activity price rates from cost centers, typically maintained via KP26-style planning in cost center accounting - though the exact activity price transaction can vary by client setup). The variance between planned (target) cost and actual cost becomes visible once the order reaches technical completion and undergoes settlement, where actual costs are transferred to the appropriate cost object (cost center, material ledger, sales order, or profitability segment depending on settlement rule). Technical completion (TECO) signals that physical work is done and no further goods movements are expected, though the order remains open for final cost settlement. Full closure (CLSD) typically happens after settlement and often after a defined retention period, controlled by archiving and status configuration. Consultants must understand this flow deeply because most production support tickets - missing goods receipt, stuck confirmations, incorrect costs, blocked settlement - trace back to a gap or sequencing issue somewhere in this execution chain.

Code example

* Illustrative execution flow for Order 100023456 * Step 1: Release order* CO02 -> change status to REL * Step 2: Goods issue of components (manual, movement type 261)* MIGO / MB1A referencing Order 100023456, Reservation 0000012345 * Step 3: Confirm operation 0010 (Mixing)* CO11N: Order 100023456, Operation 0010, Yield 500 PC, Scrap 5 PC*        Actual Setup 32min, Actual Machine 2.1h * Step 4: Auto goods receipt at final confirmation (if configured)* Movement type 101 posted automatically for 495 PC (500 - 5 scrap) * Step 5: Technical completion* CO02 -> set status TECO once all operations confirmed and GR posted * Step 6: Settlement (period-end)* KO88 (or CO88 for collective settlement) transfers order balance* per the settlement rule (e.g., to cost center or material ledger)

Real project scenario

A food manufacturing client used backflushing for high-volume ingredients but manual issue for a controlled allergen-tracked ingredient. During a production support review, actual costs on several orders showed large unfavorable variances traced to the manual-issue ingredient being under-recorded because operators frequently forgot the manual goods issue step before confirming the order. The team redesigned the process to require the manual issue as a mandatory prerequisite check before confirmation could be saved, using a combination of process training and a validation step in the confirmation transaction, which significantly reduced unrecorded consumption and variance noise in month-end cost reviews.

Common mistakes

• Forgetting that backflush components are only issued at confirmation time, so if confirmation is delayed, inventory appears overstated in the interim. • Confirming final operations before goods issue is complete, causing distorted work-in-process and cost timing mismatches. • Assuming automatic goods receipt always happens at final confirmation; this depends on control key and configuration, and some orders require an explicit separate goods receipt step. • Not reconciling scrap reporting at confirmation with actual physical scrap, leading to inflated yield assumptions in future planning. • Attempting settlement before technical completion or before all confirmations are posted, resulting in incomplete or premature cost transfer.

Best practices

• Use backflushing selectively for low-value, high-volume components and manual issue for high-value or regulatory-tracked materials. • Enforce a business process sequence (issue before final confirmation) through training and, where feasible, system controls. • Reconcile confirmed quantities and scrap against physical counts periodically to validate backflush accuracy. • Ensure control key settings on routing operations correctly reflect whether automatic goods receipt should trigger at confirmation. • Review technical completion criteria before running settlement to avoid incomplete cost transfers and repeated settlement runs.

Interview angle

Expect scenario-based questions such as 'a production order shows released but no goods movements, what could be wrong' or 'explain the difference between backflushing and manual goods issue and when you'd choose each.' Interviewers also test understanding of the confirmation-to-settlement chain, particularly why technical completion is a prerequisite for clean settlement and how scrap and variance visibility depend on accurate confirmation data.