Loading Oracle HCM Cloud Metadata

Note:

Drill through and write-back are not supported in an integration with Oracle Human Capital Management 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 Applications page and then from the Actions menu, download the Oracle HCM Cloud extracts by clicking Download HCM Extract.

For more information, see Downloading Oracle HCM Cloud Extracts.

An EPBCS HCM Extract.zip file containing the following Oracle HCM Cloud extract definitions is downloaded. 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 it. 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 to the 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 the Oracle HCM Cloud 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 page, 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 from the Application page, 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,
- creates a location,
- creates mappings to import data to the correct Oracle Hyperion Workforce Planning accounts,
For more information, see Registering an Oracle HCM Cloud Application.
From the Application page, click to the right of the Oracle HCM Cloud application, and then select Application Detail.
Select the Options tab.

Select any applicable application detail options and click Save.

Options include:

Any source filters associated with the data source are created automatically during the integration. You can select any specific criteria on the Source Filters tab to filter the results that are loaded.

Depending on the Oracle HCM Cloud metadata category, the following source filters apply:

Effective Date—Select the date on which you want the trees to be effective.
Legislative Data Group—Legislative data groups are a means of partitioning payroll and related data. At least one legislative data group is required for each country where the enterprise operates. Each legislative data group is associated with one or more payroll statutory units.
Tree Code—Tree code for hierarchy in Oracle HCM Cloud (for objects with hierarchy, for example: Org, Position)
Tree Version—Tree Version for hierarchy in Oracle HCM Cloud

Changes Only—Controls the extract mode. Valid options are N or Y.

The following table describes the different extract modes, their lookup values and descriptions:

Mode	Lookup Value	Description
N	All attributes	Includes all data in the extract. A full extract is run which produces the full data output at that point of time. The archived data is utilized as a baseline.
Y	Changed attributes	Compares this extract run with the previous extract runs and by comparing against the baseline (to identify the incremental data), displays the data that has changed only.

Note:

You can also select the above options on the Filters tab in Options.

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.