EWM - Delete Handling Unit when adding to existing Handling Unit - Putaway strategy

[ewmguy11]

Hello SAP expert,

I have the following situation. I have a storage type (RL05) for a rack storage. Most important settings for the storage type are:

• Putaway rule 2: Addition to Existing Stock/Empty Bin
• HU requirement X: HU is required
• WT Generic 2: Only Storage type is suggested by the system (the workers in the warehouse want to choose the bin by themself...)
• Mixed storage/Mixed storage in HUs: no restrictions
• Level Add. to Stock H: Addition to Stock at Highest HU Level

Rest of the settings see screenshots:

 

To the case:
For example I have the HU 810000167 with a quantity of 1 ton of the product 1000000058 on the bin RL05-01-01-01-03. 

Then I get a new inbound delivery of the same product (or also another product) with maybe 0,5 tons and I want to put those 0,5 tons to the existing HU 810000167 and throw away the Handling Unit where the 0,5 tons were on. We are working with Handling Units 100% of the time and create the Handling Units already in the delivery with the Fiori App. And when doing the putaway to the existing HU, I get of course a nested Handling Unit. 

New inbound delivery with warehouse task of the product:

Confirm the warehouse task in the foreground to the existing HU 810000167 which is already on the bin:

Then the stock looks like this on the bin with a nested Handling Unit:

Is there a way to set up the system to delete the Handling Unit when adding it to another HU so I avoid that a nested Handling Unit is created?
What I would like to have as a result is only the HU 810000167 with a quantity of 1,5 tons. 

Thanks in advance!

[nn1]

I discovered that this only works when the WT is confirmed via RF. When confirming via backend the HU always gets nested.

[schulte-bahrenberg]

...looked at this topic also. I think these are the options that you have:

- putaway WT is a product WT: change destination HU via exception code CHHU (source HU will be deleted automatically)

- putaway WT is a HU WT: change destination HU via exception code CHHU and unpack the source HU via an implementation of Badi /scwm/ex_core_co_unp_outhu 

How to control the creation of product vs. HU WT was already mentioned in other comments below I think - won't repeat that here. 

Hope that helps!

Regards,

Hendrik