E1: ESU: The ESU Merges Objects for a Pathcode Even When Build Date in 'Sar grouping file for ESUs Table' (F96400.SGESUDM) is Equal to Build Date in 'Software Update Pathcode Information' Table (F9672.SUSUDATE)
(Doc ID 2985652.1)
Last updated on NOVEMBER 13, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
In a particular pathcode, Application Software update or Electronic software updates are merging objects even when the Build Date specified in 'Sar grouping file for ESUs Table' (F96400.SGESUDM) is Equal to Build Date in 'Software Update Pathcode Information' Table (F9672.SUSUDATE).
These software updates should not merge these objects as per E1: ESU: Why Is An Object Changed Or Merged Rather Than Replaced By The Spec Merge UBE R98700? (Doc ID 660444.1).
There are other pathcodes where the same updates are not merging objects.
Steps
- Apply the software update using procedure described in E1: ESU: Overview of Recommended Steps to Apply Software Updates (ESUs and ASUs) - From EnterpriseOne Xe to 9.2 (Doc ID 626353.1)
- Check the Spec Merge Report output for Merged objects
- From UTB, compare value of column SGESUDM in F96400 and value of column SUSUDATE in F9672
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |