Copyright © 2015 WorkStrategy, Inc. All rights reserved.

Using the PeopleSoft HCM 9.2

PUM for Upgrades and

Maintenance UpdatesBrian McIntyre, President

WorkStrategy, Inc.

2

WorkStrategy Webinar Wednesdays

Upcoming Webinars

• April 01 PeopleSoft 9.2 Recruiting Solutions (TAM/CG)

• April 08 PeopleSoft 9.2 Enterprise Learning Management (ELM)

• April 29 Upgrading to PeopleSoft HCM 9.2 and PUM Overview

Upcoming Conferences

• Mar 25 Oracle HCM World (Wash D.C.)

• April 12 Collaborate (Vegas) Booth #742

• June 8 OHUG Global Conference (Vegas)

• July 21 PeopleSoft RECONNECT (Chicago, IL)

• Oct 25 Oracle OpenWorld (San Fran, CA)

3

WorkStrategy Profile

• HR Technology Firm Based in Columbia, Maryland

• Staff of HR Practitioners and Oracle / PeopleSoft HCM Specialists

• Oracle Gold Level Implementation Partner

• eComp Manager Desktop Co-Development Partner

• PeopleSoft and Talent Management Specialists

• Talent Profiles, ePerformance, eComp, Recruiting, and Succession

• 9.2 Upgrade Planning and Lab Services

• Oracle HCM Cloud (Fusion Talent/Comp, Taleo)

• Integrated PeopleTools Bolt-ons

4

New PeopleSoft Application Portal

peoplesoftinfo.com

5

New Cumulative Feature Overview (CFO)

6

CFO Results with Related “Images”

7

New 8.54 Fluid Mobile Transactions

Major upcoming ESS/MSS Mobile applications include:

• Employee Self Service:

o Company Directory, Personal Details, Talent Profile, ePay, Payslips, Time

Entry, Performance, Learning (ELM), eBenefits, Total Rewards

• Manager Self Service:

o Company Directory, Approvals, My Team, Team Time, Team Learning, Team

Performance, Team Performance Status (Analytic), Open Jobs (Recruiting),

Learning Compliance, Absence Analytics

• Youtube Video of HCM Fluid UI

o http://www.youtube.com/watch?v=ds5z_HJdj-I&feature=youtu.be

8

Fluid Mobile ESS Applications (Tablet View)

• Requires PeopleSoft HCM 9.2.09 and PeopleTools 8.54

9

Fluid ESS – Benefit Summary

10

Fluid ESS – Life Events

11

Fluid ESS – Life Events Activity Guide

12

Fluid Mobile ESS (Smartphone View)

13

Fluid ESS – Benefits Summary

14

Fluid ESS – Benefits Life Events

15

Fluid ESS – Benefits Enrollment

16

Fluid ESS – View Balances & Requests

17

Fluid ESS – Personal Details

18

Fluid ESS – Personal Details (Update Marital Status)

19

Fluid ESS – ePerformance

20

Fluid MSS – Team Performance (ePerformance)

21

Fluid MSS – My Team

22

Fluid MSS – Team Performance Status (Analytics)

23

PUM Training Videos

24

PeopleSoft Lifecycle Management

25

PeopleSoft Update Manager (PUM)

• Recently defined as PeopleSoft Selective Adoption approach

• Oracle's new process for delivering PeopleSoft fixes, updates, and new features

• Minimum release 9.2/8.53

• Consists of Oracle’s VM VirtualBox that runs on most major operating systems

• The Virtual Machine is loaded with a PeopleSoft Image (file) that contains a

complete PeopleSoft Demo database with all the latest fixes

• PeopleSoft fixes (known as Maintenance Packs and bundles) can be searched for

and “packaged” together, then applied to a Target database

• PUM Images are used with Change Assistant for upgrading and applying

maintenance updates

26

New PS Update Manager (PUM) Homepage

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1641843.2

27

PS HCM Update Image Patches & Updates

28

Certified PUM Upgrade Image 009 (from < 9.2)

29

