Production Order Blocked by Missing Component Availability

The planner says the order 'won't release' or 'is stuck in CRTD' and the missing parts list pops up every time release is attempted. Production supervisors report that a job scheduled for the floor today is not available in the system even though the warehouse team insists the material is sitting on the shelf. Sometimes the complaint comes from the opposite direction: MRP shows plenty of stock in MD04 but the order still throws a shortage on release, and nobody can explain why the two screens disagree. In batch environments the same order releases fine one day and blocks the next run with no master data change that anyone remembers making.

Work from the order outward, not from configuration inward. Start in CO02, attempt release, and capture the exact missing parts message and the component list it names. Pull the missing parts detail through the missing parts information system to see quantity short and date. Check MD04 for that material and plant to see whether a covering element exists and on what date. Check MMBE to see if stock exists but sits in quality inspection or blocked stock rather than unrestricted. Check CS03 to confirm the component is on the active BOM alternative valid for the order date and lot size, and that it carries the same plant. Check the material master MRP2 view in MM03 for special procurement key and default storage location. Finally check the checking group and scope assigned to the order type and plant in the availability check control settings, since a scope change there affects every order of that type.

Pull the order's missing parts list showing material, plant, storage location, shortfall quantity, and required date, then run MD04 for the same material and plant side by side. If MD04 shows covering stock or a firmed supply element on or before the required date but the order still blocks, the fault is in checking control scope or storage location assignment, not in the material situation. If MD04 shows nothing covering the date, the shortage is real and the evidence supports a planning escalation, not a configuration ticket.

If the shortage is real, this is a planning and procurement action, not a system fix: expedite the open supply element, split the order, or reschedule it against a later confirmed date. If the BOM is not extended to the plant or lacks a valid alternative, extend the material or correct the BOM item, both master data changes with no transport needed. If stock is sitting in quality inspection or blocked, release it through the quality process or the relevant stock posting, a data action owned by quality or warehouse. If the storage location on the BOM item or reservation does not match where stock is actually posted, correct the BOM item storage location, a master data fix. If the root cause is the checking control scope being too strict or too loose, that is a configuration change to the checking rule assigned to the order type and plant, requires a transport, and should be reviewed with logistics because it changes behavior for every order of that combination, not just the one in front of you.

The reflex is to force the release anyway, either by overriding the availability check warning in CO02 or by manually confirming the component as available without checking where the stock actually is. The order releases and looks healthy in the system, but the material still is not physically at the work center. The shortage resurfaces at goods issue or confirmation, now on the shop floor where it is harder to diagnose, and the missing parts problem gets blamed on backflush or confirmation instead of the availability check that correctly flagged it in the first place.

First triage belongs to the MRP controller or production planner who has to decide whether the shortage is real or a system false positive. If it turns out to be checking control scope, ownership moves to the PP configuration lead working with logistics, since the fix changes behavior for the whole order type and plant. The handover note should state the material, plant, order number, the missing parts message text, and the MD04 snapshot taken at the time of the block.