cancel
Showing results for 
Search instead for 
Did you mean: 

Handling Unit blocked when perform LT06 for good receive

Former Member
0 Kudos

Hi all,

when we performing good receive via LT06, in the "Palletization" tab, upon auto generation of storage unit number by system, the system pops put " Handling unit xxxxxxxx is blocked" when we proceed to create the Transfer order. The material is stuck on movement every time due to transfer order is not able to be created with this error. As alternative solution, we have to manually change the SU number (to other number) in order to proceed.

Not all the storage unit number will encounter blocking, but it happens occasionally. Any reason or cause why is this happening? Any solution for this?

Regards,

Junwei

Accepted Solutions (0)

Answers (1)

Answers (1)

catherine_mckenna
Active Participant
0 Kudos

Hi Junwei,

If the SU is in a HUM storage location, the number ranges should be the
same. If however, it is not but you try to do a posting where there is
a HU with the same value the system will also look at this HU value.

If you have in one client number both storage units that are handling
units and ones that are not handling units, then you must activate
the number assignment for the storage units (non-HU) through the
storage units. This assignment takes place at warehouse number level,
and the assignment of the handling unit numbers takes place for each
packaging material at the client level. The system cannot check the
number ranges. Therefore, when you create the number ranges, make sure
that there are no overlaps between the HU number ranges and the storage
unit number ranges. If there are overlaps here, this can cause stock
inconsistencies in Warehouse Management.

When you are putaway to a bulk storage type with SUM, and you have
specified the SU at the TO creation, the check on both the source and
destination bin is carried out on the TO creation and no further check
is performed at the TO confirmation.

If the source data (SU) is not known at TO creation, then the
destination data will need to be verified at the TO creation, when the
block on the destination bin will be raised.

I hope this information helps.

Kind regards,
Catherine