There is already a handling unit * posted for GR without stock HUSELECT005

[memberju]

Hello everyone,

during a delivery in decentralized SAP EWM with ECC, a delivery was successfully picked and packed. However, it seems that a Handling Unit (HU) that originally existed in 2015 in ERP was recreated in EWM now. During the goods issue posting, the status shows as completed in EWM, but the queue is stuck and the goods movement status in ERP has not been updated to completed.

In the HU Monitor (HUMO), I can see that this HU from 2015 was packed with a material and was already shipped via delivery back in 2015.

Question:
What steps can I take to resolve this issue so that the queue is processed correctly and the goods movement status in ERP is updated?

Thank you! 🙂

[Lakshmipathi · Accepted solution]

Go to SMQ2 in ERP, find the LUW from EWM for this delivery. Display the error text. You should still see the HU conflict message unless you have already cleaned up the HU in ERP.

If you have already deleted/archived the old HU in ERP, make sure it is really gone from HUMO and not assigned to any historical document. If you can’t delete it (archiving restrictions), the only safe fix is to repack in EWM into a different HU number and re‑trigger the GI message. Even though EWM shows GI posted, you can still use /SCWM/PRDO to unpack/repack into a new HU. Then use /SCWM/POST to re‑post the GI. This will create a new queue to ERP.

“Cancel not allowed” in ERP" is coming from SD because a billing document exists for the delivery. If the billing document is not yet posted to accounting and can be cancelled, reverse it via VF11, then reverse the GI in VL09. If the billing document is already posted and cannot be cancelled, you cannot reverse the GI in ERP.  You must instead fix the posting from EWM so that ERP receives a successful GI message.

If EWM says GI posted but ERP does not, you have a status mismatch. To fix:

Option 1: Cancel GI in EWM (/SCWM/POST → Reverse GI), repack into a new HU, then post GI again so the new queue posts cleanly in ERP.

Option 2: If reversal in EWM is blocked because ERP never posted GI, you can use the queue reset approach. In SMQ1 (EWM outbound), delete the bad LUW. Manually post the GI in ERP (VL02N/VL06O) after fixing the HU number. Then manually set the delivery to completed in EWM (via PPF action or status update).

Finally, and importantly, separate HU number ranges between EWM and ERP so old ERP HUs can never be reused in EWM. Train users not to attempt GI reversal in ERP for EWM‑managed deliveries — always reverse in EWM first.