Understanding PUM Automated Merge

Beginning with PeopleTools 8.59.02, Change Assistant supports object merge for PeopleCode, SQL and XSLT objects in your Customization Repository.

When you enable object merge in Change Assistant and upload customizations to the PUM source, the data for the PeopleCode, XSLT or SQL objects will be included in the merge repository.

If Object Merge is enabled and a change package is created that contains merge enabled objects, the merge rules are used to automatically merge the code.

The merge session contains three sets of data:

• Parent (A) Data - This is the previous versions of data delivered in the PUM source database.

• Child 1 (Customization) Data - This is the data uploaded by user to the customization repository on the PUM source database. 

  See Uploading Customer Data to Image.

• Child 2 (Delivered) Data – This is the data delivered in the PUM source database.

Note that in the initial Change Package create process, Change Assistant exports Object Merge project only with the metadata that is required for the Change Package create process. After running the object merge, the entire project is exported.