PeopleSoft PUM Update Checklist (Change Package)

0%

0 of 31 items complete

7 critical items still open - these are the highest-risk gaps.

Download checklist:

PUM image

Identify the latest PeopleSoft Update Image for your application (HCM, FSCM, Campus Solutions, ELM, CRM) on the PeopleSoft Update Manager home page in My Oracle SupportCRITICALCheck the PeopleTools level the image requires and that your Change Assistant client matches itDeploy the image as VirtualBox, NativeOS DPK on Windows or Linux, or in OCI with Cloud ManagerConfigure Change Assistant Update Manager settings: PUM source database, download and staging directoriesDefine the target environment in Change Assistant and upload target database information to the imageCRITICALConfirm the image PIA, PUM Dashboard and Update Manager pages are reachable from your workstation

Select updates

In the image PIA, open PeopleSoft Update Manager and select the uploaded target databaseDefine the change package: specific bugs, product or feature updates, or all updates available since your last imageUse the Cumulative Feature Overview tool to review new features between your current and target imageReview prerequisite bugs the package pulls in automatically and accept the full prerequisite setName the change package and record image number, scope and owner in the change logAgree which new features will be activated after apply and which stay off

Analyze

Generate compare reports for the change package objects against the target databaseCRITICALReview objects that are changed both by Oracle and by you, and decide take, keep or merge for eachUse the PUM Dashboard and your customization records to list affected customizationsOptionally run Change Impact Analyzer to find custom PeopleCode and SQL referencing changed objectsRead the change package documentation for data conversion, manual steps and post-apply tasksEstimate retrofit and test effort before committing to the apply window

Apply

Back up the target database before every applyCRITICALApply the change package with Change Assistant to a development copy firstCRITICALRetrofit customizations that the package overwrote, using the compare report decisionsRun data conversion, alter and build steps the package requires and review each logCreate a custom change package that includes the retrofitted objects for later environmentsApply the same package to test and then production in the same order and with the same stepsClear cache, rebuild search indexes affected by the package and compile COBOL if the package includes COBOL

Validate

Run PeopleSoft Test Framework (PTF) scripts for the affected business processesRegression test integrations and batch jobs touched by the packageCRITICALGrant new pages, tiles and service operations on permission lists and test with real rolesRun SYSAUDIT and DDDAUDIT and compare against the pre-apply resultsKeep the rollback path ready: database restore point and a record of every object movedCRITICALGet business sign-off and record the image number now applied on each environment

PUM uses Selective Adoption: you choose what to take from each image. Item names follow PeopleSoft Update Manager PeopleBooks for PeopleTools 8.5x and 8.6x; menu paths vary slightly by tools release.

Scoping your next PUM cycle?

Send us your current and target image numbers and customisation count and we will outline effort and test scope.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How a PUM update works

Oracle delivers application maintenance as PeopleSoft Update Images, full demo databases containing every fix and feature to date. You deploy the image, upload your target database information to it, then use PeopleSoft Update Manager in the image PIA to define a change package of the updates you want. Change Assistant builds the package, compares it to your database and applies it. Because you pick the scope, the work is mostly analysis: which objects change, which of them you customised, and what you must retest.

Image: source of updates, refreshed by Oracle regularly.
Change package: the selected updates plus prerequisites.
Change Assistant: runs compare and apply steps.

Reading compare reports

Compare reports list each object in the package with its status in the image and in your database. The important rows are objects both Oracle and your team have changed: if you take Oracle's version you lose the customisation and must retrofit it; if you keep yours you lose the fix. Record a decision per object before applying to development, and carry the decision into a custom change package so test and production get exactly what development got. Projects with many shared objects are a sign that customisations should be moved to event mapping or other isolation techniques.

Common mistakes

The frequent ones are applying straight to test without a development pass, re-defining the change package for each environment instead of reusing a custom package, skipping prerequisites, and forgetting security for new pages and tiles. Another is letting images age: applying many images of change at once makes compare reports and testing much larger. Many sites set a regular cadence and keep the PTF test library current so each cycle is smaller and faster.

Upload fresh target database information before each cycle.
Keep Change Assistant at the level the image requires.
Document every manual step for the production run sheet.

Frequently Asked Questions

What are the steps for a PeopleSoft HCM PUM update?

Download and deploy the latest HCM update image, upload your target database information from Change Assistant, define a change package in PeopleSoft Update Manager, generate and review compare reports, apply to development, retrofit customisations, create a custom change package, apply to test and production, then test with PTF and sign off.

What is a PeopleSoft compare report in PUM?

It is the report Change Assistant and Application Designer produce comparing each object in the change package between the update image and your target database. It flags whether each side changed the object, so you can decide to take Oracle's version, keep yours or merge, and plan retrofit work.

What is PeopleSoft Update Manager?

PeopleSoft Update Manager is the set of PIA pages in the update image, used with Change Assistant, to search for fixes and features, define change packages for a specific target database and track what has been applied. It replaced the old bundle and maintenance pack process for 9.2 applications.

Is a PUM update the same as a PeopleTools upgrade?

No. A PUM update changes application objects and data for fixes and features within your application release. A PeopleTools upgrade changes the technology layer, binaries and system tables. An update image may require a minimum PeopleTools level, so a tools upgrade sometimes has to come first.

If you want your team to ask what changed in a PeopleSoft change package and which customisations it touches in plain English on your own servers, we can set that up.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

PeopleSoft PUM Update and Change Package Checklist