Here’s some information on the ESU and ASU process, and how JDE determines whether an object should be applied or not.
ESU and ASU decide whether to Replace or Add an object by comparing the dates in F96400 (SGESUDM) and F9672 (SUSUDATE). If the SGESUDM date is later than the SUSUDATE, the object is marked to be replaced.
ESU installation does not check F9861 to decide if the object will be installed.
Note: On 64-bit systems, the REPLACE option has been removed, so only ADD and REPLACE are available.
Example When installing UN9 and checking object will merge or Not.
These SQL after EXE is executed and ESU Application is loaded.
SELECT SUOBNM,SUPKGNAME, SUSUDATE,SUPATHCD FROM JDESY920.F9672 WHERE SUPATHCD='DV920'AND SUOBNM='B9600186';
SELECT SGOBNM,SGESUP,SGESUDM FROM JDESY920.F96400 WHERE SGESUP='UN9' AND SGOBNM='B9600186';
The Object will merge/add/replace as F96400 (SGESUDM ) > F9672 (SUSUDATE)
SELECT SUOBNM,SUPKGNAME, SUSUDATE,SUPATHCD FROM JDESY920.F9672 WHERE SUPATHCD='DV920'AND SUOBNM='B9600186';
SELECT SGOBNM,SGESUP,SGESUDM FROM JDESY920.F96400 WHERE SGESUP='UN9' AND SGOBNM='B9600186';
The Object will merge/add/replace as F96400 (SGESUDM ) = F9672 (SUSUDATE)
E1: ESU: Understanding ESUs Installs - Software Updates (ESUs and ASUs) Under the Covers - Updated to EnterpriseOne 9.0, 9.1 and 9.2 (Doc ID 2388199.2)
E1: ESU: How to Force Merge Objects and/or Re-merge Objects Flagged on Software Update History UBE R96701 PDF as "Not Applied" (Doc ID 790705.1)
E1: ESU: Why Is An Object Changed Or Merged Rather Than Replaced By The Spec Merge UBE R98700? (Doc ID 660444.1)
E1: ESU: Net Change Functionality of Software Updates (Doc ID 651812.1)
