Kevin_Gray
Active Member
Hi List,
We're planning on going live in a couple of weeks. We don't have the traditional environments setups though and I'm trying to get things back on track. We have Dev, Prototype and Production but we created a custom environment that uses the PY7333 pathcode but has a separate database for the Business Data and Control Tables. The reason for the custom environment was for a demo environment after the IT people went to training but instead it was used to setup the Financials. Dev and Protoype was setup for payroll. Production was never used and therefore the JDE_PRODUCTION database is empty and no ESU/ASU's have been applied to that environment.
Here's the dilemma. JDE_PRODUCTION has only 2088 tables. JDE_DEVELOPMENT has 2291 tables and this custom environment has 2226 tables. I want to copy all Business Data and Control tables from this custom Environment to Dev and get rid of the custom environment. Then do a "Mirror Image" of Dev to Prod. This would get all the code of the custom mods and anything new from the ESU/ASU's applied plus the setup data from the Test finance environment, now Dev. One of the project leaders wants to copy just the finance data tables from the custom environment to production and go live from there (thinking that the central objects/version refresh is going to be done prior to). I just don't think that its that easy just because of the missing tables in Prod. I know that ESU's and ASU's now generate tables and indexes and populate tables that they create. I'm just concerned that if we don't do a full business data refresh from our test environment and only copy the selected finance tables that the missing tables created by ESU/ASU's could cause us grief. I tend to think that if ESU/ASU's create tables its to fix issues whether it be for performance or just adding functionality.
Does anyone share my point of view or can anyone let me know the proper way to approach this. I hope this makes sense. I'm trying to keep this post brief, sorry!
Please help!!
Thanks,
Kevin
We're planning on going live in a couple of weeks. We don't have the traditional environments setups though and I'm trying to get things back on track. We have Dev, Prototype and Production but we created a custom environment that uses the PY7333 pathcode but has a separate database for the Business Data and Control Tables. The reason for the custom environment was for a demo environment after the IT people went to training but instead it was used to setup the Financials. Dev and Protoype was setup for payroll. Production was never used and therefore the JDE_PRODUCTION database is empty and no ESU/ASU's have been applied to that environment.
Here's the dilemma. JDE_PRODUCTION has only 2088 tables. JDE_DEVELOPMENT has 2291 tables and this custom environment has 2226 tables. I want to copy all Business Data and Control tables from this custom Environment to Dev and get rid of the custom environment. Then do a "Mirror Image" of Dev to Prod. This would get all the code of the custom mods and anything new from the ESU/ASU's applied plus the setup data from the Test finance environment, now Dev. One of the project leaders wants to copy just the finance data tables from the custom environment to production and go live from there (thinking that the central objects/version refresh is going to be done prior to). I just don't think that its that easy just because of the missing tables in Prod. I know that ESU's and ASU's now generate tables and indexes and populate tables that they create. I'm just concerned that if we don't do a full business data refresh from our test environment and only copy the selected finance tables that the missing tables created by ESU/ASU's could cause us grief. I tend to think that if ESU/ASU's create tables its to fix issues whether it be for performance or just adding functionality.
Does anyone share my point of view or can anyone let me know the proper way to approach this. I hope this makes sense. I'm trying to keep this post brief, sorry!
Please help!!
Thanks,
Kevin