2,294 total views
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.
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>
Sample for Job Business Object. We can see that it has two discriminators Job and JobGrade.
- 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
- 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
- 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
- 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
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.
Latest posts by Sricharan Monigari (see all)
- Renaming HCM Extracts is a possibility from 20D - November 24, 2020
- Sangam20 – Oracle Users Group Conference - November 23, 2020
- Passing Parameter values from Flow Instance to HDL Transformation Formula - November 23, 2020
- Solve manual FTP server update issue for HCM Extracts post every P2T refresh - November 16, 2020