Oracle Human Resources Management Systems Implementation Guide

Implementation

Implementation Steps

Before You Start

Before you begin implementing Oracle HRMS, you must ensure your legislation-specific startup data is installed. The installation is normally done by the MIS Manager. You need this startup data before you use Elements, Payment Methods or Legislation Specific Flexfield Structures.

See Oracle E-Business Suite Installation Guide: Using Rapid Install for more information.

Also, check to see whether there are any post installation steps you need to perform before you start to implement Oracle HRMS.

See: Post Install Steps.

Post Install Steps

There are two generic post install utilities for Oracle HRMS:

DataInstall enables you to specify all the legislations that you want to install for HR and Payroll, and HR only. This means that when you subsequently perform an installation or upgrade, you can install your legislations in a single operation. DataInstall provides a series of menus from which you can specify the legislation and product combinations.
AutoPatch (adpatch) applies the installation or upgrade combinations that you have previously specified in DataInstall.

Canada and USA

If you are installing Oracle Payroll (Canada and US) you also need to install Quantum, a third party taxation product, produced by Vertex, that Oracle Payroll (Canada and US) uses.

France

If you are installing a French localization, there are two additional post install steps for that must be completed for Oracle HR for France. These are:

Run the Seed French Data process
Create a new EUL (End User Layer) in Discoverer and enable user access to database tables and views by running the Grant HR Access to Discoverer process

Additional Information: See also My Oracle Support Knowledge Document 2277369.1, Oracle E-Business Suite Support Implications for Discoverer 11gR1.

US Federal HR

If you are installing the US Federal HR localization, there is one additional step to be able to produce bitmap reports.

To Run the DataInstall Utility (Required)

To specify legislations using DataInstall:

Run the DataInstall utility to select legislations using the command:
```
jre oracle.apps.per.DataInstall <APPS Username> <APPS password>
```
Note: In multiple ledger installs, supply the username and password of the first APPS account.

The DataInstall Main Menu is displayed.
Choose option 1. This displays a screen showing a list of product localization combinations that you can choose.

For each product or localization that already has legislation data on the database, the Action will be defaulted to upgrade. This cannot be changed.
Federal HR only: Choose both Oracle Federal HR and Oracle Human Resources from the list of product localizations.
Select any new installations that you want to implement. For example, if you wanted to install Canada Payroll, number 3, you would type 3I. This would also set the action on Canada Human Resources to Install as dependencies are maintained.

If you are installing an additional legislation, to correct a mistake use the Clear option. If you have selected to install an additional Payroll and HR legislation, clearing the Payroll legislation will clear the HR legislation also.

You cannot use Force Install for upgrades. You only need to use Force Install if you want to reapply steps in the Global Legislation Driver that have already been applied.
If you select a localization other than US or UK, you are returned to the main menu.

If you select a US or UK localization the DataInstall - College Data Option screen is displayed showing whether college data is currently installed for US and UK localizations. The install option is only available if you have no existing college data. If you have existing data then the localization will default to Upgrade, though this can be changed.

Choose Remain if you want to keep the existing data and not apply the upgrade, or choose Clear to set the action to null.

You cannot use Force Install at this point.

Press Return to display the main menu and make further changes or exit.
US and Canada only: If you have installed Oracle Payroll, select the JIT/Geocodes option from the DataInstall menu to load the latest JIT/Geocodes data.

This option is also available to Oracle HR customers who wish to validate US or Canadian addresses using Vertex Geocodes data and/or maintain employee tax data in Oracle HR. However, customers who do not have Oracle Payroll must obtain a license from Vertex before installing this data.

Press Return to display the main menu and make further changes or exit.
When you choose to exit the DataInstall Actions Confirmation screen is displayed.

Select Y to save your changes and exit, or select N to exit without saving your changes.

When you have exited, the DataInstall Actions Summary screen is displayed. This summarizes the actions that will be taken when the program exits, or when ADPATCH is run with the Global Legislation driver.

Run the Global Legislation Driver using AutoPatch (adpatch) (Required)

