E1: ESU: Installation Procedures Promoting ESUs For Each Pathcode - Superceded ESUs / Special Instructions - Recommendations - Baseline ESUs (Doc ID 628097.1)

Last updated on JULY 28, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Checked for Relevance on 06-06-2011





Goal

Scenario 1 - Procedures Promoting ESUs For Each Pathcode and Recommendations

Customer first followed the procedures of downloading and installing a Baseline ESU onto their Development Server for the DV pathcode, followed by performing the necessary Special Instructions for pre and post package builds, package build and deployment of the objects contained in the OMW project created, to the enterprise server and clients.

The project was then advanced from status 21 to 26 (project transferred to PY pathcode) and all the Special Instructions were followed for the PY pathcode and all its environments as well as a package built and deployed to PY for the Enterprise server and clients.

The project was then advanced to 28 and then 38 (objects are moved into production) and all the steps were followed for Special instructions as well as package built and deployed to PD for Enterprise server and clients.

The questions are to do with pulling down subsequent ESU's dependent on the Baseline in respect to all pathcodes:

Scenario 2 - Applying and Promoting ESUs Procedures - ESU superceded versions - Special Instructions

This is a procedural question regarding applying Baseline ESUs. Customer applied first a Baseline ESU to their Development environment. Then, they applied a second small update ESU dependent from the Baseline ESU to the Development environment as well. There were problems with some of the applications involved, so they have applied a third update ESU, which actually is a superceded version of the 2nd update ESU installed.
Now customer is ready to apply these ESUs to their Prototype environment. They usually apply their ESU to PY environment without the spec merge, and then promote the project with the objects from DV to PY.

The questions are:

1. Since the 3rd ESU they applied to DV was a superceded version of the 2nd ESU they applied, can they just apply the Baseline and the 3rd ESU to their PY and PD environments, OR does customer still need to apply the 2nd ESU like they've done did in DV environment?

2. Since customer promotes the objects from each ESU in DV to the other environments, do they still need to do all the ESUs Special Instructions - pre and post package instructions - in each environment?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms