Steps of applying ESU in P96470

Applying and Promoting Software Updates (ESUs and ASUs)

This process of applying and updating Software Updates (ESUs and ASUs)  is designed to encompass all ESUs and Updates of all sizes. The process for Applying all Software Updates (ESUs and ASUs) should be similar to this:

1. Download the Software Update into its own directory.

2. Check with the documentation for any Tools Release or ESU or any other as prerequisites.

3. Update Software Update Log if you maintain one. This was discussed above.

4. Extract the Update (if it is a planner ESU, make sure you back up the /Planner/Spec and /Planner/Bin32 directories BEFORE running Setup.

5. Check what Control Tables and other merges are going to run . You can verify that by looking at the Software Updates P96470 application, [Work with Software Updates] form, Row Menu - "Update Schedule" button. Refer to Document 1318978.1 E1: ESU: Understanding ESUs Installs - Software Updates (ESUs and ASUs) Under the Covers - Updated to EnterpriseOne 9.0 - for more details, and afterwards take the necessary preparations.

6. Go into Software Updates P96470 application, select the Update, click next, select the Pristine environment, PS900 and choose the "Affected Objects" exit bar button. (This is assuming that you have applied the same software updates to Pristine that you have applied to DV900, which is our recommendation).

7. Complete a thorough examination of what objects will be affected by this update.

8. If, after your Impact Analysis results, you decide to apply the Software Update, then make sure you have the made the necessary backup precautions in accordance to an emergency recovery plan that you have created.

9. Apply the Update to PRISTINE.

10. Perform Special Instructions.

11. Build a package in Pristine, if this is part of your process.

12. Prepare to Apply to DV900. Use the functionalities of the "Affected Objects" application to verify that no projects have tokens for any of the objects in the Software Update. If there are projects, then you will want to communicate with the development team to make sure changes are not overwritten. Then, make sure all development is checked in for the object in the Update. Make sure all of the tokens are released for the objects affected by the Software Update.

13. Make sure all "Affected Objects" that have been modified are marked to be Merged in the Specification Merge Selection application with a " C " and a " 1 ". Refer to Document 660444.1E1: ESU: Why Is An Object Changed Or Merged Rather Than Replaced By The Spec Merge UBE R98700? - for more information on Specification Merge Flags.

14. Apply the Software Update, in its entirety, to the DV900 environment.

15. Perform any retrofitting necessary and check objects back in.

16. Perform Special Instructions.

17. Build and deploy a package.