Loading Employees and Users In Oracle Fusion Using HDL

 HDL:HCM Data Loader is a utility for loading business objects in bulk from any source to Oracle Fusion HCM.

We use HCM Data Loader to:

1. Perform one-time migration of legacy data to HCM.

2. Maintain your Oracle Fusion HCM data for occasional or ongoing updates. 

 

PreRequisites:

1. The HCM data loader configuration should be set to Full mode

Navigate to Setup and Maintainence  search for Configure HCM Data Loader task.

Click on the task

Go to HCM Data Loader Scope – Select Full from the dropdown

Note: Once the HCM Data Loader Scope is changed to FULL, both FBL and Spreadsheet loader become Invalid

**ROLE needed to access this task: “Human Capital Management Integration Specialist”

Steps involved in Data loading:

1. Data from any source is made into the dat file as per the template

2. Dat file is loaded into the content server

3. Through HCM Data loader data is imported to the staging table

4. All the imported errors are sent back to the user

5. From the Staging table the data is loaded to the Application Table in FUSION

6. All the loading errors are sent back to the user

Preparing Dat Files:

1. All the data to be loaded is prepared in Worker.dat file .

2. This file can be generated from the application.

Login to Fusion Applications

Navigate to My Workforceà Data Exchange

 

Click on the Tasks Iconà Click on Initiate Data Load 

 

Search with Module As GLOBAL HR-Core Setup and Business Object as Worker .Select the row and click on Generate Template

 

**Note: If a specific Business object is not selected before clicking Generate Template, then templates will be created for all the Business objects in the Selected Module.

• Click on Submit. It with submit a ESS job in the background and generates the template. 
  
  

  

Download the generated template 

 

Save the Worker.dat File.

Getting Started:

It is recommended that, when loading a new worker, only the following mandatory components be supplied in .dat file, with the full date-effective history you require for each worker:

• 
  
  Worker
   Person Name
   Work Relationship
   Employment Terms
   Assignment

The reason for this recommendation is that you should aim at getting the workers loaded in the system. In order to achieve that, few components are required. Once this objective has been achieved, you can focus on additional data.

METADATA Line Structure:

METADATA|Worker|EffectiveStartDate|EffectiveEndDate|StartDate|SourceSystemOwner|SourceSystemId|ActionCode

DATA

Line structure:

MERGE|Worker|2016/01/01|4712/12/31|2016/01/01|HRC_SQLLOADER|T101|HIRE

NOTE: The data should be saved in .dat extension file and zip the file.The .dat file name should be according to the naming convention  it should be Worker.dat in our case.

Sample Worker.dat File for load worker:

 

Save the .dat file . Right Click on the DAT File and zip it.   

Navigate to My Workforce -->Data Exchange—right click on the tasks icon and select Import and Load Data 

 

 

It will ask to submit “Import and Load HCM Data File” ESS job. Click on Submit

 

Keep refreshing until the both the import and load process complete successfully.

  Below are the list of 5 process need to be run to sync users and employees
   Synchronize person records( Parameter : After batch load --> Yes)
    Update person search keyword( Parameter : After batch load--> Yes)
    Send pending LDAP request
    Retrieve Latest LDAP changes
    Refresh Manager Hierarchy.