Order Stuck Incomplete During Settlement

Controlling reports that the same batch of production orders shows up on the settlement run every period, never dropping off the list even after settlement has apparently been executed. Finance asks why WIP or variance on certain orders never zeroes out. Production supervisors say the order is finished, the material is in stock, but the system will not let them mark it closed - CO02 shows the order still open, or CO88 throws it into the error log with no clear message beyond an incompletion warning. Sometimes the plant controller notices at year-end that a handful of orders from three periods back are still sitting with unsettled costs, and nobody can explain why they were never picked up cleanly the first time they were processed.

Run CO88 in test mode for the plant and period in question with the detail log switched on, and list every order that returns an error or a partial settlement result rather than a clean settlement confirmation. Cross-reference that list against orders with open reservation quantity greater than zero and against purchase orders assigned to a production order with no goods receipt. An order appearing on this list for more than one period in a row confirms it is not a one-off timing issue but a genuine blocked settlement.

Where the cause is open reservations or open procurement documents, this is a data fix owned by production and purchasing - post the missing goods issue, receive the outstanding purchase order, or reverse and close the requisition if it is no longer needed, then rerun settlement. Where confirmations are missing or TECO was never set, production posts the missing confirmation and sets technical completion manually or via the automatic goods receipt confirmation step, again a data correction with no config change. Where the settlement rule is missing or incomplete, controlling corrects the distribution rule directly on the order (data fix) or, if this is happening across many orders of the same type, the default rule template needs to be built into the order type settings, which is a config change requiring transport. Where the settlement profile itself is blocking valid settlements structurally, that is a config correction in the IMG under the order type's settlement profile assignment, transported through the normal change path. Where the CO period is locked, finance opens the period, settles, then re-closes it - a control action, not a fix to the order.

The reflex is to force the order through with a full or manual settlement override, or to flag the order deleted or technically complete without resolving the open reservation or procurement document underneath it. This clears the worklist entry but leaves the underlying open goods movement or open purchase order unresolved - inventory or accounts payable will show a discrepancy later, and the variance that should have posted to the cost object never does, so it either vanishes or lands on the wrong account at year-end reconciliation.

Production owns unposted goods movements and missing confirmations; purchasing owns open procurement documents tied to the order; controlling owns the settlement rule, the RA run, and the settlement profile configuration. The handover note should list the order number, the specific blocking condition found in the CO88 detail log, and which side needs to act before the next settlement run is attempted.