The Generic HR Post Install Driver delivers the generic entity horizon and all the selected localizations. To run it, type in the following commands:
```
$ cd $PER_TOP/patch/115/driver
$ adpatch
```
Then apply the driver hrglobal.drv
After applying the Global Legislation Driver, examine the out file hrlegend.lst. This logs any localizations selected in the DataInstall utility but which have not been applied by this driver. Refer to the Installation Manual to ensure that everything has been applied correctly, or contact World-wide Support.
UK only: Examine the following out files:
- pegbutcl.lst. This file logs the step that removes previously seeded user tables for the UK legislation before delivering the latest version. It may also show where seed data names have been changed between releases.
- perleggb.lst. This file logs the housekeeping step that gets rid of redundant UK seed data after delivery of the latest version. It also records the new balance feeds that have been inserted following an upgrade from Oracle Human Resources to Oracle HRMS.
- The log file produced by the FFXBCP formula compilation step. The name of the FFXBCP log follows the naming convention of the <request_id> log, and is included in the last section of the adpatch log.
These files are used by Oracle Support Services to diagnose problems with seed data following an upgrade. SQL errors indicate severe problems. Keep these files for reference in the event of any future problems with UK seed data.

Install Quantum for Oracle Payroll (Canada and US) (Conditionally Required)

Important: The following steps are to be done in RUN Edition of Application

Set up a directory structure to hold the Quantum product.

By default, Oracle Payroll looks for the Quantum product in the $PAY_TOP/vendor/quantum directory, however, you can choose where it is placed and override the default location.

Suggestion: You can create a $PAY_TOP/vendor/quantum_versions directory and a quantum symbolic link under $PAY_TOP/vendor Directory pointing to the correct version of Quantum, since the Quantum products release cycle may be different from Oracle Payroll. For example, copy Quantum 3.0.1 to $PAY_TOP/vendor/quantum_versions/3.0.1. Now create quantum symbolic link as "ln -s quantum_versions/3.0.1 quantum" under $PAY_TOP/vendor directory. It is necessary to create the Symbolic link relative to the $PAY_TOP/vendor instead of creating a link from Root Directory by using $PAY_TOP/vendor/quantum_versions/3.0.1.
Unzip the Quantum Components from the Quantum Patch.

Oracle Applications provides a Quantum Patch in which will be a ZIP file called pyvendor.zip. On unzipping the patch, the pyvendor.zip can be found under directory [patchnumber]/sht/lib. In the ZIP file will be one ZIP file per operating system that is supported by Oracle Payroll (US). Uncompress the pyvendor.zip file and then Uncompress the zip file of the required operating system. Move the required version into the directory structure created in Step 1. For example, uncompress the files then do the following:
```
$ mv SOLARIS/3.0.1 $PAY_TOP/vendor/quantum_versions
$ ln -s quantum_versions/3.0.1 $PAY_TOP/vendor/quantum
```
The extraction from the compressed file will create a directory called (<operating system>3.0.1) and two sub directories (lib and utils) along with a number of files in each directory.
Build the Quantum product's data files.

To build Quantum's data files, firstly create a directory to hold the data files. Oracle Payroll assumes that these data files are in $PAY_TOP/vendor/quantum/data.

Secondly, run the utility cbmaint that is in the Quantum utils directory. This utility will show a menu of either Payroll or Geocoder. Choose the Payroll option and at the prompt "Enter the Payroll datasource name:" enter the directory into which the data files are to be placed, for example, $PAY_TOP/vendor/quantum/data (Please note to replace $PAY_TOP with the absolute path for your instance). Once the processing is complete, the menu will reappear and the utility can be exited.

Note: Ensure that the file permissions of the data files are set to readable for all the relevant users. If this is not done then Oracle Payroll will not be able to access these files.
Populate the Quantum data files.

