Algorithm of Packing and Unpacking a Handling Unit: Part-I
The purpose of this blog is aimed at providing a holistic approach on how to unpack, pack a handling unit in a HU+WM managed location when handling unit is assigned to object like outbound delivery.
It’s been an experience that unpacking or un-assigning the Handling unit from an outbound delivery is inconspicuous to consultants and when standard practice is not followed,inconsistency arise. The blog is written to present a paradigmatic process of un-assigning the handling units from delivery and what are the key mechanism and configuration which drives this
I will replicate a scenario where an error message generally gets triggered ” HUDIALOG107” when Handling unit is tried to be deleted from Outbound delivery.
Generally there are 2 types of Handling units
- Assigned HUs: Assigned HUs are created during packing like in Outbound delivery, production orders, process orders.
- Unassigned HUs( Free HUs)- Handling units which are created without any reference to objects. Free HUs are created HU02.
Recently, i was answering to a question on below thread and that inspired me to write on this topic.
We will take an outbound delivery in which handling unit is already assigned. The HU is packed in a storage location is WM+HU managed.
- I am taking an outbound delivery which has been PGIed(261), WM activity complete
It can be seen that all Picking, Packing, WM activity and goods movement is completed
3) Since the delivery is already PGIed, we need to run VL09 to reverse the delivery.
4) It can be observed that Goods movement status=C, So it is required to reverse the goods movement, then only we can un-assign the Hus
5) Once ODB is reversed, the good movement status is reset
6) In VL03N, goods movement status is updated as below
7) Now, go to VL02N—> pack button, HU02 screen is called and try to unpack the delivery containing Handling unit in total content tab of HU02
8) An error message is triggered as below
Note: Before we try to unpack a handling unit in Outbound delivery, it is obligatory to send Handling unit to an Interim Bin which allows Re-packing. In SAP terminology, 923 is generally used as Re-packing storage type and HUs are moved here only from 914 interim storage type.
Also,when there’s an outbound delivery from HUM and WM storage location, it’s not possible to leave unpacked stock once it has been picked (WM status = C). Since, the outbound delivery is connected to confirmed Transfer order in WM, unpacking in HU managed location will create inconsistency.
In HU-managed storage locations, materials can be managed in HUs only. Mixed stock (stock made up of packed and non-packed materials within the same storage location) is not supported. HUs can also be managed in interim storage types.
9) Since handling unit is an asset which carries some cost, it needs to be manually moved to an storage type which allows repacking
10) If we look into the transfer order of delivery which was created before we cancel the delivery, the Storage Unit( SU) was moved from 866 to 914 interim storage area.
11) So, we will move this HU from 914 interim storage area to 866 destination storage bin. In this case, HU becomes SU in WM. The big difference between SU and HU ist that HUs can also be managed in interim storage types, however, SUs lost its existence in interim storage are.
12) In TO, Handling unit is getting transported from 914 to 866 via LT09. The main purpose of transporting Handling unit assigned to delivery from interim storage area 914 to destination storage was to de-assign HU from delivery so that delivery can be freed from clutches of handling unit.
13) There is an error here which i need to explain. When we try to move HU via LT09, it triggers an error.
According SAP KBA 2201423 – HUDIALOG107, Sap says that with LT09, we need to move the HU/SU to back into it’s original bin. However, we observed that while moving to its original bin, LT09 throws an error which says that the original storage type doesnt not support repacking. My understanding is that SAP needs to correct this KBA 2201423 – HUDIALOG107.
SAP needs to mention that when Handling unit is assigned to an outbound delivery, and when we conduct de-assignment of HU from delivery, the HU needs to be moved to that Storage Type which supports repackaging and there are 3 main condition which needs to be fulfilled while transporting HU/SU from interim storage type.
- Storage type should have no Putaway Strategy.
- Storage type should have no Storage Unit Activation.
- Storage type should have no Capacity indicator set
14) If we look the storage type configuration of 866 and compare with 923(Repacking storage type which generally used from repacking a HU), it can be observed that 866 has Storage type activated, so it disallows HU of getting changed, and hence we were getting error.
So, in nut shell, with LT09, it is required to move the HU/SU to that storage types which doesn’t’ have above 3 fields activated in configuration, No storage,no SU activation and no Capacity indicator set.
15) So, by LT09, HU is moved to 923 interim storage area.
16) Now, try to delete the assignment of HU from delivery as below. (Dont click on delete HU) Handling unit is a technical asset which carries some cost, so delete the Assignment.
17)Once HU assignment is deleted, you will get a message and after saving, HU is free from delivery and it is ready for re-picking.
19) Go to VL02N, it is observed that Delivery qty=picked qty, so it is required to conduct repicking again. So, click on pack button and copy pack quantities as dlv. quantities
20) Once you click and press enter, delivery qty and picked qty are reset to zero, which means Delivery is ready for re-picking again and WM activity can be followed
Hence, the Part-I of this topic ends here. In its sequel, I will explain the how HU once being unpacked moved to partner storage location and what are the key configuration that plays the role. Also how packing from partner storage location via HU02, HU is moved to HU managed storage location and how interim storage types and Bins are determined. All in Sequel.
I would wait for readers response if any necessary corrections are required.