ID 2235545.1 Oracle HCM Cloud Checklists For Upgrading From Release 11 To Release 12 v3

Oracle HCM Cloud: Checklists for Upgrading
from Release 11 to Release 12

ORACLE WHITE PAPER | MAY 2017
Table of Contents
Introduction 1
Upgrade Approaches 1
Five Phases of Project Management for an Upgrade 2
Evaluate: Overview 2
Areas of Focus 2
Expected Outputs 2
Activities 2
Evaluate: Checklist 3
Plan: Overview 4
Areas of Focus 4
Expected Outputs 4
Activities 4
Plan: Checklist 5
Configure: Overview 6
Areas of Focus 6
Expected Outputs 6
Activities 6
Configure: Checklist 7
Test: Overview 8
Areas of Focus 8
Expected Outputs 8
Activities 8
Test: Checklist 9
Rollout: Overview 10
Areas of Focus 10
Expected Outputs 10
Activities 10
Rollout: Checklist 11
To Do Lists 12
Release 12 Upgrade Planning Checklist 14
FAQs 16
A Final Note 26
Introduction
This white paper helps ensure that you complete all the tasks for a successful upgrade. Follow the step-by-step
instructions in the upgrade planning checklists to track and plan the Release 12 upgrade. These checklists are
designed to provide advanced planning information. Release 11 customers may choose to use this information to
plan future solutions as they are enhanced.
It is crucial to develop a release plan to ensure a smooth transition from old technology to new. For some
localization customers, upgrade is essential to meet compliance requirements.
Further resources that you can consult before you upgrade:

All White Papers for Fusion Applications HCM (Doc ID 1504483.1) for Products, Tools and Localizations
o Oracle Applications Cloud Service Entitlements (Doc ID 2004494.1)
o Oracle Fusion HRMS (US): Payroll Reconciliation (Doc ID 2086251.1)
o Oracle Fusion HRMS (CA): Payroll Reconciliation (Doc ID 2170948.1)
o Oracle Fusion HCM (UK): Payroll Reconciliation (Doc ID 2133313.1)
o Setting Up and Migrating UK Statutory Absences (Doc ID 2235239.1)
o Oracle Learning Cloud : Master Article (Doc ID 2158160.1)
Release Upgrade Planning
o Oracle Applications Cloud - Release Upgrade Planning (Doc ID 2016981.1)
o Release Updates on Customer Connect or Oracle Help Center
o Oracle HCM Cloud Functional Known Issues - Release 12 (Doc ID 2223760.1)
o Oracle Applications Cloud - Release Upgrade Planning (Doc ID 2016981.1)
o Oracle ERP Cloud: Performing Your Release 12 Upgrade (Doc ID 2220217.1)
o Oracle HCM Cloud: Performing Your Release 12 Upgrade (Doc ID 2231259.1)
o Oracle HCM Cloud Release 12 Impact Assessment (Doc ID 2248540.1)
Security
o Creating Custom Roles for OTBI Reporting Access in Release 12 (Doc ID 2262948.1)
o Upgrading Applications Security in Oracle HCM Cloud Releases 12 (Doc ID 2023523.1)
o Release 12: Pre-Upgrade Activity if Customized Predefined Roles (Doc ID 2210187.1)
o Using the Oracle Fusion Applications Security Console (Doc ID 1946961.1)
o Cloud Application Security Architecture and Configuration: Role Privileges (Doc ID 2022454.1)
o Audit Reports in Fusion Application (Doc ID 2210883.1)
Upgrade Approaches
You must evaluate your business priorities versus resource availability in order to determine how to plan your
upgrade. Common approaches are:
Technical Upgrade only. Strictly upgrade. No feature uptakes are included and you validate the deployed
business processes in Release 11 continue to work after the upgrade. The intention is to defer adoption of new
features and products to post-upgrade new project initiatives.
Technical Upgrade and Light Features Uptake. Upgrade, plus minimal feature uptakes, for example,
localization changes, or additional language install.
Technical Upgrade and Features Uptake. Upgrade, plus key product complete features uptake, for example,
Oracle Fusion Applications Security Console, and Person Spotlight.
1 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

Five Phases of Project Management for an Upgrade
Consider dividing your upgrade project into phases for optimal outcome, making it easier to manage and monitor.
The following model has been used during upgrades by many customers and is considered a best practice:
Evaluate Plan Configure Test Rollout
Evaluate: Overview
This phase aims to:
Evaluate the added functions and features in the new release, taking core and future business
requirements into account
Explore possibilities to improve user experience, efficiency, and effectiveness
Examine browser and operations enhancements, with an emphasis on improving client response time
Areas of Focus
Understand value and enhancements in Release 12, see Release Updates