Once the data files have been created they need to be populated with taxation data. The taxation data is held in a file called qfpt.dat, which will be delivered in the pyvendor.zip file. Copy this file into the Quantum product area. Once this has been done the data file update utility can be run. This is located in the utils directory called vprtmupd. Select the Update Payroll Tax option from the menu, and answer the displayed questions. The first prompts for the datasource, this should be the location of the data files created in the previous step. The second is the location of the qfpt.dat file. For example:
```
Enter Datasource: $PAY_TOP/vendor/quantum/data
Enter the path of the update file:  $PAY_TOP/vendor/quantum
```
Important: It is necessary to replace the $PAY_TOP with the absolute path in your instance in the above parameter values.

The update file supplied is a default file, it is not guaranteed to calculate taxes correctly. Its purpose is to allow you to perform testing prior to contacting Vertex to request the correct update file.
Register the Quantum Data Files location.

If the data files for Quantum have not been placed in the default location ($PAY_TOP/vendor/quantum/data), then the location of these files must be supplied to Oracle Payroll. This is performed by placing a row in the PAY_ACTION_PARAMETERS table:
```
SQL> insert into pay_action_parameters values ('TAX_DATA', '< Override Location >');
```
Add instructions to Custom Code Synchronization Driver.

For the Online patching requirement, the File system will now exist as Two Editions. One will be designated as RUN (the one currently in use by Application) and other as PATCH (this will become RUN after the next patching cycle and current RUN will become PATCH). The Quantum Setup done above in RUN Edition should be moved to PATCH Edition so that after the next patching cycle, the latest RUN Edition will have the Quantum Setup done above.

In order to achieve this synchronization between RUN Edition and PATCH Edition File systems, we have a provision through the "Custom Syncup Driver" available as part of ADOP Prepare Phase

It is necessary to add commands (which will be explained below) to the Custom Syncup Driver $APPL_TOP_NE/EBSapps/appl/ad/custom/adop_sync.drv to synchronize the Quantum Files. As Quantum files can be maintained default Location of $PAY_TOP/vendor/quantum or Customer preferred Override Location, instructions are mentioned below on how to add commands to the Custom Syncup Driver based on the way Quantum files are maintained.

Important: The following instructions are explained with reference to Linux Operating System. Users on other Operating systems should use the equivalent instructions in their Operating Systems to acheive the required synchronization.

Quantum files under default Location of $PAY_TOP/vendor/quantum:

It is necessary to synchronize the Quantum directories from RUN Edition to PATCH Edition File system. If the Quantum directories are mentioned in Action Pararameters, then those values are also need to be updated. The commands to be added are:
```
##Begin of Section for Quantum Synchronization##
##Sync up Quantum Directories##
rsync -lzr %s_run_base%/EBSapps/appl/pay/12.0.0/vendor %s_patch_base%/EBSapps/appl/pay/12.0.0
##Update to Action Parameter Level Quantum Directories Overrides##
%s_tools_oh%/bin/sqlplus %s_apps_user%/%s_appsPwd% @%s_run_base%/EBSapps/appl/pay/12.0.0/patch/115/sql/pyusupdpa.sql %s_run_base% %s_patch_base%
##End for Quantum Synchronization##
```
Quantum files under customer preferred Override Location:

If customer is using any different location to store the Quantum files instead of the default $PAY_TOP/vendor/quantum and if this Override location is outside the RUN Edition and PATCH Edition File systems , it is necessary to ensure that they specify the synchronization step as given below in the custom sync up driver $APPL_TOP_NE/EBSapps/appl/ad/custom/adop_sync.drv. In this case, no requirement to update the Action Parameter Values holding the Quantum Override directories. They must always hold the values corresponding to the Override Location. The commands to be added are:
```
##Begin of Section for Quantum Synchronization##
##Sync up Quantum Directories##
rsync -lzr <Location where quantum directory is present> %s_run_base%/EBSapps/appl/pay/12.0.0/vendor
rsync -lzr %s_run_base%/EBSapps/appl/pay/12.0.0/vendor %s_patch_base%/EBSapps/appl/pay/12.0.0
##End for Quantum Synchronization##
```

Run the Seed French Data process (France)

This process creates and populates some of the user defined tables used by the various French reports for the Business Group of the current responsibility. It also delivers the example data for the Bilan Social. It should be run for each Business Group that contains data for the French legislation.

