on 08-20-2012 4:01 PM
Is it a good practice to have seperate number ranges between Storage Units and Handling Units?
As we consider HU however as a heavy application-module, whereby sometimes simple internal SU in a WM can be sufficient.. Like wise we sometimes make use of external Logistic Service Providers which only require a pallet number for shipments, whereby they want to make use of own WM-systems (not requiring us to set up/maintain WM for them).
Thus we have configured in our system:
- locations managed via HU+SU (Storagelocations requires HU, and linked to WM)
- locations managed via SU only (no HU)
- locations where we pack goods in IM via HU (no WM).
Of course when in a warehouse the HU+SU are combined =the same number, of course there are no issues and everything runs fine.
As the number range of HU runs much faster (as it is global) than SU (which is WM-specific), I have my concern to block a certain HU-number range in order to allow those warehouses which donot use HU (only SU) to work 'error-free'.
For those warehouses or IM-locations where we don't combine SU/HU; we do experience that SAP it self esthablishes a link to a HU and a SU number although the material/plant/storage location offers no match. The match is purely based on the number. This is causing issues when differences are to be booked as we are hindered with this undesired SU/HU link.
Is seperating the number range the only answer?
Looking forward to your advice/best practice.
Hi,
May I know if the question still exists or not? If so, please reply it. Thanks a lot.
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.