on 05-24-2011 4:16 PM
Hi All
We currently have 2 warehouses and 2 plants but are discussing combining the warehouses so that one warehouse will feed 2 plants.
Directly procured parts will still be delivered directly to the separate plants
What are the possible pitfalls in combining the 2 warehouses?
What master data settings will cause the biggest problems
Thanks in advance
Darren
I recommend to follow the physics.
Do not combine 2 warehouse that are located apart from each other, even it is technically possible.
If it is just one physical warehouse which was splitted into two because of 2 plants, then combine it.
One warehouse means, theat the data in WM1 and WM2 is not anymore individual to a specific warehouse as it is right now
Further, the users have always to enter the plant if they create TOs manually, which was not the case with individual warehouses per plant.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jurgen
Many thanks for the response.
WM1 and WM2 material master views will not be a problem as we do not use any Storage Strategies or Palletization settings in either plant and the General data is pretty much standard between the plants/warehouses.
The issue I can see is with the manual generation of the TOs. This is something that we do frequently and all the warehouse staff have their plant PID'd which is something we will have to remove.
SO Master Data is not an issue but its processing demand from the 2 separate plants is going to be an issue.
Also, we will have no traceability of parts picked in the central warehouse and then put on a truck and delivered to a plant serveral miles away
Thank you for your info Jurgen.
Darren
User | Count |
---|---|
99 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.