Highlight process changes and improvements
Gauge potential business impact of an upgrade
Begin to define an upgrade strategy, including your Managed Cloud if any
Confirm upgrade schedule via My Services
Estimate upgrade efforts
Communications with parties concerned upstream and downstream
Expected Outputs
Risk and mitigation measures for upgrading to Release 12
Business impacts:
o Expected benefits for the business
o Expected costs (resources, time, impact on co-existence etc.)
Entry/exit criteria
Activities
1. Agree upon upgrade schedule, including CloudOps tasks such as P2T/T2T, language packs, pod re-
sizing, etc. See Lead Time tab on Release 12 Upgrade Planning Checklist.xlsx.
2. Review product enhancements. See Release Readiness, Training, Events on Customer Connect.
3. Contemplate configuration management. See R11 PRE-UPG To Do Lists.
4. Review performance and scalability improvements.
5. Review potential environmental impact.
6. Review add-on localizations and/or languages.

Evaluate: Checklist
# Activity / Action by Decision (if applicable)

1 Define an upgrade strategy, including your Managed
Cloud, Taleo Recruiting if any
2 Arrange upgrade schedule via My Services
3 Arrange Cloudops requests such as P2T/T2T,
language packs, pod re-sizing etc.
4 Review product enhancements
5 Contemplate configuration management, see R11
PRE-UPG To Do Lists against the upgrade instance
6 Review performance and scalability improvements
7 Review potential environmental impact
8 Review add-on localizations and/or languages
9 Upgrade impact assessment inc. upstream and
downstream
10 Risk and mitigation plan
11 Business benefits realization
12 Each instance entry/exit criteria

Plan: Overview
This phase aims to: Formulate the upgrade project, including the project management details from roles and
responsibilities to testing.
Areas of Focus
Project resource planning
Upgrade plan and timelines
Prepare test scope and iteration
Assessment of end-user impact re: change management
Establish issue resolution process
Expected Outputs
Detailed upgrade plan:
Project organization and governance
o Test plan including regression testing, language testing, and integration testing
o Resource allocation and task assignments
Projected timeline with built-in milestones and contingency plans
Activities
1. Consider impact on user learning materials.
2. Define testing strategy and testing flows.
3. Identify training needs.
4. Address impact on 3rd party components and interfaces.
5. Articulate defect/issue resolution process
6. List of milestone deliverables.
7. Define milestone checkpoints.
8. Project kickoff session.

Plan: Checklist

1 Project plan
2 Consider impact on user learning materials
3 Define testing strategy and testing flows
4 Identify project teams training needs
5 Address impact on 3rd party components and
interfaces
6 Issue resolution process
7 List of milestone deliverables
8 Define milestone checkpoints
9 Project kickoff session
10 Business change communications: about the upgrade

Configure: Overview
This phase aims to: Further develop and validate an end-to-end upgrade project plan, focusing on the technical
aspects of the upgrade and configuration of components. Configuration steps include integration testing, ensuring
that components fit and function together seamlessly.
Areas of Focus
End-to-end assessment online/offline process steps
Release 12 changes activate/disable new features
Validation against system administration setup enable/disable notification
Expected Outputs
An upgraded Release12 test environment available for various testing work streams i.e. Business
Functional/Languages, HCM Data Loader, Extracts, Payroll Interfaces, Reporting
Specific upgrade changes to be noted for the next pod upgrade/test iteration
Entry criteria met
Activities
1. Design decisions.
2. Configuration changes and migration methods.
3. Complete post-upgrade technical/functional steps. See R12 POST-UPG To Do Lists.

Configure: Checklist

1 Design decisions
2 Configuration changes and migration methods
3 Complete R12 POST-UPG To Do Lists against the
upgraded instance
4 Update project plan
5 Document instance-specific upgrade changes for the
next upgrade/test iteration
6 Test team training
7 Test scripts & target testing population

Test: Overview
This phase aims to cover:
Quantitative testing procedures
Functionality validation
Enterprise Scheduling Service (ESS) process validation
Integration validation
Business and technical requirement validation
Defect discovery and regression testing
Areas of Focus
Functional
HCM Data Loader, Extracts, Payroll Interfaces
System performance
Referential data validation
Reports & Analytics
Upgrade patch/bug fixes escalation
Expected Outputs
System performance baseline
Testing progress status/results
Decision to execute full test iteration
Go/No-go Decision to proceed to Rollout or return to Plan/Configure stages
Activities
1. Verify post-upgrade technical/functional changes. See R12 POST-UPG To Do Lists.
2. Check outstanding REL12UPG SR, bug ETAs and patching schedules.
3. Validate upgrade is successful.
4. Consolidate changes for user learning materials.

Test: Checklist

1 Verify post-upgrade technical/functional changes, see
R12 POST-UPG To Do Lists
2 Check outstanding REL12UPG SR, bug ETAs and
patching schedules
3 Validate upgrade is successful
4 Consolidate changes for user learning materials
5 Instance performance baseline
6 Testing progress status/results
7 Decision to execute full test iteration
8 Go/No-go Decision to proceed to Rollout or return to
Plan/Configure stages
9 Review production pod upgrade schedule
10 Promote configuration changes to production instance
11 Business change communications: upgrade progress
12 End user learning activities

