Merging Configurations, Customizations, and Personalizations Using ADS

The merge provided by Application Data Sets (ADS) framework applies to the merge able attributes and records defined in a data set. The merge property value determines whether the customer value for that attribute or record is retained or not. The merge using ADS takes place when there are modifications on attributes like labels, titles of a pivot grid model provided by Oracle PeopleSoft.

In the secondary merge process the framework provides options which determine the merge behavior for modifications made by the customer. Pivot Grid ADS uses the secondary merge for cases like addition of new dimensions or facts, changing the view options and so on.

See, Lifecycle Management Guide: Application Data Set Overview.

Note:

These examples assume that the user follows the default merge process. After the compare, user has the option to override the merge and accept values for merge-able attributes.

The following scenarios compare the impact on pivot grid objects when you have to merge data between existing application and the application update available using the default merge process or the secondary merge process.

The scenarios describe a customer who is on an application version and how he proceeds for an application update using the ADS framework:

  1. The customer decides to take the new update from PeopleSoft Update Manager (PUM) which includes an ADS project containing the pivot grid update.

  2. He selects the updates he wants and creates a change package in the Change Assistant. If the customer selects an update containing a pivot grid, then the update is included as one of the ADS values.

  3. The customer applies the change package in the target database. The change package with the ADS project has several steps like:

    1. Copy to file.

    2. Compare.

    3. Review.

      In this step the customer reviews the compare reports and overrides actions if required.

    4. Copy from file.

The following sections describe the process and result of an application update in different scenarios where secondary merge is required or not required and changes are applied by application development, customer, or user.

Related Topics