Working with Specification Merges

This section discusses:

• Working with Object Librarian Merge

• Working with Versions List Merge

• Working with Central Objects Merge

• Working with Update Language Text Merge

This table explains what happens to the following types of objects if they have been modified by the customer when the specification merge programs run during an upgrade or a cumulative update. The table assumes the JD Edwards EnterpriseOne action and the customer action are on the same object.

JD Edwards EnterpriseOne action	Customer action	Upgrade	Update
An object is modified.	No action.	No action.	Add or replace.
An object is modified.	The same object is modified.	Merge (replaces data structures and applications).	Merge (replaces data structures and applications).
An object is added.	No action.	No action.	Add.
No action.	A new object is added.	Add.	No action.
No action.	No action.	No action.	No action.
No action.	The same object is modified.	Merge.	No action.
An object is deleted.	No action.	No action.	The report should contain a warning. Object Librarian should be updated to product code 88.
An object is deleted	An object is modified	The report should contain a warning, and the object is merged.	The report should contain a warning and the object is not deleted.

See Also

Object Specification Merge Report (R98700) in Working with Reports in this guide for more information about the reports.

For users who are upgrading an alternate language, the merge copies all text for custom objects. For modified JD Edwards EnterpriseOne objects, all changed or added text is copied forward to the new release.

For users who are updating an alternate language, the TAM package contains only base text. The merge replaces central objects base text with base text from the package. Translated text is not removed.