BOM Component Missing From Production Order

Production planning or the shop floor reports that a material everyone expects to see on the order pick list simply is not there. Phrasing varies: 'the packaging component never gets picked', 'the order was released short one raw material', 'warehouse says the reservation for this part never generated', or a planner notices the order cost estimate is missing a line that used to be there. Nobody initially calls it a BOM problem because the BOM itself, opened on its own, shows the component sitting exactly where it should be. The confusion usually starts when someone compares two orders for the same finished material created a week apart, one has the component, one does not, and the difference is not obvious from the order header.

Pull the BOM in CS03 using the explosion date equal to the order's basic start date, not today's date, and compare the resulting item list line by line against the order's component list from CO03. Where a line exists in the BOM but not the order, check its status, deletion flag, and effectivity fields side by side, then confirm the order's actual BOM alternative and explosion number against what the linked production version specifies in C223.

If the item was deleted or miscategorized, correct it in CS02, a data change with no transport, but existing orders will not pick it up automatically and need the PP master data re-read function executed against the open order in CO02. If effectivity dates are wrong, extend them in CS02, same data-only path, followed by the re-read. If the production version points to the wrong alternative, correct the version in C223, a master data fix; if the BOM selection priority logic itself is wrong at the order-type level, that is a customizing change requiring a transport through the landscape and should go through the master data or PP configuration owner rather than being patched locally. If the cause is an object dependency, the fix belongs to whoever owns variant configuration content and typically needs testing in a quality system before transport, since dependency logic affects every order for that configurable material, not just the one being investigated.

The immediate reflex is to open the order in CO02 and add the missing material directly as a manual, non-BOM component line. This gets the current order moving and satisfies whoever is waiting on the pick list, but it does nothing to the BOM, the production version, or the object dependency that caused the gap, so the next order for the same material comes up short again. It also detaches that component from the BOM's cost structure and where-used history, which shows up later as an unexplained variance in the cost estimate or a missing link during an engineering change review.

Production planning master data maintenance owns the BOM item and its status and effectivity fields; the MRP controller or plant data steward owns the production version assignment; variant configuration object dependencies belong to whoever maintains classification content for that material group. The handover note should carry the order number, material, plant, BOM usage and alternative, the missing component, and the order's basic start date so the receiving team can reproduce the explosion exactly.