Rollout: Overview
This phase aims to: Apply the refined project plan for the upgrade from Release 11 to Release 12 to the Production
environment.
Areas of Focus
Replication of specific test iteration, on Support/Parallel Production instance
Basic checks of business flow and data quality
Post-upgrade monitoring of production system
Expected Outputs
System/user documentation finalized
Production system finalized
Activities
1. Configuration migration.
2. Examine exit criteria regarding readiness to upgrade production.
3. Communication to Oracle via My Services to confirm production upgrade.
4. Support/Parallel Production instance refresh to start immediately after production goes live.
5. Smoke testing the upgraded production pod.
6. Sign-off on the Release 12 production upgrade.
7. Document lessons learned.
8. Project closure.

Rollout: Checklist

1 Review exit criteria re: readiness to upgrade
production
2 Confirm production upgrade via My Services
3 Support instance P2T refresh & Email/Pwd reset
4 Smoke testing the upgraded production instance
5 Sign-off Release 12 production upgrade
6 Business change communications: upgrade
conclusion with known issues and instance release to
end users
7 Document lessons learned
8 Project closure
9 Post-upgrade monitoring notion

To Do Lists
If your project is part of a pilot program live in prior release and has a few features to uptake in Release 12, focus on
the following To Do Lists to fast track your upgrade.
R11 PRE-UPG Key Actions Helpful Tips
Prepare for R12 Release 12: Pre-Upgrade Activity if Read the pre-upgrade section of the Oracle Human Capital
security upgrade customizations made to the Simplified Management Cloud Security Upgrade Guide, see Doc ID
Reference Role Model, see Doc ID 2023523.1
2210187.1 Also read HCM Common What's New, this covers the security
enhancements that have been made in R12
Choose dates for Self-service request via My Services Stage to upgrade on Tuesdays whereas Production(Prod)/Parallel
R12UPG Prod on Fridays (Thursdays for Middle East)
Schedule P2T/T2T via My Services
(first come first o replay Scheduling Rel12 Upgrade on Customer Connect
served)
If project in midst of implementation phase, consider upgrade
Stage and Pre-Prod in the same week
If customer is live and has one Stage one Parallel Prod,
consider upgrade Prod/Parallel Prod in the same week and
P2T immediately after
o see Doc ID 2015788.1 for Environment Refresh
o see Doc ID 1632261.1 for P2T/T2T Guidelines
o see Doc ID 2108681.1 for Taleo/HCM Cloud Refresh
o see Doc ID 2173513.1 for new environment with refresh
o see Doc ID 2092389.1 for Data Masking
If customer is on Quarterly Patching Cadence (be aware of the
longer refresh blackout period), consider all Rel11 pods to
keep the same so to focus on R12UPG testing
If customer is on R12 Quarterly Patching Cadence, based on
post-upgrade bug status, customer can log SR at least 11
days prior to the first Friday of the month to switch to monthly
o see Doc ID 1966109.1 for applications update policy
Environment Custom Data Masking via HDL Scramble production confidential data, eg. Grade, Salary, etc
Readiness
Activate Single Sign-On (SSO) on stage Re-activate Single Sign-on on stage for testing
o see Doc ID 2100578.1 for SSO Enablement
Regression test security and connectivity between Fusion
HCM and Taleo Recruiting
o see Doc ID 2120646.1 for Integration Connectivity
o see Doc ID 2108705.1 for SSO Integration
Scope of UPG Testing Plan and prepare new test scripts Review functional known issues/workaround
o See Doc ID 2223760.1 for Release 12 HCM Cloud
Release 12 Upgrade Planning Checklist for uptake actions:
Business flow (see column M)
Profile option values (see column Q)
Security roles and function privileges (see column R)
Navigation path (see column S)
Decision on Priority Order (U), Reimplement (V), Must Uptake
(W), Consider Hiding (P) based on columns (F/G/ H/L)

R11 PRE-UPG Key Actions Helpful Tips
Configuration Freeze Backup Before P2T or T2T if Gold instance
Change Freeze Production changes, for example customization,

configuration, and data fix script to freeze prior to P2T/T2T
Publish Sandbox (never attempt to Import R11 Sandbox to
R12)
o see Doc ID 1510578.1 for Composer migration
o see Doc ID 1510288.1 for Flexfields migration
o see Doc ID 1905704.1 for FSM migration best practice
o see Doc ID 1510580.1 for HCM Extract Definition migration
Prepare backups in both target and source instances
o see Doc ID 1581294.1 for archiving BI custom reports
Cease all ESS jobs in source instance for upgrade to start
o see Doc ID 1467664.1, Doc ID 2206441.1 for details
R12 POST-UPG Key Actions Helpful Tips
Perform R12 security Identifies changes to predefined roles Read the during and post-upgrade section of the Oracle
post-upgrade steps and privileges Human Capital Management Cloud Security Upgrade Guide,
see Doc ID 2023523.1
o How Roles are Migrated, pp.18
o New, Updated, and Deleted Roles and Privileges, pp.36
o Run Required Processes, pp.47
Manage user lifecycle via Security o Validate User Lifecycle Settings, pp.49
Console o Update Custom Roles for Goal Management, pp.60
o Update Custom Roles for Profile Management, pp.63
o Provide Access to Areas of Responsibility Pages pp.67
o Identifying and Regenerating HCM Data Roles, pp.72
Re-enable Menu Human Resources Dashboard Or move contents to Infolets

