Defining Update Change Packages

The latest PeopleSoft Update Image downloaded from MOS includes the PeopleSoft working database, PeopleTools, applications, managed objects, codeline, and the data and metadata required to use the PeopleSoft Update Manager. The Update Manager PIA interface is used to identify required and desired updates for the change package definition.

The Define Change Package wizard will guide you through the steps to create a change package definition. There are 6 steps:

  1. Select Target Database

    Note:

    The target database is selected from the Select Target Database folder on the Update Manager Dashboard. This page is only displayed when no target databases have been up loaded.

  2. Enter Change Package Name

  3. Select Scope

  4. Select the updates, objects or criteria

    Based on the scope selected in step 3, appropriate page will open to select your updates. If you select All Updates Not Applied in step 3, this step is skipped.

  5. Review Bugs

  6. Done Identifying Bugs

Dependency Calculator

When the user transitions from Step 4 to Step 5 the dependency calculator is automatically executed.

  • The calculator is a PeopleCode Program.

  • If you selected to select by Specific Updates, Updates by Criteria, or Updates by Object Name, the dependency tree is calculated such that  bugs that are Already Applied, and the post-requisites of those same bugs are excluded from the package during the calculation process. Unapplied pre-requisites of applied bugs will, however, be included in the calculated result.

  • If you selected All Updates Not Yet Installed, the calculator will insert all updates that have not been applied in the selected target environment into the results table.

Note:

All requisite updates are specific to and calculated based on the target database. If the change package is reused for another database, Change Assistant will perform a check to ensure all requisites exist. If requisites are missing, you will get an error message.