0% found this document useful (0 votes)
192 views2 pages

Creating A Simple File Using Source Keys: HDL HCM Data Loader

The document discusses data loading for HCM Data Loader (HDL). It explains that HDL uses .dat files to contain data for workers, jobs, and element entries. It describes two mechanisms for uniquely identifying records being loaded: user keys using a combination of attributes, and source keys using a combination of source system ID and owner. Source keys are recommended as they do not change over time and support translation. The document provides examples of HDL file formatting including using METADATA to define attributes and source keys to identify records.

Uploaded by

swati280591
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
192 views2 pages

Creating A Simple File Using Source Keys: HDL HCM Data Loader

The document discusses data loading for HCM Data Loader (HDL). It explains that HDL uses .dat files to contain data for workers, jobs, and element entries. It describes two mechanisms for uniquely identifying records being loaded: user keys using a combination of attributes, and source keys using a combination of source system ID and owner. Source keys are recommended as they do not change over time and support translation. The document provides examples of HDL file formatting including using METADATA to define attributes and source keys to identify records.

Uploaded by

swati280591
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

HDL

HCM Data loader

.dat file extension


Worker.dat contains data for workers, Job.dat contains data for jobs and ElementEntry.dat
contains data for element entries

When you supply data to be processed by HDL, you must uniquely identify each record in
the file. For new records, two mechanisms are supported:

User Key – a combination of user-friendly attributes that can be found on the user interface,
which uniquely identify the record. For example, the JobCode and SetCode for a Job, the
PersonNumber for a Worker.

attributes that serve as unique identifiers for records

Source Key –

a combination of two attributes, SourceSystemId and SourceSystemOwner, are used to


uniquely identify the record.

The SourceSystemId value can be any value, but is often the identifier on the source system,
or a value generated by an algorithm. The SourceSystemOwner ensures the source key is
unique when multiple source systems exist

The source key is the recommended solution as user key values can change over time and
can often be translated.

The source key doesn't change during the life of the record. You can use the source key to
reference the record from other objects too. Source keys are particularly useful when the
user key attribute is auto-generated by Oracle HCM Cloud, such as PersonNumber.

METADATA|JobFamily|JobFamilyCode|JobFamilyName|EffectiveStartDate|EffectiveEndDate

 The first value on any HDL file line is always the File instruction, in this
case METADATA.
 All files must include METADATA lines to define which attributes are included
in the file and the order in which their values are supplied.
MERGE – additional line to file

Creating a Simple File using Source Keys


Setup and Maintenance.
Manage Common Lookups

Lookup Type HRC_SOURCE_SYSTEM_OWNER

Add

METADATA|Grade|SourceSystemOwner|SourceSystemId|GradeCode|SetCode|GradeName|
EffectiveStartDate|ActiveStatus

METADATA|Grade|GradeCode|SetCode|GradeName|
EffectiveStartDate|ActiveStatus

MERGE|Grade|IC1|COMMON|Individual Contributor 1|2000/01/01|A

GUID

Generated in Oracle fusion when record is created

Held in integeration key map (HRC_INTEGERATION_KEY_MAP) TABLE

Cannot be assigned in the HDL file while creating the business object

Can be assigned in HDL file while updating/deleting business object

Surrogate ID

Generated in Oracle fusion when record is created

Unique only for the object type

Cannot be assigned in the HDL file while creating the business object

Can be assigned in HDL file while updating/deleting business object

You might also like