Download the Upgrade Image (.zip files)

30

PUM Image 9.2 Image 009 Fix/Features “Content List”

31

PUM Setup Timeframe Guidelines

Task Time Comment

Download Virtual Machine

Software

1 hour Download from https://www.virtualbox.org

Download the PeopleSoft Image (PI) 4 – 5 hours Ten or more large GB files. Download from

MOS PeopleSoft Images Home Page

Create Single Image File from

Downloaded PI Files

1 – 2 hours Final Image file approximately 35 – 40 GB

Configure and Start PI 1 – 2 hours May need assistance from networking staff

Estimate Total 2 days

32

Start by Downloading Oracle’s VirtualBox

33

Go to My Oracle Support (or PUM Home) and Select Image

34

Review PUM Image Details

35

Download Image

36

Multiple Files (.ova) Are Downloaded

37

Run ova_gen.bat Utility to Group .ova Files

38

Upload the Image File to the VirtualBox Appliance

• Click “Import” from the VirtualBox File Menu to Import the Image File

39

Configuring CA Output and Staging Directories

40

How Change Assistant and PUM Interact

• Change Assistant (CA) setup for

an Upgrade or Update includes

setting up a connection to the

PUM Image and the Source and

Target databases

• Once a Change Package is

created by the user, CA

downloads the package

41

Change Package Wizard

42

Change Package Wizard – Define Change Package

43

Change Package Wizard – Select Updates

44

Change Package Wizard – Select “Find” link

45

Search for Maintenance Update (e.g. Tax Update)

• Scroll down to the “Review Candidate Bugs” section and click the “Find” link.

Enter “14-A” and click OK. The purpose here is to exclude all of the updates

concerned with Tax Update 14-A. Repeat the “Find” process until no more 14-A

tax update related bug numbers are found. (In PI images 1- 5 there are three

related 14-A tax updates).

46

PS PUM Change Package Wizard – Review Candidate Bugs

47

PS PUM Change Package Wizard – Review Bugs

48

PS PUM Change Package Wizard - Summary

49

PS PUM Change Package Wizard – Review Change Packages

50

From CA, Locate the Created Update Package

51

Change Assistant Creates the Change Package

• Click the Finish button. CA will create the Change Package. A “Processing…”

dialogue box is displayed showing the progress of package creation. A zip file will

be created in the CA download folder

52

Change Package Download

• Change Assistant downloads the package to the Change Assistant download

directory configured earlier

53

Apply Change Package

54

CA Will Process Change Package Steps

55

Patchsets

• Additional fixes available on My Oracle Support (MOS) posted after the Image was

released

• Additional Change Assistant steps are provided to apply these to the PUM Image

56

Using PUM for Upgrades vs. Updates

• The chart below summarizes the use of the PUM for Upgrades versus Updates.

For an Upgrade two PUM images are used, an Upgrade Image and a regular

Update Image. Once the upgrade is complete additional fixes can be packaged

and installed from the Update Image.

Upgrade Update Comment

Set up PUM as usual Set up PUM as usual Follow PUM Install/Config Documentation

Use Update Image to Create

Change Package of “Required

for Install/Upgrade” Patches

only

Create Change Package of

desired bug fixes or

updates

Use one of the search options in the PUM web

application to find the desired patches

Use Change Assistant to

download and install the

Change Package

Use Change Assistant to

download and install the

Change Package

Change Assistant installs the package

Use Upgrade Image as the

Source for initial database

upgrade

The Change Package itself

becomes the Source for

subsequent database

updates

Change Assistant is used to apply the

upgrades/updates in either case

57

Applying Payroll Tax Updates

• Payroll tax updates are now

downloaded and applied via the PUM

• Select the tax update(s) (e.g. Tax

Updates 14A through 14D) from the

PUM image and create a change

package

• Change Assistant will install the

package to the Target database

(typically a Development Database)

• Any reapplication of customizations or

other needed fixes are reapplied to the

original Tax Update project

Posting Month PS 9.2 Image Tax Updates Included

June, 2013 1 13-A

