Basics of HCM Data Loader in Fusion
Basics of HCM Data Loader in Fusion

 2,294 total views

In this article we will go through the basics of HCM Data Loader aka HDL which is one of the most familiar data loading tools in Fusion HCM.

Here is the Agenda for this post:

  • What is HCM Data Loader?
  • Configure HCM Data Loader Parameters
  • Who Can Load Data Using HCM Data Loader?
  • Navigation of HDL in Fusion Applications
  • Reviewing Supported Business Objects
  • Understanding the Business Object Shape
  • Supported File Line Instructions
  • Definition and Data Line Structure
  • File Discriminators
  • Line Validation
  • Keys and its importance

What is HCM Data Loader?

  • It is a Flat File based bulk loading of data into Oracle HCM Cloud. 
  • It is used for Data Conversion into Fusion from any legacy system (PeopleSoft, EBS, SAP, Workday, etc.) for one-time or incremental loads. 
  • It is suited for large volumes of data loads and hierarchical data.
  • It supports multiple data sources.
  • If the customer is a global customer and they might be using different legacy applications in different countries, we can load all legacy systems data into fusion using HDL.
  • It uses two step approach, first it will load into staging table and then imports data into the core tables.
  • It supports loading complex data objects like Worker with full date effective history.

Configure HCM Data Loader Parameters:
More details on configuring HCM Data Loader parameters has been posted at Configure HDL Parameters. Please check it out and come back to this article.

Who Can Load Data Using HCM Data Loader?
Human Capital Management Integration Specialist job role is required to access the HCM Data Loader related tasks.

Navigation of HDL in Fusion Applications
Navigate to Navigator > My Client Groups > Data ExchangeNow on the right hand side tasks bar, we can see the tasks for HDL as seen below:

Reviewing Supported Business Objects
In the HCM Data Loader tasks, click on “View Business Objects” task

Understanding the Business Object Shape
The HDL file supports Hierarchical shape of business object components. It supports Multiple child occurrences and it has the ability to load child components independently

Supported File Line Instructions

These are the most frequently used File line instructions and is not an exhaustive list. There are some business object specific file line instructions that can be used. However it would be a new topic of discussion to get into business object wise file line instructions.

Exhaustive list of all SET operations have been listed at SET Operations on HDL file

Definition and Data Line Structure
METADATA / MERGE / DELETE line format:<INSTRUCTION>|<DISCRIMINATOR>|<Attribute 1>|…|<Attribute n>

File Discriminators
Sample for Job Business Object. We can see that it has two discriminators Job and JobGrade.

Line Validation

  • First METADATA line is defined for each object and the next line is followed by the corresponding MERGE/DELETE data Line.
  • One .dat file cannot have same METADATA Line repeated more than once.
  • Each METADATA line should have a valid discriminator
  • Contain unique reference for itself using any one of the supported key resolutions
  • Child component must include a unique reference to its parent.
  • MERGE/DELETE Line should contain the values of the same attributes as defined in the corresponding METADATA Line

Keys and its importance
Keys are used to uniquely identify one of the below

  • The local business object component
  • The parent of a business object component
  • Any other object referenced by a business object component

Types of Keys supported by HDL
HCM Data Loader supports Four types of keys to uniquely identify a business object.

  • Oracle Fusion GUID
  • Oracle Fusion Surrogate ID
  • Source Keys
  • User Keys

Oracle Fusion GUID

  • Generated in Oracle Fusion when a record is created
  • It holds an Hexadecimal value
  • Unique across all objects in Fusion system
  • Held in Integration Key Map (HRC_INTEGRATION_KEY_MAP) table
  • Cannot be assigned in the HDL file while creating Business Object
  • Can be assigned in HDL file while updating/deleting Business Object

Source Keys

  • Two values combined “SourceSystemOwner” and “SourceSystemID” make a unique source key combination
  • Multiple Source System Owners can be configured if the customer uses multiple legacy systems
  • Held in Integration Key Map table
  • Can be used in creating/updating/deleting data in HDL file

Oracle Fusion Surrogate ID

  • Generated in Oracle Fusion when the record is created
  • Numeric value
  • Unique only for the object type
  • Held against the object definition
  • Cannot be used while creating Business Object in HDL file
  • Can be used while Updating/Deleting Business Object in HDL file

User Keys

  • Natural values
  • One or many attributes
  • Sometimes alternatives
  • Sometimes updateable
  • Can be used while creating/updating/deleting Business Objects in HDL file

Key Resolution Sequence
1.Oracle Fusion GUID
2.Oracle Fusion Surrogate ID
3.Source Keys
4.User Key

HDL file will use this sequence to identify the key fields that have been provided in the HDL file. If multiple types of key fields are provided, then it will pick up the first in this sequence.

Hope you got basic functionality of HCM Data Loader.

If you have any questions, please feel free to reach out to me by posting in comments section.

If you are interested in learning Fusion Technical tools go through this post

If you liked the article, please share it with your friends/ colleagues/ teammates or anyone who might also benefit from it.

The following two tabs change content below.
Sricharan is a Fusion HCM Solution Architect with over 13+ years of overall experience and 5+ years of Fusion experience. He is passionate about technical aspects of Fusion HCM and writes interesting articles on HCM Extracts, HCM Data Loader, Fast Formula, BI Publisher, Integrations and Automation etc.

This Post Has 3 Comments


    hi charan,
    can share me more info hcm dalaloder

  2. Unknown

    Good Intro… Thanks for sharing!

  3. Scraatch

    Thank you for the explanation, do you have an idea how the stage tables are structured?

Leave a Reply