When a goods receipt won't post in SAP EWM, the block is almost always at a specific, identifiable point in the inbound flow — not random. This is the path a senior consultant walks to isolate it, from the inbound delivery through to the posting to the ERP.
1. Check the inbound delivery status in EWM
Start at the inbound delivery. Confirm it replicated correctly from ERP to EWM, that it's in a status that allows goods receipt, and that the quantities and products match what you expect. A delivery that didn't fully replicate — or that sits in an incomplete status — will never post.
2. Verify the warehouse task was created and confirmed
In EWM, goods receipt typically depends on putaway warehouse tasks being created and confirmed. Check whether the WT exists, whether it's open or confirmed, and whether confirmation is what triggers the posting in your process. An unconfirmed or errored task is one of the most common reasons the GR never completes.
3. Look at the qRFC queues between EWM and ERP
EWM and ERP communicate through queued RFC (qRFC). A goods receipt posts in EWM and must flow to ERP — if a queue is blocked, stuck, or in error, the posting stalls. Check the inbound and outbound queues for entries in a failed or waiting state, as a blocked queue silently holds up everything behind it.
4. Check handling unit and packing consistency
If your process uses handling units, an inconsistency — an HU not closed, a packing mismatch, or an HU in the wrong status — can prevent the receipt from posting. Confirm the HUs for the delivery are complete and in a postable state.
5. Review posting-relevant configuration and dates
A goods receipt can be blocked by period or date issues (a closed posting period in ERP), by a missing or incorrect movement type mapping, or by process-type configuration in EWM that doesn't resolve. If the data looks clean, the block is usually one of these configuration or period constraints.
6. Read the error in the application log
EWM's application log records why a posting failed — often a specific message about the queue, the delivery, the period, or a missing configuration entry. That message is the fastest route to the root cause; work back from it rather than guessing.
The faster way
Cross-system posting failures like this are exactly what SupplyChain Assist is built to reason through — describe the symptom and where it's stuck, and it walks the likely causes with the specific checks for your setup, instead of you working the inbound chain alone or waiting on a support queue.