Exception code HUAD creates HU without document assignment?

[martinprokop]

Hi, I try to use exception HUAD during RF Unloading (Unloading by ASN). System creates (empty) HU at bin, which has to be specified in customizing of the except. code. But this HU is not assigned to the ASN/ inbound delivery - it seems to be independent. What is the standard purpose of this functionality, then? I want to use this functionality in following way:

1. During unloading, create empty HU for every single physically unloaded pallet, without information about its content (something similar, what does the "unknown content HU" functionality, which is planned/created from /SCWM/GRPE, however)

2. Create one dummy collective HU for whole TU and set it to Unld status (post GR for all deliveries in TU)

3. Use Deconsolidation to repack content from collective HU into particular physical HU's - and post possible quantity differences to the original inbound delivery

[martinprokop]

Update: I solved also the "nesting" of unloaded UK-HU to collective HU.

1. Simple by adding a relation entry intable /SCWM/HU_IDENT.

2. Additionally also an entry in table /SCWM/HUREF to record a relation of unloaded UK-HU to TU (relation entry for all assigned inboud deliveries in this TU).

[martinprokop]

Hello Ajit,

thank you for axplaining of original purpose of HUAD to me!

Still, I can't use the standard scenario described in help, because of point 1. mentioned above.
I don't want to create precise number of UK-HU in GUI (/SCWM/GRPE) - I don't know how many are they before thea are physically unloaded. I can predefine their numbers neither - labels will be sticked first when uloading them.
This means I want to create (and label) them during Unloading. Therefore I was lookig for some functionality to create new UK-HU during Unloading. I agree, HUAD exception is not the one.

In meantime I configured new exception, which allows me to create the required UK-HU in Unloading. In Badi SCWM_ES_CORE_PSC I predefine process and process step to enable Unloading at this HU. Confirmed WT is created during Unloading. However, this HU is not nested in the collective HU of the TU and therefore has no connection to the TU/delivery.
I might be totally wrong, but this seems to me a feasible scenario..

[schulte-bahrenberg]

...agree with Ajit. Your scenario fits quite well to the standard scenario of receiving 'HUs with unknown content'. As you mentioned this process I assume that you have explored it before. So what is missing that you decided to use the exception codes instead?

[Ajit_Routray]

Hi Martin.

Use of HUAD - "

• If the HU is assigned to another delivery, the system issues an error message. If you then enter the exception codeHUAD, the system looks for the delivery and splits it correspondingly.
• If you notice upon closing the transaction that a notified HU is missing, enter the exception codeHUMI. The system adjusts the delivery correspondingly, meaning the quantity is corrected correspondingly."

• Copied from Link- https://help.sap.com/saphelp_ewm70/helpdata/en/6c/cbcb53ad377114e10000000a174cb4/frameset.htm

I guess Your Scenario can fulfil. Please check link and configure accordingly. In this link, you could find the unknown content HU movement.

https://help.sap.com/viewer/3d97bec9bf1649099384bb8167df3cf2/9.5.0.2/en-US/0b76e244e8d84d128a7efc4bc...

Deconsolidation (not original SAP EWM Function) is like packing centre, create HU according to Physical HU then Repack as per need.

Please let us know if you have further queries.

Kind Regards,

Ajit