Items
Manager Resources Dashboard
Tools Download Desktop Integration Installer Re-install ADFdi correct version on client
Enable Offerings Enabling Offerings and Functional Select enable for implementation checkbox
Areas
Enabling Features Features and Feature Choices
Specific Person Mapping Extended Lookup Codes Export Lookup tables to excel to detect custom changes
Lookup Types
Service Requests REL12UPG triage process Tag the SR with prefix in the Problem Summary field, eg.
REL12UPG:POD:GHR:NULLPOINTER EXCEPTION ERROR DURING
POD = instance name
NEW PERSON HIRE
On-going Uptakes Announcement: (Monthly) Update - Specifically, this communication lists the products that release
Visibility into New SaaS Functionality new functionality in the last 30 days.
Review the updated New Feature Summary and What's New
for the recent changes. Read Revision History first.

Release 12 Upgrade Planning Checklist
This worksheet is designed to help you prepare your upgrade scope of work. Download the Release 12 Upgrade
Planning Checklist including FEB monthly updates.xlsx (see attachment) and decide what you need for this
upgrade.
Details in columns A-C/Q-T are taken from the Whats New document, and columns P/U-AB are for customer use.
Note: Alter the use of customer columns or create additional columns to suit your needs.
Figure 1. Easy ways to scope out your upgrade.
How to use this planning checklist.xls:

Step 1 Ignore. Mark any products not in use and localizations with a Yes in column Y. Next, open the filter for
column Y, uncheck Select All, and check Blanks.
Step 2 Prioritize.
Must Uptake. Mark with a Yes in column W for localization statutory updates. Next, open the filter for
column W, uncheck Select All, and check Blanks.
Postpone. Mark with a Yes in column X for very desirable features and somewhat desirable features that
can be deferred. For example, if your 2018 Flexible Benefits Program Open Enrollment is to start in the
month of December, then deploy the Benefits new features at a later stage. Next, open the filter for column
X, uncheck Select All, and check Blanks.
Re-implement. Open the filter for column L, uncheck Select All, and check Y. Mark with a Yes in column V
for highly desirable features including Business Intelligence. Clear all filters.
Consider Hiding. Open the filter for column F, uncheck Select All, and check Y. Next, open the filter for
column Y, uncheck Select All, and check Blanks; mark with a Yes in column P if relevant. Repeat the same
against column X. Clear all filters.
Open the filter for column X/Y, uncheck Select All, and check Blanks. Prioritize core products in column U with
the order of 1, 2, or 3. Clear all filters.
Step 3 Estimated Efforts. Open the filter for column U, uncheck Blanks. Enter estimated efforts in days or hours
in column Z.

Step 4 Create PrivotTable. Select the range and select New Worksheet.
Download the sample Release 12 Upgrade Planning Checklist.xlsx (see attachment) to see how the PrivotTable
helps you formalize scoping decision.
Note: Inputs are fictional.
Figure 2. PrivotTable indicating the scope and efforts.

FAQs
Action Required: Enterprise Scheduler Service (ESS) Jobs Must Complete Prior to Maintenance /
Upgrade / P2T Refresh
It is a good practice to cease any scheduled ESS jobs before the start of planned maintenance. See Doc ID
2212493.1 for further technical guidance.
REST API for Oracle HCM Cloud Release 12

In Release 12, HCM REST resources are granted to reference privileges, then to the reference job roles. See
Oracle Help Center for Required Roles and Privileges. Note that many of the HCM REST APIs are still controlled
availability in Release 12.
Manage Data Access for Users

The new Data Security Model Manage Data Access for Users only impacts ERP/SCM customers. It is not
relevant to HCM or CRM implementation.
Warning: Import Users and Roles Application Security Data job has not been run successfully in the last
6 hours. Schedule the Import Users and Roles Application Security Data job to synchronize updated
data.
Verify setting for Hours Since Last Synchronization Job Run Warning via (N) Tools > Security Console >
Administration (T).
Post-P2T Production Email Reset / Mass Password Reset

The SR-based service entitlements are being deprecated and replaced with functions now supported via the
Security Console.
Use HDL worker.dat to alter business entity PersonEmail, preferably a generic mailbox for stage
testing.
Run ESS job Send Personal Data for Multiple Users to LDAP to synchronize accounts with LDAP, for
those users whose information has changed.
Self-service Password Reset or reset Automatically generate password for the testing population via
User Accounts.
Translation Editor
Available to FSM Manage%Lookups% tasks, you can now directly enter the translation on the same page. Use
profile option FND_TRANS_EDITOR_LANGS to limit languages shown in the pop-up, example US,JA,KO no ZHS.

Release 12 Schema, table and columns
See Tables and Views for Oracle HCM Cloud.
Simplification of 3 Tier Employment Model

Employment Model Simplification offers new customers with 2 Tier only employment model, see following three
options:
2 Tier Multiple Assignment
2 Tier Single Assignment
2 Tier Single Contract Single Assignment
No impact to customers already went live on 3 Tier employment model.
Any project under implementation using 3 Tier employment model should consider early switch to 2 Tier option.
For future phased roll-out, live customers should conduct feasibility study in 2 Tier option for new countries/legal
entities and 3 Tier employment model at enterprise level.
See Choosing the Correct Employment Model in Release 12: Frequently Asked Questions (Doc ID 2261187.1)
Changes from Extensible to User for Specific Person Lookup Types

