Skip Headers

Home

Contents

Book
List

Contact
Us

PDF

4 Define HCM Configuration for Coexistence

This chapter contains the following:

HCM Configuration for Coexistence Parameters

Initializing HCM Coexistence: Explained

HCM Configuration for Coexistence Parameters

The HCM Configuration for Coexistence parameters determine how the Load Batch Data process operates. These parameters apply whether you run the process independently or as part of the Load HCM Data for Coexistence process. In general, you set these parameters during implementation and do not need to alter them later, unless for a specific purpose such as error correction.

To set these parameters, you perform the task Manage Loader Configuration.

Unless otherwise indicated, you cannot override the values of these parameters for individual data-load processes.

Oracle On Demand Parameters

Parameter Name	Default Value	Can Be Overridden?
On Demand FTP Root Directory	Null	No

On Demand FTP Root Directory

Name of the Oracle On Demand server's mounted root directory.

Oracle Data Integrator Parameters

Parameter Name	Default Value	Can Be Overridden?
ODI Context	DEVELOPMENT	No
ODI Log Level	2	No
ODI NLS Language	AMERICAN_AMERICA.WE8ISO8859P1	No
ODI Password	Null	No
ODI Root Directory	Null	No
ODI User	Null	No
ODI Work Repository	FUSIONAPPS_WREP	No

ODI Context

The logical name of the group of logical-to-physical mappings for connections in Oracle Data Integrator (ODI).

ODI Log Level

A numerical value between 1 and 5, where 5 is high, indicating the level of detail included in the ODI log file. Do not change the default value unless requested to do so by Oracle Support.

ODI NLS Language

The ODI import file language and encoding settings.

ODI Password

The password for the ODI user name.

ODI Root Directory

The file system directory where ODI creates work and log files.

ODI User

The ODI user name.

ODI Work Repository

The ODI repository that contains ODI-related code definitions.

Loader Parameters

Parameter Name	Default Value	Can Be Overridden?
Load HCM Data Files Automatically	N	No
Loader Cache Clear Limit	500	No
Loader Chunk Size	100	Yes
Loader Maximum Errors Allowed	100	Yes
Loader Number of Processes	1	Yes
Loader Save Size	1	No

Load HCM Data Files Automatically

Indicates, for the enterprise, whether the Load HCM Data for Coexistence process runs automatically on receipt of a zipped data file from a source application. If you leave this parameter set to N, you must run Load HCM Data for Coexistence manually.

Loader Cache Clear Limit

The number of logical business objects to be processed before the Load Batch Data process clears the cache. Do not change this value unless requested to do so by Oracle Support.

Loader Chunk Size

The number of logical business objects a single Load Batch Data thread processes in a single action.

Loader Maximum Errors Allowed

The maximum number of errors in a thread before processing terminates. If an error occurs when processing a complex logical business object (such as a person record), then all rows for that business object are rolled back and marked as Error in Row.

Loader Number of Processes

The number of Load Batch Data threads to run in parallel. If you are processing large amounts of data (for example, more than 1000 rows) or complex data (such as person and work relationship data) consider running 4 or 8 threads in parallel.

Loader Save Size

The number of logical business objects to be processed before committing the objects to the database. Do not change this value unless requested to do so by Oracle Support.

User Name Parameters

Parameter Name	Default Value	Can Be Overridden?
User Name Expression	Null	No

User Name Expression

By default, the user name of an HCM coexistence user is the person's e-mail address. You can set the user name to either the person number or an assignment number by entering one of the following expressions in the User Name Expression field:

loaderCtx.getPersonAttr("PersonNumber")
loaderCtx.getAssignmentAttr("AssignmentNumber")

Initializing HCM Coexistence: Explained

Once your source application is configured for use with Oracle Fusion and connections are established between the two systems, you are ready to perform the initial load of business objects from the source application to Oracle Fusion.

The following figure summarizes the initial data-load process.

Define Business Objects in Oracle Fusion

You define the following business objects in Oracle Fusion by performing the associated tasks in the order specified by the Oracle Fusion Functional Setup Manager.

