Creating A Simple File Using Source Keys: HDL HCM Data Loader
Creating A Simple File Using Source Keys: HDL HCM Data Loader
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.
Source Key –
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
Add
METADATA|Grade|SourceSystemOwner|SourceSystemId|GradeCode|SetCode|GradeName|
EffectiveStartDate|ActiveStatus
METADATA|Grade|GradeCode|SetCode|GradeName|
EffectiveStartDate|ActiveStatus
GUID
Cannot be assigned in the HDL file while creating the business object
Surrogate ID
Cannot be assigned in the HDL file while creating the business object