User customization level lookup tables provide customers with full ability to modify the delivered values whereas
Extensible customization level lookup tables allow partial modification, such as display sequence, meaning, and
description. If customers change seeded lookup values/tags, ownership will be transferred to the customer and
Oracle will no longer update these changed values. In other words, only those modified rows will be locked and are
skipped by the next Seed Data patching. Never delete a seeded lookup code; you can disable it by deselecting the
Enabled flag. Enter a service request if you require technical assistance.
Figure 3. Following table shows which actions are permissible.
Action User Extensible System
Deleting a lookup type Yes No No
Inserting new codes Yes Yes No
Updating start date, end date, and enabled fields Yes No, unless the code is customer entered data No
Deleting codes Yes No, unless the code is customer entered data No
Updating tags Yes No No
Updating module Yes No No
Oracle delivered data means LAST_UPDATED_BY = SEED_DATA_FROM_APPLICATION.
Post-upgrade, you can export below tables to excel for comparison. Mapping the extended lookups is not required if
there are no changes made to these User customization level lookup tables:
Figure 4. Post-upgrade lookup tables
Customization Level: User Customization Level: System
CONTACT ORA_PER_CONTACT
MAR_STATUS ORA_PER_MAR_STATUS
PER_HIGHEST_EDUCATION_LEVEL ORA_PER_HIGHEST_EDUCATION_LEVE
PER_NATIONAL_IDENTIFIER_TYPE ORA_PER_NATIONAL_IDENTIFIER_TY
PER_ETHNICITY ORA_PER_ETHNICITY
PER_VISA_PERMIT_TYPE ORA_PER_VISA_PERMIT_TYPE
Can I load date-effective data using HCM Spreadsheet Data Loader?

You can create date-effective business objects. You can also update date-effective person and assignment data
using HCM Spreadsheet Data Loader.
You cannot delete nor correct date-effective data using HCM Spreadsheet Loader.
See Release Training HCM Spreadsheet Data Loader (video).

What are the supported DBIs (database items) and UE (user entity) for HCM Extracts in Release 12?
The list REL12_Entity_Attribute_Spreadsheet contains only UE name (not the route name or query) which will be
used to create Data Group and the DBI which will be used to create Attribute in the extracts:
The output contains the route name and query: REL12_DBI_ROUTE.xls
The output contains lists all of the database items in addition to the list of all the Module Name, their
corresponding User Entity and Database Item Group: REL12_DBI_Spreadsheet.xls
The output contains the UE and DBI: REL12_Entity _Attribute_Spreadsheet.xlsx
Obsolete suffix was added to signify should not use these UE/DBI's in Extract, mainly due to performance issues
see (column D) ENTITY_DESC, (column E) ATTRIBUTE_NAME of REL12_Entity_Attribute_Spreadsheet
If live customer is aware of those obsolete DBIs in production and experiences no issue, then do nothing
New extracts should not use obsolete DBIs
How to trouble shoot when DBI seems not retrieving the correct value?
DBI not retrieving correct values depends on the Extract hierarchy. UE/DBI used and such query can be obtained
from user entity pop-up or view user entity details UI.
What Talent DBIs are enabled for use in Fast Formulas in Release 12?
Goal Management: download REL12_TalentDBI_HRG_HcmGoalCore.xls
for person context DBIs, search for prefix HRG_PER
Performance Management: download REL12_TalentDBI_HRA_HcmPerformanceCommon.xls
for person_id, assignment_id context DBIs eligibility rule usage, search for prefix _FF_
for DBIs specific to an evaluation and participant to be used in fast formula type "Performance Rating
Calculation", search for prefix _FC_
cannot be used in eligibility rule
in the calculation rule, name of the return variable must be L_RETURN_VALUE, numeric only
Profile Management: download REL12_TalentDBI_HRT_HcmProfileCore.xlsx
for person context DBIs, search for prefix HRT_PERSON
Is there a way to audit Performance Eligibility batch processes in the past?

Use following BIP query:
SELECT *
FROM fusion_ora_ess.request_history
WHERE definition = 'JobDefinition://oracle/apps/ess/hcm/performance/setup/DocEligibilityProcessJobDef'
AND product = 'HRA'
AND application = 'EarHcmEss'
ORDER BY requestid DESC

