tmackin
Reputable Poster
We have implemented JDE OW at our facility and are considering bringing up another location. We are looking for feedback on a couple of scenarios we have talked about.
1. Incorporate the new location into our existing production environment.
2. Using our development environment as their production environment.
In the first scenario, we would need to keep all data separate and distinct being that each location has no need to see each other's data. We might like to combine the financial information for reporting purposes, centralize the A/P and A/R functions but keep all other functions separate to each location. How would we accomplish this? Would this be feasible? Is there an easy way via OW security to control access? Do you see any possible problems down the road?
In the second plan, we would sacrifice the development environment and let it become production for the new location. If we went this way, do we have to have a complete set of objects and tables or could we just have tables for the new location and share objects?
I would like to hear from anyone who has implemented multiple locations or has any other comments as to the pitfalls of either scenario. Waht are the pros and cons for each plan? We are a small shop, have no mods to OW, only one software support person. Looking for the best solution to ease the support function. TIA
1. Incorporate the new location into our existing production environment.
2. Using our development environment as their production environment.
In the first scenario, we would need to keep all data separate and distinct being that each location has no need to see each other's data. We might like to combine the financial information for reporting purposes, centralize the A/P and A/R functions but keep all other functions separate to each location. How would we accomplish this? Would this be feasible? Is there an easy way via OW security to control access? Do you see any possible problems down the road?
In the second plan, we would sacrifice the development environment and let it become production for the new location. If we went this way, do we have to have a complete set of objects and tables or could we just have tables for the new location and share objects?
I would like to hear from anyone who has implemented multiple locations or has any other comments as to the pitfalls of either scenario. Waht are the pros and cons for each plan? We are a small shop, have no mods to OW, only one software support person. Looking for the best solution to ease the support function. TIA