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]

In your case, the HU number already exists in ECC from 2015, so when decentralized EWM tries to post the goods issue back to ERP, the inbound qRFC fails because ERP sees that HU as already “consumed” in a historical delivery. That’s why EWM shows the delivery as completed (because the warehouse task/HU processing finished locally). The outbound queue to ERP is stuck, so ERP’s goods movement status never flips to “Completed”.

• To fix this, go to SMQ1 in EWM, filter by your delivery number or LUW containing /SCWM/… function modules (e.g. /SCWM/ERP_GOODSMVT_OUTBOUND). Display the error text. You should see something like “HU already exists” or “HU already assigned to delivery …”.
• Go to HUMO in ECC, Enter the HU number and check the Status, Assigned document (old delivery from 2015). This confirms the HU number conflict.

So with the above scenario, you have two options.

Option A – Change HU number in EWM
Unpack the item from the problematic HU in EWM.  Create a new HU with a fresh number range (one that does not exist in ERP). Repack the goods and re‑post the goods issue.  This avoids the conflict entirely.

Option B – Clean up HU in ERP
If the old HU is no longer relevant and can be archived/closed, you could technically delete or renumber it in ERP — but in practice, HU numbers are not meant to be reused, so this is rarely recommended in production.

SAP best practice is to ensure separate HU number ranges for EWM and ERP to avoid reuse.

Once the HU conflict is resolved:

Go back to SMQ1 in EWM, select the stuck LUW and choose Execute LUW (or Activate if it’s in SMQ2 inbound in ERP). The goods movement should post in ERP, and the delivery status will update.

[memberju]

Ok thank you so much!

[memberju]

I tried Option B, because Good issue was posted in EWM. And I could not unpack the item from the HU. But now the message "Cancel of Goods Issue not allowed with existing Bill" appears. I think they employee tried to delete the Goods Issue. So the queue is still there (or a new one). Do you know what to do? Thank you in advance!