Payroll Upgrade Regression Testing
There are two assumptions for this section. Customers are following the practice noted in the Payroll
Reconciliation white paper for the respective localizations - specifically around reconciliation on a per payroll run
basis. The other assumption is, before the upgrade, the stage was refreshed with a recent copy of production
data.
As part of the post upgrade testing, please follow the payroll reconciliation white paper as regards Pay Period
Balancing. You should use following reports to compare your payroll run results as to what were calculated
before the upgrade. Based on the last payroll results in your upgraded pod, run these sets of report and they
should match the output from the production pod. A match indicates that the reports in Release 12 are working
properly and are consistent with their Release 11 output.
After you validate that, then roll back last payroll run and re-execute it. While you normally would not roll back a
payroll, since there is potential related performance overhead associated with such actions, rolling back a payroll
and re-executing it allow you to test the main payroll processes and help ensure you get consistent results that
you got from when you ran it in your production environment. You can use the SQL scripts from this document to
track the execution of these processes.
Run your Payroll Reconciliation Reports again to compare and contrast results. Results either should be the
same or differences explainable by some new features or functionality. Since the results can be quickly
compared to the report you submitted previously, you should be able to complete this task with ease.
Now that you have confidence that the processes and report are working as expected, you can move forward in
executing the next payroll cycle. This step can be challenging if you are dealing with large volumes of data, such
as a retail organization, so you may want to try and get as many element entries captured, or decide what is
reasonable that you want to validate, and load the data before you execute the next pay period. Include all the
delivered and custom post payroll process steps you normally perform in a payroll cycle, among other custom
processes. You want to make sure all these are in good working order post-upgrade. Also, reconcile this payroll
run using the payroll reconciliation document as your guide.
Check if any special payroll runs that you want to incorporate to verify the application performs as intended,
example add a holiday bonus run to your R12 test plan. This will help address any issues that may arise, and you
would be better prepared for that run by focusing more on the business process.
In addition to reconciling the payroll runs from above, make the effort to reconcile your Month, Quarter (primarily
for the US) and Year-to-Date balances. The payroll reconciliation white paper documents what you should use to
manage this reconciliation activity, to get a feel on what your numbers will look like come that point in time. You
should not put off this activity (in fact you should have a plan in place by when those numbers should be
reviewed), so get a preview of what the numbers are on your upgraded R12 environment.
Step1: Run the Payroll Reconciliation Process for Pay Period Balancing. Upon successful completion of
the payroll process, use these reports to reconcile the payroll:
Gross-to-Net Report
Payroll Activity Report
Statutory Deduction Register
Payroll Register Report
Payment Register Report
Step 2: Run the Payroll Reconciliation Process for Year End Balancing. Upon successful completion of
the payroll process, use these reports to reconcile the payroll:
Gross-to-Net Report
Payroll Activity Report
Statutory Deduction Register
Payroll Register Report
Payment Register Report
End-of-Year Register

A flow instance submitted that the task threw an error
Use following BIP query to:
1.1 Determine Flow Task Instance (also Flow Instance Name) Status
Check the start and end times of the schedule
Check the ESS job status/logs for the scheduled job
SELECT fti.status,
fti.flow_task_instance_id,
ft.base_flow_Task_name,
pc.checklist_name,
pr.call_type,
pr.call_id
FROM pay_flow_Task_instances fti,
pay_flow_tasks_vl ft,
pay_checklists_vl pc,
pay_requests pr
WHERE fti.flow_instance_id =
(SELECT flow_instance_id
FROM pay_flow_instances
WHERE instance_name = 'FLOW_INSTANCE_NAME')
AND fti.base_flow_task_id = ft.base_flow_task_id
AND ft.base_flow_task_id = pc.base_flow_task_id
AND fti.flow_task_instance_id = pr.flow_task_instance_id
AND call_type IN ('ESS','FLOW_ESS')
1.2 Find out the status of the ESS Job
SELECT requestid,
state,
username,
error_warning_detail,
executable_status
WHERE requestid = <CALL_ID>
1.3 Checklist Instance and Flow Task Instance Status

SELECT
fi.instance_name,
pc.checklist_name,
pci.worklist_id,
pci.status checklistStatus, fti.status flowTaskInstanceStatus, fti.flow_task_instance_id
FROM
pay_flow_instances fi,
pay_flow_task_instances fti,
pay_checklist_instances pci
WHERE
fi.flow_instance_id = pci.flow_instance_id
AND fi.flow_instance_id = fti.flow_instance_id
AND fti.base_flow_task_id = pc.base_flow_task_id
AND pc.base_checklist_id = pc.base_checklist_id
AND pci.base_checklist_id = pc.base_checklist_id
AND fi.instance_name = 'FLOW_INSTANCE_NAME'

1.4 Flow Task Interactions
select (select flow_task_name from pay_flow_tasks_vl where base_flow_task_id =

from_flow_task_id) as from_node ,
(select flow_task_name from pay_flow_tasks_vl where base_flow_task_id = to_flow_task_id)
as to_node
from pay_flow_task_interactns
where base_flow_id = (select base_flow_id from pay_flows_vl where base_flow_name =
'BASE_FLOW_TASK_NAME')
1.5 Basic Flow Task Instance Status
select fti.flow_task_instance_id,
fti.status,
ft.flow_task_name
from pay_flow_tasks_vl ft,
pay_flow_task_instances fti
where fti.base_flow_task_id = ft.base_flow_task_id
and fti.flow_instance_id = (select flow_instance_id from pay_flow_instances where
instance_name = 'FLOW_INSTANCE_NAME')
1.6 Check if the flow was submitted with the correct set of parameters
select fp.parameter_name,pv.flow_param_value, fp.default_val,fp.default_type,

