timhui
Active Member
FYI
Since we need the new functions that are in ERP 8 but not in Xe and that JDE does not want to implement those new functions in Xe, we have to do the ERP 8 Upgrade. After a few weeks¡¯ preparation, we thought we were ready to upgrade our OneWorld Xe based on what described in the J.D. Edwards ERP 8 Upgrade Guide. Therefore, we started our upgrade on 07/31/2002. Well, we are still testing modules in DV and PY today. We are not confident enough to promote the ERP 8 to PD yet.
During and after the upgrade process, we encountered numerous problems. By getting assistances from GSS, we think we have a solid ground for ERP 8 so far.
Because the settings may be different from one company to the others, you may not encounter the same problems we encountered as well.
However, here is something you need to check and correct before you start your ERP 8 upgrade process (from Xe).
1. The ERP 8 Upgrade Guide is similar to Xe Upgrade Guide. You can say that the difference between the ERP 8 Upgrade Guide and Xe Upgrade Guide is the pathcode. The pathcodes for ERP 8 are like DV7334, JD7334, and PD7334 etc, and those for Xe are DV7333, JD7333, PD7333, etc. The rest is almost the same.
Beware: The numbers of those estimated space required for each environment (pathcode) and each database on the Deployment server and the Enterprise server are those for Xe. ERP 8 needs more than what Xe needs. For example, the estimate required space for each pathcode on SQL server stated in the ERP 8 Upgrade Guide is 2.2 GB but actually it needs 3.2 GB per pathcode. The pathcode here means JDE_DV7334, JDE_JD7334, etc. The JDE7334 database on SQL server needs 470 MB, instead of 320 MB. ERP 8 shares the same data databases with Xe. That means JDE_DEVELOPMENT, JDE_CRP, JDE_PRODUCTION, etc. are shared between ERP 8 and Xe. However, there are lots of tables changed in ERP 8 so, once you upgrade an environment to ERP 8, that environment in Xe will work right anymore.
2. Before you start the upgrade process, check your Specification Merge Selection (GH9611, P98401) for each environment from a fat client. The one you see on the deployment server is for JDEB7 on the deployment server. The one you should check is the one in your database (JDE7334). Unless you have to preserve those JDE objects with your custom codes, make sure the flags of those objects in other than SYS 55 to SYS 59 are blank in all environments. Please check out the JDE document, OTM-02-0025, at the Knowledge Garden. And make sure all your custom objects assigned to from SYS 55 to SYS 59. Otherwise, they will be assigned to SYS 88 and will not be pulled over from Xe to ERP 8.
3. During the ERP 8 Upgrade process, DO NOT use Microsoft NetMeeting application to monitor the progress of the upgrade process running on the Deployment server, especially at the Spec Merge stage. You may be able to use MS NetMeeting before and after the Spec Merge process but not suggested.
4. You have to do this step manually after the ERP 8 Upgrade process complete successfully. The upgrade process does not create new tables in your database server. There is a new table for Payroll/HR, F073521, you need to create it manually in all environments. Otherwise, your payroll process will be erred out.
5. If you would like to have the menu tabs in ERP 8, you need to download and apply the JE1213 ESU. P00820 is marked as an obsolete object and did not bring over from Xe. After you apply this ESU, you will have this object and be able to create menu tabs.
Good luck to anyone out there planning to do the ERP 8 Upgrade from Xe.
--Tim
Since we need the new functions that are in ERP 8 but not in Xe and that JDE does not want to implement those new functions in Xe, we have to do the ERP 8 Upgrade. After a few weeks¡¯ preparation, we thought we were ready to upgrade our OneWorld Xe based on what described in the J.D. Edwards ERP 8 Upgrade Guide. Therefore, we started our upgrade on 07/31/2002. Well, we are still testing modules in DV and PY today. We are not confident enough to promote the ERP 8 to PD yet.
During and after the upgrade process, we encountered numerous problems. By getting assistances from GSS, we think we have a solid ground for ERP 8 so far.
Because the settings may be different from one company to the others, you may not encounter the same problems we encountered as well.
However, here is something you need to check and correct before you start your ERP 8 upgrade process (from Xe).
1. The ERP 8 Upgrade Guide is similar to Xe Upgrade Guide. You can say that the difference between the ERP 8 Upgrade Guide and Xe Upgrade Guide is the pathcode. The pathcodes for ERP 8 are like DV7334, JD7334, and PD7334 etc, and those for Xe are DV7333, JD7333, PD7333, etc. The rest is almost the same.
Beware: The numbers of those estimated space required for each environment (pathcode) and each database on the Deployment server and the Enterprise server are those for Xe. ERP 8 needs more than what Xe needs. For example, the estimate required space for each pathcode on SQL server stated in the ERP 8 Upgrade Guide is 2.2 GB but actually it needs 3.2 GB per pathcode. The pathcode here means JDE_DV7334, JDE_JD7334, etc. The JDE7334 database on SQL server needs 470 MB, instead of 320 MB. ERP 8 shares the same data databases with Xe. That means JDE_DEVELOPMENT, JDE_CRP, JDE_PRODUCTION, etc. are shared between ERP 8 and Xe. However, there are lots of tables changed in ERP 8 so, once you upgrade an environment to ERP 8, that environment in Xe will work right anymore.
2. Before you start the upgrade process, check your Specification Merge Selection (GH9611, P98401) for each environment from a fat client. The one you see on the deployment server is for JDEB7 on the deployment server. The one you should check is the one in your database (JDE7334). Unless you have to preserve those JDE objects with your custom codes, make sure the flags of those objects in other than SYS 55 to SYS 59 are blank in all environments. Please check out the JDE document, OTM-02-0025, at the Knowledge Garden. And make sure all your custom objects assigned to from SYS 55 to SYS 59. Otherwise, they will be assigned to SYS 88 and will not be pulled over from Xe to ERP 8.
3. During the ERP 8 Upgrade process, DO NOT use Microsoft NetMeeting application to monitor the progress of the upgrade process running on the Deployment server, especially at the Spec Merge stage. You may be able to use MS NetMeeting before and after the Spec Merge process but not suggested.
4. You have to do this step manually after the ERP 8 Upgrade process complete successfully. The upgrade process does not create new tables in your database server. There is a new table for Payroll/HR, F073521, you need to create it manually in all environments. Otherwise, your payroll process will be erred out.
5. If you would like to have the menu tabs in ERP 8, you need to download and apply the JE1213 ESU. P00820 is marked as an obsolete object and did not bring over from Xe. After you apply this ESU, you will have this object and be able to create menu tabs.
Good luck to anyone out there planning to do the ERP 8 Upgrade from Xe.
--Tim
