Goods Issue Blocked on Outbound Delivery

Reported as the truck is at the dock and the delivery will not confirm, or the warehouse clicked post goods issue and got a red message instead of a material document number. Sometimes it is phrased as the PGI button is greyed out, or the delivery keeps saying picking not completed even though the team physically loaded the goods. Occasionally it surfaces as a batch job failure: a background PGI run for a wave of deliveries throws errors for some documents and posts others cleanly, and nobody can explain why one delivery in the batch is different from the rest. The common thread is that everyone treats it as a technical block, when in most cases the delivery is correctly refusing to post because a precondition genuinely is not met.

Pull the list of deliveries with an open goods movement status for the affected shipping point or route using the delivery monitor, then cross-reference each one against stock overview for the specific batch and storage location at the same posting date. For the account determination theory, reproduce the exact movement type and valuation class combination in a test posting and capture the error text, which will name the missing G/L account determination entry directly.

If picking is unconfirmed, this is a warehouse execution fix: confirm or reprocess the transfer order, no config or transport involved. If stock has been consumed elsewhere, the fix is operational: re-source from another batch or storage location, or hold the delivery until replenishment, again a data and process decision, not a system defect. Missing account determination is a configuration gap and must go through OBYC with a transport to reach production; do not let anyone post a manual journal entry as a workaround, since that breaks the automatic linkage for every future posting of that combination. A closed posting period is opened deliberately through MMRV by whoever owns period-end close, and should never be opened blanket-wide just to push one delivery through, since that reopens the period for every material and every movement. Batch or serial number gaps are corrected by completing the missing master data on the specific batch or material, which is a data fix. A deletion flag or invalid storage location is a master data correction requiring the material master owner to confirm the plant or storage location is actually still meant to be active.

The reflex is to change the delivery quantity down to whatever the system will accept, or to delete the delivery and recreate it from the order. Both hide the real shortage instead of resolving it: a reduced quantity means the customer gets less stock than ordered without anyone deciding that deliberately, and recreating the delivery loses any batch, serial number, or packing work already done and simply reproduces the same error against the new document once it hits the same stock or account determination gap. Asking basis to open every posting period broadly is equally common and equally wrong, since it removes a control for the whole plant to fix one document.

Warehouse operations owns picking confirmation and physical stock accuracy. The SD or MM consultant owns diagnosing which of the causes above applies and routing the config gap to the right owner. FI or MM configuration owns account determination and posting period control. The handover note should state the delivery number, the exact error text, the stock check performed with quantities, and which specific cause was confirmed before any fix is applied.