fp.base_flow_parameter_id from
pay_flow_instances fi,
pay_flows_vl f,
pay_flow_parameters_vl fp,
pay_flow_param_values pv
where f.base_flow_id = fi.base_flow_id
and fp.base_flow_id = f.base_flow_id
and pv.flow_instance_id = fi.flow_instance_id
and fp.base_flow_parameter_id = pv.base_flow_parameter_id
and fi.instance_name = 'FLOW_INSTANCE_NAME'
1.7 Check what parameters were evaluated for the Flow Task Instance
select tp.element_name,
ftp.default_type,
ftp.default_val,
ftpv.flow_Task_param_value
from
pay_flow_Task_parameters_vl ftp,
pay_flow_Tasks_vl ft,
pay_task_parameters_vl tp,
pay_flow_task_param_vals ftpv,
pay_flow_task_instances fti
where ftp.base_flow_task_id = ft.base_flow_Task_id
and ftp.base_flow_Task_id = fti.base_flow_Task_id
and tp.base_task_parameter_id = ftp.base_Task_parameter_id
and ftpv.flow_Task_instance_id = fti.flow_task_instance_id
and fti.flow_Task_instance_id = <FLOW_TASK_INSTANCE_ID>
and ftpv.base_flow_Task_param_id = ftp.base_flow_Task_param_id

1.8 Access ESS Parameters
SELECT name,value FROM fusion_ora_ess.request_property WHERE requestid =

<CALL_ID>
Submitted a report and navigated to the process and reports tab for the view results icon but to no avail.
Able to independently run the report and see the output from the BI server though.
2.1 Find the url for the BI report that was submitted
Check what the report generated
Through the url to verify if the report has generated output or not
SELECT value
FROM FUSION_ORA_ESS.request_property
WHERE requestid IN
(SELECT requestid
WHERE requestid IN
(SELECT call_id
FROM pay_requests
WHERE flow_instance_id =
WHERE instance_name = 'FLOW_INSTANCE_NAME')
AND call_type= 'BI_OP')
)
AND name = 'bip.status_url'
Use this query to get the BI url for payslips where you want to view what is passed to the DOR:
SELECT value
FROM FUSION_ORA_ESS.request_property
WHERE requestid IN
(SELECT requestid
WHERE absparentid IN
(SELECT call_id
FROM pay_requests pr, pay_flow_instances fi
WHERE fi.flow_instance_id = pr.flow_instance_id
and fi.instance_name = 'FLOW_INSTANCE_NAME' and pr.call_type = 'FLOW_ESS'
))
AND name = 'bip.status_url'

2.2 Check the status of the BI job
if the query did not return a value then the BI job was not submitted, check your delivery option
configuration
BI job failed and the callback was unable to register the url details in ESS, check the error
condition
if the report did generate successfully but the UCM server was down, then flows were unable to
upload the generated output to the attachment server, please raise SR for technical assistance
SELECT state,
error_warning_message,
error_warning_detail
FROM fusion_ora_Ess.request_history
WHERE parentrequestid =
(SELECT call_id
FROM pay_requests
WHERE flow_instance_id =
WHERE instance_name = 'FLOW_INSTANCE_NAME'
)
AND call_type = 'FLOW_ESS'
)
2.3 Check Payslip Request Id(CALL_ID)

Verify if a payslip was generated in the BI server, but was unavailable to the worker
select requestid from fusion_ora_ess.request_history where parentrequestid =
(select call_id from pay_requests where flow_instance_id = (select flow_instance_id from
pay_Flow_instances where instance_name = 'FLOW_INSTANCE_NAME') and call_type =
'FLOW_ESS')
and jobtype = 'JobType://oracle/as/ess/ext/JavaJobType'
Future flow schedules seem not working.

3.1 Flow Instance start and end schedules
select fi.flow_instance_id,
fi.instance_name,
fi.status,
fi.recur_sch_formula_id,
to_char(fi.scheduled_date, 'DD/MM/YYYY HH:MI:SS') sch_start_date,
to_char(fi.schedule_end_date, 'DD/MM/YYYY HH:MI:SS') sch_end_date,
pr.call_id
from pay_flow_instances fi,
pay_requests pr,
pay_flow_task_instances fti,
pay_flow_tasks ft
where instance_name like 'FLOW_INSTANCE%'
and fi.flow_instance_id = pr.flow_instance_id
and fi.flow_instance_id = fti.flow_instance_id
and ft.base_flow_task_id = fti.base_flow_task_id
and ft.base_flow_task_name = 'START_FLOW'
and pr.flow_task_instance_id = fti.flow_task_instance_id
and pr.call_type = 'FLOW_ESS'

3.2 Find a list of all child requests (if the process is multi threading, it will spawn multiple jobs)
select requestid,definition,state,error_warning_detail from fusion_ora_ess.request_history
where parentrequestid in(SELECT
pr.call_id
FROM pay_flow_Task_instances fti,
pay_flow_tasks_vl ft,
pay_requests pr
WHERE fti.flow_instance_id =
WHERE instance_name = 'FLOW_INSTANCE_NAME'
)
AND fti.base_flow_task_id = ft.base_flow_task_id
AND ft.base_flow_task_id = pc.base_flow_task_id
AND fti.flow_task_instance_id = pr.flow_task_instance_id
AND call_type IN ('FLOW_ESS', 'ESS'))
: 'Bold' to be replaced with site-specific details

