Applying Change Package That Includes Merge-Enabled Objects

When merge-enabled objects are included in a change package, additional steps will be present in the Change Assistant job template to perform the automatic merge.

The new steps will perform the following update actions:

  1. Running the Merge Analysis Process-IP

    This step will run the merge analysis process in the initial pass for mergeable objects included in the current change package. The merged code is stored in staging tables.

  2. Backing Up Source Objects Prior to Merge Promotion

    This step will run Copy to File for existing (delivered) objects from PUM source prior to merge promotion. This file is used to restore the PUM Image to it’s original (pre-merge) state after the merging process is complete.

  3. Running the Merge Promotion Process-IP

    This step will run in the initial pass to promote the staging tables to the PUM Source tables.

  4. Exporting Change Package MO Project from Source

    This step creates a project with the merged code that is exported back into the change package.

  5. Restoring Source Objects After Completing Merge

    This step runs the Copy from File to restore the PUM delivered objects from the backup created in the step Backing Up Source Objects Prior to Promotion.

  6. Running Compare of Vanilla Object Project

    This step compares the PeopleSoft delivered version of the objects that were merged to the target database. These secondary compare reports can be used for additional reference when reviewing the primary compare results which compare the Merged versions of the mergeable objects to your target database.

  7. Updating the Project Actions for Merged Objects

After the Managed Object compare is run, you can review the compare reports which will show how the code was merged.

Note: If the merge steps fail, you can view the Merge Session to resolve any issues. See Viewing PUM Automated Merge Sessions.