Process Description for Integrating Data from Oracle HCM Cloud

Data Integration provides an out of the box solution that enables customers to apply predefined mappings from the Oracle Human Capital Management Cloud data model to target dimensions in Workforce or Strategic Workforce Planning.

Data Integration along with Oracle HCM Cloud provides templates that the user must load to the Oracle HCM Cloud instance so that data can be extracted.

Oracle HCM Cloud extracts are used to extract high volumes of data from Oracle HCM Cloud. Each of the predefined Oracle HCM Cloud extracts are defined as "Data Sources" in Data Integration.

When Data Integration performs the data extraction portion of the integration, it designates each predefined Oracle HCM Cloud extract as a data source entity. In turn, these data sources are mapped directly to the Workforce or Strategic Workforce Planning data model in Planning Modules.

There is one template named "EPBCS Initialize.xml" that is not an extract template, but which is used by the test connection process and initialize process on the Data Integration side. If a user does not upload the full set of templates provided by Data Integration, they must still upload "EPBCS Initialize.xml " so that Data Integration can successfully initialize the content from the Oracle HCM Cloud system, and so that it can perform the test connection step.

The following is a description of metadata templates that are provided as part of this integration:

Entity data including organization code, name, and available organization structure
Employee data including person number, full name, and available demographic information
Job data including job code, name, and available job structure
Position data including position code, name, and available position structure
Component data including grade code and name
Union Code data including bargaining unit code and name

The following is a description of the data that is provided by way of the extract templates:

FTE
Salary Basis
Salary Rate for defined basis
Union Code

Customers can also pull the position start date which Data Integration converts to the start month for loading into the Workforce application. They can also customize and extend these integrations, for example, by applying other mapping as needed to meet their business requirements.

Note:

Drill through and write-back are not supported in Oracle HCM Cloud.

At a high level, the steps for loading data from an Oracle HCM Cloud extract data source are:

Make sure that you have been assigned a Human Capital Management Integration Specialist job role.

A Human Capital Management Integration Specialist job role is required to manage Human Capital Management extracts. The Human Capital Management Integration Specialist (Job Role) is the individual responsible for planning, coordinating, and supervising all activities related to the integration of human capital management information systems.

For more information, see Human Capital Management Integration Specialist (Job Role).
In Data Integration, then from Application option, select the application corresponding to the Workforce application, and then on the Dimension Detail tab, assign classifications for the seeded dimensions in Planning Modules.

Classifications for the seeded dimensions include "Employee", "Job", "Property," and "Union" dimensions.
From the Application option, from the Actions option, download the Oracle HCM Cloud extracts by clicking Download Extract.

For more information, see Downloading Oracle HCM Cloud Extracts.

Extracts included in the zip:

An EPBCS HCM Extract.zip file containing the following Oracle HCM Cloud extract definitions is created. These files are a subset of the data that can be extracted and loaded into the Workforce application.
- EPBCS Assignment_<Release>.xdoz
  
  Note:
  
  You must import EPBCS Assignment_<Release>.xdoz into the /Custom folder of BI Publisher and not Oracle HCM Cloud.
  
  Note:
  
  If you require non-English characters, download the EPBCS HCM Extract.zip file and then unzip the zip. Next go to BI Publisher Document Repository and import the EPBCS Assignment.xdoz file.
- EPBCS Entity Metadata_<Release>.xml
- EPBCS Employee Metadata_<Release>.xml
- EPBCS Position Metadata_<Release>.xml
- EPBCS Location Metadata_<Release>.xml
- EPBCS Job Metadata_<Release>.xml
- EPBCS Initialize.xml
  
  Note:
  
  In all cases, the EPBCS Initialize.xml must always be imported in Oracle HCM Cloud.
  
  Note:
  
  All extracts must be imported without the Legislative Group. That is, the Legislative Group must be blank.
- EPBCS Component Salary Metadata.xml
- EPBCS Assignment Data.xml
- EPBCS Account Merit Metadata.xml
Data Integration ships the template that is needed for the extract as content that is uploaded to the Oracle HCM Cloud application. This content is provided by Data Integration because it is not seeded with the Oracle HCM Cloud.
Save the zip to a temporary folder.
Import the Oracle HCM Cloud extract definitions saved in the temporary folder to the Oracle HCM Cloud.

For more information, see Importing the Oracle HCM Cloud Extract Definition.
Import BI Publisher etext template in the Shared/Customer folders.

This template converts the data into the required format.

For more information, see Importing the BI Publisher eText Templates.
Validate and submit Oracle HCM extracts.

You must validate submit an extract before submitting an integration. An integration uses this submitted extraction for fetching data while running.

For more information, see Validating and Submitting the Oracle HCM Cloud Extract Definition.
From the Application option, select the Connections option and configure a connection to the Oracle HCM Cloud.

For more information, see Configuring an Oracle HCM Cloud Connection .
In Data Integration in the Application option, register each individual Oracle HCM Cloud extract (source entity) to be used in an integration under the data source category and Oracle HCM Cloud type.

When this step is completed, Data Integration creates:
- the dimensions (import format) to map Oracle HCM Cloud columns to Planning Modules dimensions,
- a location,
- mappings to import data to the correct Oracle Hyperion Workforce Planning accounts,
For more information, see Registering an Oracle HCM Cloud Application.
Create the integration between the Oracle HCM Cloud source application and the target Oracle Enterprise Performance Management Cloud application.

Note:
Each Oracle HCM Cloud extract imported is registered automatically as a target data source application.
If necessary, modify any dimension details.

All columns from the Oracle HCM Cloud extract are mapped to the EPM target dimensions class with the type "Generic."

For more information, see Mapping Dimensions.

Note:
As a rule, when loading data from an Oracle HCM Cloud data source, do not change, add, or delete any dimension details on the Map Dimensions page.
Member mappings are predefined when the Oracle HCM Cloud extract is registered as an application.

Additionally, Oracle HCM Cloud extracts support the transformation of actual data imported from Oracle HCM Cloud in the Data dimension column.

For example, in the Oracle HCM Cloud, the employee type might be "F" (for full time employee type), or "T" (for temporary employee) while in Planning Modules, the same designations are shown as "FULLTIME," or "TEMP."
Any application filters associated with the Oracle HCM Cloud data source are predefined when the application is registered.

You can select any specific criteria on the Source Filters tab to filter the results that are loaded.

For more information about filters, see Defining Direct Integration Options.
Run the integration.

For more information, see Running an Integration.