Instruction

Preferences
SUI Set Preferences is available from a new page.
With the ability to mass import general preferences at user level for global deployment, in Release 12 the Import
Process will override the last updated values. See how-to guide for details.
FSM Enabling Offerings

Before creating an implementation project, it is a recommended practice to update the offering and functional areas
by selecting the enable for implementation checkbox. Features and feature choices determine what functions and
profile options are available to users. See Oracle Applications Cloud Using Functional Setup Manager (video) for
more details.
Subscribed: Customer has subscription(licensed) for the Offering
Provisioned: Offering is provisioned(installed) on the customer environment
On a GSI (Global Single Instance) environment, there are more offerings provisioned compared with what a
customer has subscribed to. Possibly, customers may find more than enough for the project. Customers should
only use the Offerings they need and ignore any others that are not applicable to them.
Fusion HCM Taleo Recruiting Integration

Taleo upgrade scheduling is SR-based whereas the R12 upgrade of Oracle Cloud must come through upgrade
scheduling via My Services.
Taleo 15A was given an end-of-life due date of September 30, 2017; all 15A customers must upgrade to 15B prior
to this date. Any 15A customers not elected 15B will be set in the July-September upgrade timeframe.
For out-of-the-box (OOTB) customers, the Fusion and Taleo refreshes must be coordinated.
If your Taleo upgrade schedule is not the same as the HCM Cloud, consider upgrade regression testing against
the delivered or custom integration processes:
Foundation data from Fusion HCM to Taleo Recruiting
New hire candidate and requisition data from Taleo Recruiting to Fusion HCM
Employee and user data from Fusion HCM to Taleo Recruiting

A Final Note
Oracle HCM Cloud provides a straightforward upgrade experience. Get prepared in advance for a successful
transition to the latest release updates.

Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
CONNECT WITH US
blogs.oracle.com/oracle
Copyright 2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0617
Oracle HCM Cloud: Checklists for Upgrading from Release 11 to Release 12

May 2017
Author: Surlina Yin
Contributing Author: Jim Kirkpatrick

ID 2235545.1 Oracle HCM Cloud Checklists For Upgrading From Release 11 To Release 12 v3

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ID 2235545.1 Oracle HCM Cloud Checklists For Upgrading From Release 11 To Release 12 v3

Hochgeladen von

Copyright:

Verfügbare Formate

Oracle HCM Cloud: Checklists for Upgrading

from Release 11 to Release 12

Five Phases of Project Management for an Upgrade 2

Release 12 Upgrade Planning Checklist 14

Further resources that you can consult before you upgrade:

1 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

Evaluate Plan Configure Test Rollout

Explore possibilities to improve user experience, efficiency, and effectiveness

Understand value and enhancements in Release 12, see Release Updates

o Expected benefits for the business

o Expected costs (resources, time, impact on co-existence etc.)

3. Contemplate configuration management. See R11 PRE-UPG To Do Lists.

4. Review performance and scalability improvements.

5. Review potential environmental impact.

6. Review add-on localizations and/or languages.

2 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

# Activity / Action by Decision (if applicable)

3 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

Project resource planning

Upgrade plan and timelines

Prepare test scope and iteration

Assessment of end-user impact re: change management

Establish issue resolution process

Project organization and governance

o Resource allocation and task assignments

Projected timeline with built-in milestones and contingency plans

2. Define testing strategy and testing flows.

3. Identify training needs.

4. Address impact on 3rd party components and interfaces.

5. Articulate defect/issue resolution process

6. List of milestone deliverables.

7. Define milestone checkpoints.

8. Project kickoff session.

4 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

# Activity / Action by Decision (if applicable)

5 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

End-to-end assessment online/offline process steps

Release 12 changes activate/disable new features

Validation against system administration setup enable/disable notification

Entry criteria met

2. Configuration changes and migration methods.

3. Complete post-upgrade technical/functional steps. See R12 POST-UPG To Do Lists.

6 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

# Activity / Action by Decision (if applicable)

7 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

This phase aims to cover:

Quantitative testing procedures

Enterprise Scheduling Service (ESS) process validation

Business and technical requirement validation

Defect discovery and regression testing

HCM Data Loader, Extracts, Payroll Interfaces

Referential data validation

Reports & Analytics

Upgrade patch/bug fixes escalation

Testing progress status/results

Decision to execute full test iteration

Go/No-go Decision to proceed to Rollout or return to Plan/Configure stages

2. Check outstanding REL12UPG SR, bug ETAs and patching schedules.

3. Validate upgrade is successful.

4. Consolidate changes for user learning materials.

8 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12

# Activity / Action by Decision (if applicable)

9 | ORACLE HCM CLOUD: CHECKLISTS FOR UPGRADING FROM RELEASE 11 TO RELEASE 12