SU and HU number overlap

[Former Member]

Hello Experts,

we have encounter error message "HU XXXX is not in a HU managed location" in our cycle count (LX26)

we found that this is due to HU and SU number range overlap and we can change the HU number range to prevent future issue.

what we needs your help to answer are:

1. for existing SU that already had this issue, does it mean we can't use that number in the future?

2. how can we find all these SU being affected?

Thanks for all your help in advance

Regards,

Fu Qiang

[balaji_ganesan2 · Accepted solution]

Hello Fu,

Definition of SU and HU number ranges that overlap. Please find below an excerpt of the IMG documentation for SU number range definition (path LE-> WM -> Storage Units -> Master Data -> Define number ranges) which warns against such issue:

"If, in a client, you have storage units that are also handling units, and SUs that are not handling units, then you must use storage unit number assignment for the storage units that are not HUs. You assign

these numbers at warehouse number level. THE SYSTEM CANNOT CHECK THE NUMBER RANGES AGAINST EACH OTHER. Therefore,when you create number ranges YOU MUST ENSURE THAT THE NUMBER RANGES FOR THE HUS AND FOR STORAGE UNITS DO NOT OVERLAP. Any overlaps in these number ranges can lead to inconsistencies within Warehouse Management."

To resolve this issue for existing ones, you could move the SU out of the storage type and putaway a new one after the number ranges have been updated.

Thanks,
Balaji

[Former Member · Accepted solution]

Thank you so much for your answer, Balaji.

just double check if my understanding is correct. to solove this issue, what we should do is actually a SU to SU transfer right? we move the stock out of the impacted SU and move them to new SU which number is not overlap after changing the number range.

This will involve a lot of physical movement in warehouse but its necessary, right?