Index

Upgrade E-Business Suite Release 11i to 12....................................................................................................2Human Resources Tasks...............................................................................................................................2

Time Estimation...............................................................................................................................................5Assumptions.....................................................................................................................................................6

Upgrade E-Business Suite Release 11i to 12

Human Resources Tasks

Application Task Description

Human Resource

s

Step 1 Apply latest HRMS Legislative Updates (required)

To maintain required legislative compliance, you must apply all legislative data updates.

Step 2 Verify Labor Distribution tables (conditional)

Only if Labor Distribution implemented

If you currently use Oracle Labor Distribution and have not previously applied HRMS Family Pack H (or later), there may be Labor Distribution tables that contain invalid data.

Run the concurrent program PSP: Post Upgrade Bad Data Report from the Labor Distribution Superuser responsibility to determine whether any Labor Distribution tables have invalid data.

Step 3 Re-seed custom salary components (conditional)

Only if Labor custom salary components implemented

If you previously created customized salary components (as described in Oracle Human Resources Management Systems Implementation Guide Release 11i), you may need to re-run the associated SQL script to re-seed custom salary components. You can determine if this action is necessary by referring to the Release 12 version of the implementation guide to ensure that your customizations in the salary component area are re-implemented as expected.

Step 4 Migrate Training Administration to Learning Management (conditional)

The upgrade automatically updates Oracle Training Administration to enable new functionality and changes the product name to Learning Management. During the upgrade, a concurrent request was submitted to determine what further action is required. See Guide to the OTA Classic Upgrade Report (Doc ID: 269571.1) for a description.Find the attached file.

Step 5 Complete HRMS Configuration Workbench Setup (conditional)Only if HRMS Configuration Workbench implemented

If you currently use HRMS Configuration Workbench with Winrunner, you need to apply an additional patch (5441645), which contains updated Winrunner files

Step 6 Verify Time Zone conversion for Learning Management (required)

OTA.J.Rollup.1 and Release 12 include the Time Zone conversion for Oracle Learning Management upgrade. It requires you to examine the Update Time Zone concurrent manager log file that is automatically generated during the upgrade process. For additional information, or if you encounter any errors, follow the instructions in Guide to the Time Zone Update (Doc ID: 371179.1).

Step 7 Check downtime reduction report (recommended)

Log on as System Administrator and submit the Data Update Process Status Report concurrent request. It identifies a number of data update tasks, which may run for an extended period of time if you have a large volume of data that requires manipulation.

Step 8 Migrate stored names to new and revised formats (required)

Family Pack K supplies definitions of standard person-name formats to define the structure of person names.

Approvals Management

Step 1 Attach new responsibilities to existing users for AME (conditional)

After the upgrade, you must migrate new responsibilities to existing Approvals Management Engine (AME) users. From the System Administrator responsibility, attach the Approvals Management Post-Upgrade Process concurrent program to the System Administrator Reports request group. Then, run the concurrent program to attach the new responsibilities.If you have previously applied 11i.AME.B, omit this step.

Payroll

Step 2 Associate a set of books with an organizational payment method

This step is required only if your payroll implementation has Cash Managementinstalled. For more information, see Accounting Reference Information for CashManagement Integration, Implementing Oracle HRMS.

Step 2 Run the QuickPay Exclusions Data Upgrade process (recommended)

If you have not previously run the QuickPay Exclusions Data Upgrade process, you should do so now. From the System Administrator responsibility, run the Generic Upgrade Mechanism concurrent program from the Processes and Reports menu

Step 5 Enable Subledger Accounting (SLA) (conditional)

If you intend to enable Subledger Accounting for Oracle HRMS in the first available version of Release 12, you must perform a manual upgrade sequence to support your transfers to SLA. The manual sequence includes these steps:1.Set up Journal Line Definitions2.Set up the Application Accounting Definition3.Set up the Method for each chart of accounts

Intelligence

Step 1 Perform additional steps for Embedded Data Warehouse (required)

This release includes Embedded Data Warehouse (EDW) Release 4.3, which requires post-installation steps to complete the implementation. See the Oracle Embedded Data Warehouse Install Guide (A90299-05) for instructions.

Step 3 Perform additional Daily Business Intelligence steps (required)

This release includes Daily Business Intelligence Release 8.0. See the Oracle Daily Business Intelligence Implementation Guide for information.

Step 4 Perform additional Balanced Scorecard steps (required)

This release includes Balanced Scorecard Release 5.0. See the Oracle Balanced Scorecard Install Guide for information.

Time Estimation

Module Implementation Testing Resources NotesCore Human Resources 1 3 1Self Services 0 2 1Payroll 1 4 1Learning Management 2 2 1Business Intelligence 15 2 1

Total 19 13 1

Assumptions

1. Resources are available and allocated to the upgrade project, as testing is very key part of the project

2. Time estimation only for standard modules implementation.3. any custom objects should be built according to oracle specifications and recommendations, as

none standard customizations are not safe from upgrade