For information on the user defined tables created by this process see: User Defined Tables Used by the Bilan Social, Oracle HRMS Enterprise and Workforce Management Guide , and User Defined Tables, Oracle HRMS Configuring, Reporting, and System Administration Guide

Run the Seed French Data process in the Submit Requests window.

Create an EUL and Enable User Access to Database Tables and Views by Running the Grant HR Access to Discoverer process (France)

Additional Information: See also My Oracle Support Knowledge Document 2277369.1, Oracle E-Business Suite Support Implications for Discoverer 11gR1.

In order to use the supplied business area and Discoverer workbooks you must perform the following steps:

Create an EUL

If you do not have an existing Oracle Discoverer EUL you must create one before you can import the HR France - Bilan Social business area.

See: Oracle Discoverer Administration Guide for further information on creating an EUL.
Import the hrfrbsel.eex file

Once you have a suitable EUL you must import the hrfrbsel.eex file. This will deliver the HR France - Bilan Social business area. This file is contained in the Bilan Social Discoverer Components zip file that can be obtained from Oracle World Wide Support.

See: Oracle Discoverer Administration Guide for further information on importing files.
Run the Grant HR Access to Discoverer process

The EUL user must be given the correct permissions in order to access the tables and views in the database that are used by the Bilan Social. To do this, you must run Grant HR Access to Discoverer process in the Submit Requests window.

You will now be prompted to enter the following parameters:
- the connect string for the database on which the Bilan Social data is stored
- your EUL user name
- your EUL password
Choose Submit. The process will now run and assign the appropriate permissions to your EUL user.

HR Print Reports (US Federal)

To be able to produce bitmap and postscript reports, you must relink ar60runb.

Chenv to the environment.
Make sure that FND_TOP and APPL_TOP are correct.
cd $FND_TOP/bin
adrelink.sh force=y "fnd ar60runb"

Implementation Checklist

Use the following checklists to record which parts of Oracle HRMS you want to use. Then refer to the implementation steps to see the high level steps you must complete for each business function you have chosen to implement.

< Post Install Steps (Required)

Refer to the Post Install Steps to see any steps you must perform before you implement Oracle HRMS.

< Administration (Required)

Includes key and descriptive flexfields, Extra Information Types (EITs), currencies, View All HRMS User, and lookups.

< Enterprise and Workforce Management (Required)

Includes organizations, jobs, positions and position control, workflow for transactions, HR budgets, person types, and collective agreements.

< Payroll Process Management (Optional)

Includes payrolls, payment methods, and payslip information. For Canada, also includes Workers' Compensation, and provincial medical.

< Compensation, Benefits, and Payroll (Optional)

Includes grades, grade related pay, benefits eligibility, life events, compensation objects, enrollment requirements, activity rates, elements, salary administration, leave and absence management, element sets, rate by criteria, and additional setup for payroll processing and health and welfare.

< Benefits Implementation Without Total Compensation Setup Wizard (Optional)

Provides the full sequence of steps you follow to set up benefit plans manually.

< Workforce Sourcing and Deployment (Required)

Includes recruitment, assignment statuses, contract statuses, assignment rate types for contingent workers, special personal information, global deployments, and requirements matching.

< Talent Management (Optional)

Includes competencies, objectives (Workforce Performance Management), qualifications, and appraisals.

< Workforce Intelligence (Optional)

Includes predefined Discoverer workbooks and a predefined Discoverer End User Layer based on HRMS transactional tables.

Additional Information: See also My Oracle Support Knowledge Document 2277369.1, Oracle E-Business Suite Support Implications for Discoverer 11gR1.

< HR Information Systems (Optional)

Includes reports, letter generation, configuration, task flows, user security, audit requirements, Oracle Applications Help, and Web Applications Desktop Integrator (Web ADI).

Implementation Flowchart

Some of the steps outlined in this section are Required, and some are Optional. Required with Defaults means that the setup functionality comes with predefined, default values in the database; however, you should review those defaults and decide whether to change them to suit your business needs. If you want or need to change them, you should perform that setup step. You need to perform Optional steps only if you plan to use the related feature or complete certain business functions.

Administration