August, 2013 2 13-B, 13-C, 13-D

October, 2013 3 13-E

December, 2013 4 13-F

January, 2014 5 14-A

March, 2014 6 14-B

June, 2014 7 14-C

August, 2014 8 14-D

October, 2014 9 14-E *

December, 2014 10 14-F *

January, 2015 11 15-A

58

Applying Payroll Tax Updates

• Change Assistant (CA) creates a modified

change package

• The modified change package becomes the

Source for subsequent application to other

databases including the production

database

• In an upgrade, issue resolution fixes during

testing are placed in project files and

applied back into the Source database for

the next upgrade. However, Tax Update

fixes are added back into the original tax

update project file and CA creates a

modified change package.

• The modified change package becomes the

Source for the next upgrade. There is no

Source database, the modified change

package is the Source.

14-F10December, 2014

Document

1917096.2

14-E9October, 2014

Document

1913205.1

14-D8August, 2014

Document

1676641.1

14-C7June, 2014

Document

1623091.1

14-B6March, 2014

Document

1609474.1

14-A5January, 2014

14-F10December, 2014

Document

1917096.2

14-E9October, 2014

Document

1913205.1

14-D8August, 2014

Document

1676641.1

14-C7June, 2014

Document

1623091.1

14-B6March, 2014

Document

1609474.1

14-A5January, 2014

59

Oracle’s Virtual Machine VirtualBox Issues

• Oracle’s VM VirtualBox software for the

PeopleSoft Update Manager (PUM) is not

designed to work on other Virtual

machines such as VMWare

• Hardware Virtualization cannot be set in

the VirtualBox when the host server is

itself a Virtual Machine

• It may be possible to work around the

issue, but none of them are supported by

Oracle

• A physical server is needed for the PUM

• The PUM server should have at least 8 GB

of RAM. Provide at least 100 GB of disk

space per PeopleSoft Image configured on

the server

60

Quick Tips for Challenges Experienced Using PUM

Challenge 1

• During tax update, Change Assistant failed to download all of the files such as

SQRs, COBOL, etc.

• Resolution: Had to go back through the process of creating a tax update change

package and downloading it again before getting it to work

Challenge 2

• During tax update, Change Assistant applied a tax update project file to the Target

database. Discovered later that Change Assistant did not copy all the objects in the

project to the Target

• Resolution: The solution was to apply the project manually (via Application

Designer) to the Target database

61

PUM Technical Resource Requirements

• A single technical resource can complete all of the steps involved in installing,

configuring and conducting the PUM updates

• Other technical resources may be needed for configuring a physical server and any

networking issues

• The technical resource should be well versed in using Application Designer and

Data Mover, as well as have good troubleshooting skill

• The technical resource should allocate at least a week the first time setting up and

using the PUM

62

Customer Case Study – Application Inventory

• PS HCM 9.0 / PT 8.53.08 upgrade to PS HCM 9.2 / PT 8.53.11

• Applications

o Human Resources / Workforce Administration

o Base Benefits / Ben Admin / eBenefits

o Self Service

―ESS (eProfile)

―Manager (highly customized)

o Time & Labor (highly customized)

o NA Payroll

o ePay

o eDevelopment

o Talent Acquisition Manager (TAM) (not in use)

o Candidate Gateway (not in use)

63

Customer Server Environments

• Two AIX Database Servers

o 1 Production - Oracle 11g RDBMS

o 1 Development – Oracle 11g RDMS

• Three MS Windows 2008 R2 PeopleSoft Application Servers (PT 8.53)

o 1 Production

o 1 Development

o 1 Backup – not currently used

• Six MS Windows 2008 R2 PeopleSoft Web Servers (PT 8.53)

o 4 Production

o 2 Development

• Two MS Windows 2008 R2 PeopleSoft Batch Servers (PT 8.53)

o 1 Production

o 1 Development

64

Customer 9.2 Upgrade Timeline

Project Phase Timeline Deliverable

Project Planning 3/10 – 3/14 Tailored Project Plan w/ Resources

