E1: ESU: Understanding and Managing Net Change - Change Management - From EnterpriseOne Xe to 9.1
(Doc ID 626395.1)
Last updated on MAY 30, 2017
JD Edwards EnterpriseOne Tools - Version SP24 and later Information in this document applies to any platform.
***Checked for relevance on 10-Jul-2014***
This document is details the Change Management/Net Change system that ERP 8.0 and Xe use for applying Software Updates and Promoting them using Object Management Workbench. ERP 8.0 and Xe both use an integrated Net Change system. After reading this document, you should have a better understanding of what happens behind the scenes when applying Software Updates. You should have an understanding of how the software uses Net Change to determine which objects will be installed by an Update, and which objects it will not install because they have already been installed by a different Software Update. When you apply a Software Update patch, the change management system logs the BUG/SAR and the Object you installed. When it is recording the installed object, it also records the version of the Oracle JDE object that our Development team has given it. It tracks these "versions" of objects by what is called a Oracle JDE build date. For example, a standard object, like the P4210, can be in multiple Software Updates over the course of time, and each time the newer object contains an additional BUG/SAR, it will have a new build date. This object name, P4210, is stored in a table with the build date. Then, when you apply subsequent Software Updates that contains the P4210, the Change Management/Net Change system compares the build date to see if it needs to install the object. If the P4210 already has a later build date than the P4210 in the ESU, then it will NOT install the object because it has already been installed by a previous Update.
Table of Contents
1. Conceptual Explanation of Change Management/Net Change 2. Net Change Tables Out-of-the-Box 3. Net Change date-fields READ and UPDATED during an ESU or ASU 4. Net Change date-fields READ and UPDATED during the promotion of OMW Projects 5. Change Management date-fields READ and UPDATED during Object Check-in 6. Change Management Summary
Information pertains to all customers installing Electronic Software Updates (ESUs) and/or Application Software Updates (ASUs). This document was originally designed for EnterpriseOne Xe. The process is identical in ERP 8.0 and the terminology can be carried over except the use of Xe. The Net Change - Change Management logic is also valid for later EnterpriseOne application release levels as E1 8.12, 9.0 or 9.1.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!