Business Object	Task
Application Reference Data Set	Manage Reference Data Sets
Employment Action	Manage Actions
Employment Action Reason	Manage Action Reasons
Enterprise	Manage Enterprise HCM Information
Legal Employer Organization Payroll Statutory Unit Organization	Manage Legal Entity HCM Information
Legal Entity	Manage Legal Entity
Legislative Data Group	Manage Legislative Data Groups
Payroll Element Input Value	Manage Elements
Payroll Element Type	Manage Elements
Person Assignment Status Type	Manage Assignment Status
Person Type	Manage Person Types

You define the following objects only if you use Oracle Fusion Talent Management for Coexistence.

Business Object	Task
Talent Profile Content Type	Manage Profile Content Types
Talent Profile Type	Manage Profile Types
Talent Instance Qualifier	Manage Instance Qualifiers
Talent Instance Qualifier Set	Manage Instance Qualifiers

Generate and Export Mapping Identifiers from Oracle Fusion

After completing the definition of business objects in Oracle Fusion, you generate and export mapping identifiers for them by performing the Manage HCM Configuration for Coexistence task. The mapping identifiers are placed automatically in a zipped data file that is written to the FTP server, from where the system administrator for the source application can retrieve them.

Create Data Maps in the Source Application

Once the mapping identifiers for the Oracle Fusion business objects are retrieved from the FTP server and imported to the source application, you map business objects in the source application to Oracle Fusion objects so that data can be exchanged between the two data models.

The detail of this task depends on the source application. For more information, see the following documents on My Oracle Support:

Integrating PeopleSoft HRMS 8.9 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480967.1)
Integrating PeopleSoft HRMS 9.0 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480995.1)
Integrating PeopleSoft HCM 9.1 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480996.1)
HCM Coexistence - Integrating EBS HCM 11i and Fusion Talent Management and Workforce Compensation (Document ID 1460869.1)
HCM Coexistence - Integrating EBS HCM R12.1 and Fusion Talent Management and Workforce Compensation (Document ID 1460868.1)

Extract Data from the Source Application

When the data-mapping task is complete, you extract data for upload to Oracle Fusion from the source application and transfer it to the FTP server.

The detail of this task depends on the source application. For more information, see the following documents on My Oracle Support:

Integrating PeopleSoft HRMS 8.9 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480967.1)
Integrating PeopleSoft HRMS 9.0 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480995.1)
Integrating PeopleSoft HCM 9.1 with Fusion Talent Management and Fusion Workforce Compensation (Document ID 1480996.1)
HCM Coexistence - Integrating EBS HCM 11i and Fusion Talent Management and Workforce Compensation (Document ID 1460869.1)
HCM Coexistence - Integrating EBS HCM R12.1 and Fusion Talent Management and Workforce Compensation (Document ID 1460868.1)

Perform the Initial Data Load

You load data to Oracle Fusion by performing the Load HCM Data for Coexistence task. For the initial data load, you perform the task once for each of the following groups of business objects:

Work structures records
Person records
Employment records
Workforce compensation records
Talent management records

You perform the initial data load in the order in which the data-load tasks appear in the Oracle Fusion Functional Setup Manager. In addition, you load the business objects within each group in a specified order to respect dependencies between them.

Synchronize Data After Initial Data Load

After the initial data load completes successfully and you begin to use Oracle Fusion, you must take steps to keep data synchronized between your source application and Oracle Fusion.

In particular:

Talent management records are migrated to Oracle Fusion Talent Management, which becomes the source of truth for that data; however, all other uploaded data is managed in the source application. Therefore, you must upload it to Oracle Fusion regularly to ensure that data in the two environments remains synchronized. The frequency of incremental data loads (also performed using the Load HCM Data for Coexistence task) depends on the frequency of changes to the source data and on your use of Oracle Fusion.
Traffic between the source application and Oracle Fusion is not one-way: you must extract data updated by Oracle Fusion Workforce Compensation and return it to the source application for further processing. For example, a worker's salary amount is returned to the source application for payment by the payroll system. To extract data from Oracle Fusion, you perform the Extract HCM Data for Coexistence task. You must upload data to Oracle Fusion again only after loading the compensation changes in the source application.