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

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

Upgrade E-Business Suite Release 11i to 12
Human Resources Tasks
Application Task Description

Human Resources

Step 1 Apply latest HRMS Legislative Updates (required) Step 2 Verify Labor Distribution tables (conditional) Only if Labor Distribution implemented

To maintain required legislative compliance, you  must apply all legislative data updates.  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. 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. If you currently use HRMS Configuration  Workbench with Winrunner, you need to apply an  additional patch (5441645), which contains updated  Winrunner files 

Step 4 Migrate Training Administration to Learning Management (conditional)

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

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). 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.  Family Pack K supplies definitions of standard  person­name formats to define the structure of  person names.  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. This step is required only if your payroll implementation has Cash Management installed. For more information, see Accounting Reference Information for Cash Management Integration, Implementing Oracle HRMS. 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  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 Definitions 2.Set up the Application Accounting Definition

Step 7 Check downtime reduction report (recommended)

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

Approval s Manage ment

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

Payroll

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

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

Step 5 Enable Subledger Accounting (SLA) (conditional)

3.Set up the Method for each chart of accounts

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. This release includes Daily Business Intelligence  Release 8.0. See the Oracle Daily Business Intelligence   Implementation Guide for information. This release includes Balanced Scorecard Release 5.0.  See the Oracle Balanced Scorecard Install Guide for  information.

Intellige nce

Step 3 Perform additional Daily Business Intelligence steps (required) Step 4 Perform additional Balanced Scorecard steps (required)

Time Estimation
Module Core Human Resources Self Services Payroll Learning Management Business Intelligence Total Implementation 1 0 1 2 15 19 Testing 3 2 4 2 2 13 Resources 1 1 1 1 1 1 Notes

Assumptions
1. 2. 3. Resources are available and allocated to the upgrade project, as testing is very key part of the project Time estimation only for standard modules implementation. any custom objects should be built according to oracle specifications and recommendations, as none standard customizations are not safe from upgrade