PeopleSoft 9.2 Delta and Upgrade

Analysis

3/20 – 4/01 9.2 HCM Delta Delivery and Completed Upgrade

Analysis

Initial 9.2 Upgrade 4/07 – 6/18 Upgraded Database

Acceptance Testing 6/16 – 7/16 Acceptance Test Completion

Test Move to Production 7/14 – 7/18 2nd Upgraded Database

Acceptance Testing 7/21 – 8/06 Acceptance Test Completion

Test Move (For Timing Only) 8/04 – 8/08 3rd Upgraded Database

Final Move to Production 8/30 – 9/01 Production Signoff

65

Other Customer Upgrade Issues with the PUM

• Oracle’s VM VirtualBox software for the PeopleSoft Update Manager (PUM) is not

designed to work on other Virtual machines such as VMware

• Customers had to procure a physical server for the VirtualBox software install

• Took additional time (4 weeks) to procure and configure the server

• Tax Update Process vs. Upgrade Process Using PUM

o Similar, except no Source database for the Move to Production

o Initial Custom Project is applied to Target database

• A few Payroll Tax Update issues with PUM

o All objects were not copied to the Target database

66

9.2 Upgrade Steps

67

Upgrade Lab: Compares and Scripts

(1) Not included in Upgrade Lab

68

Key Project Deliverables and PUM

• Load PUM and download Virtual 9.2 HCM Image (e.g. 9.2.xxx)

• Use as “demo” database

• Upgrade Analysis

o Delta Overview

o Documentation of 9.2 functionality, decisions, and best practices

• Upgrade Lab

o Compare spreadsheets

o Upgraded HCM 9.2 database

o Current HCM 9.2 demo database

o Customization analysis with disposition decision

o 2 Test upgrade passes (clean up scripts, timings)

• Customization Reapplication

• Additional Upgrade Passes

o Test Move to include remaining critical customizations

o Another Pre-Final Move to capture timings only

• WS on-site assistance during acceptance testing

• WS on-site for the Final Move to Production weekend

69

Project Management Used

• Weekly Status Conference Calls

• Daily Check-ins

• Republish Project MPP

• Project Health Checkups

• Open Issues Log, Escalation

• Electronic Versions of All

Deliverables

• Informal Communication

• Weekly Reviews of Milestones

Against Project Schedule

• Risk and Readiness Assessments

70

9.2 / 8.53 Upgrade MS Project Plan

71

PeopleSoft 9.2 HCM Upgrade Analysis

After 9.2 Upgrade FastTrack

• Review current vs. future state requirements

• Summary of PUA findings

• Build project plan for 9.2 upgrade – plan and schedule

Client Tasks (provide to WorkStrategy)

• Wish list of desired 9.2 functionality

• Demo 9.2 HCM database

• List of known customizations

• Dates for target environment readiness

WorkStrategy Deliverables

• Assessment of upgrade impact on existing functions, transactions, processes

• Definition of new 9.2 functionality and process improvement

• Review of Compare Report results (if available)

• Analysis of implementation effort

• Documentation of decisions, challenges, and recommendations

Upgrade

Steps

Reapply

ModsTesting

Upgrade

Analysis

Move

To Prod

72

Upgrade Analysis Results

73

Change Assistant – PS Object Compares

74

Converted Raw Compare Data to WorkStrategy Tool

75

Lab/Onsite Script Timing

76

Streamlined Scripts

77

• Review peoplesoftinfo.com

• Review PUM Homepage

• Review PeopleBooks, YouTube videos

• Install and view the 9.2 demo image

• Call WorkStrategy for 9.2 demos

• Get WorkStrategy’s Project Plan

Brian J McIntyre

President

brian.mcintyre@workstrategy.com

410.707.3760 cell

Amber Drenner

Marketing

amber.drenner@workstrategy.com

410.715.1020 x112

Brian J McIntyre

President

brian.mcintyre@workstrategy.com

410.707.3760 cell

Amber Drenner

Marketing

amber.drenner@workstrategy.com

410.715.1020 x112