1

2
3
4
Oracle Fusion HCM Data Loader provides bulk data loading for any HCM business object registered with it.
To achieve this it is delivered with a delimited file reader, comprehensive staging data model and a multi-
threaded data loader for fast bulk updates to Oracle Fusion Human Capital Management, including
products like Oracle Fusion Global Human Resources, Compensation, Absence Management, Performance
Management, Profile Management, Global Payroll, Talent and Workforce Management.

5
6
Business Object data files and any files to be loaded at Attachments, or into Large Objects are all delivered
in compressed zip files.
Your zip file can be encrypted.

7
Zip files are delivered to the WebCenter Content Server, either using the user interface, or by calling the
web service.

Encrypted zip files are decrypted by HCM Data Loader when they are streamed from the WebCenter
Content server.

8
9
Use this for talk track ..

10
Skip all these slides for process flow go to UI directly

11
12
13
14
15
16
17
18
19
20
21
It is important to understand the hierarchical shape of Oracle Fusion HCM business objects. The majority of
business objects have a hierarchy of components and data is loaded using HCM Data Loader using the same
hierarchical shape.
This allows you to load multiple occurrences for child components in one file. It also allows you to supply
simplified data files when reporting incremental changes.

The business object file will comprise of data lines for each component in the hierarchy you want to load
data for.

<Each business object supported by HCM Data Loader has its own documentation, detailing the hierarchical
shape of the object, along with the attributes that are available for each component of the hierarchy.>

22
Oracle HCM Cloud business objects tend to be hierarchical in nature, with one parent record type and
potentially many child and grandchild record types. For example, the Job object, has a Job parent record
and for children it has valid grades, job evaluation, and two extensible flexfields, also known as EFFs. We
call each of these entities a component of the business object hierarchy.

23
Each component in the business object hierarchy will have its own set of attributes.

All components need a key that can be used to locate the record to maintain it, or to reference it from
another object.
Child components also need a key to uniquely identify their parent record.

24
Then there will a set of attributes that form the components data. For example, the job component
records information such as the job name, its active status, whether the job is full or part time, regular or
temporary. Whereas the Valid Grade component simply references the grade that is valid and the dates
when it became valid and stops being value.

For all components of a business object hierarchy you can see that there are some attributes in common,
highlighted here in orange. On the Job component these JobCode and SetCode attributes are defined as
the user key. A unique way of referencing an individual job. The child components of the Job also have
these same two attributes as we need to know which job the valid grades, evaluation critieria and EFF
records pertain to.

When you supply data for bulk loading using HCM Data Loader, you will need to have an understanding of
the business object shape and the keys that identify local and foreign objects, in order to successfully load
your data.

25
HDL is flexible, although the components are part of a business object hierarchy, they can be loaded in
isolation.

26
27
Every file line must start with a valid instruction.

There are 5 valid instructions in the Data Loader file format.

If you want to override the default Data Loader settings you supply a SET instruction.
Comments are used for user understanding only, they do not get processed by Data Loader.
Every dat file must include a METADATA definition line. One METADATA line is supplied for every
component of the business object hierarchy you intend to provide data for.
To create or update data in the Oracle HCM Cloud you supply a MERGE line containing the data to be
uploaded.
DELETE is used if you wish to purge an object from Fusion. It does NOT support removing individual date-
effective records, but can be used as the different levels within a business object hierarchy, e.g. you can
delete a Person Email Address. NOTE: Not all objects support the DELETE instruction, for example you
cannot delete a complete Worker, just some of the child components within Worker.

28
Every DAT file must contain at least one METADATA line.
You provide one METADATA line for every component of the business object hierarchy you wish to include,
and so it is important to understand the shape of the business object you are loading data for.

Please see the Understanding HCM Data Loader Business Objects training on how to achieve this.

Each component in a business object hierarchy has a discriminator which is unique for that business object.
For example, the Job hierarchy has discriminators: Job, JobGrade, JobEvaluation, JobExtraInfo and
JobLegislative

Every METADATA line includes the business object discriminator immediately after the METADATA
instruction. You then specify the names of the attributes that you are supplying data for. Attribute names
can appear in any order.

The instruction, discriminator and attribute names must be delimited, the default delimiter is the pipe
character.

You do not include METADATA lines for components that you do not use. You should not include attributes
on those METADATA lines if you are not supplying values. This is because every attribute you define in
your METADATA will be validated and used to identify dependencies on other objects. So if you are
supplying the Job.dat file with the Grade.dat file and you have included the JobGrade METADATA line, Data
Loader will not attempt to load the Job file until the Grade file has completed loading to ensure all
referenced grades exist in the Oracle HCM before the Job are loaded.

This is an example of the Job template file. Template files are available from the Initiate Data Load page in

29
the Data Exchange work area. These contain all METADATA lines applicable to each business
object. The Understanding HCM Data Loader Business Objects training explains how to
generate and use these files.

29
The MERGE instruction is used to tell Data Loader you want to create, correct or update data in Oracle
HCM. You do not need to understand if your data will be created or updated.

As with the METADATA lines, after the MERGE instruction you must supply the component discriminator
that your attribute values are for. You then supply your attribute values in the order you defined the
attributes on the corresponding METADATA line.
As with METADATA lines, the instruction, discriminator and attribute names must be delimited, the default
delimiter being the pipe character.

If you are supplying data for multiple components you can choose to provide all your METADATA lines at
the top of your file, followed by all the data lines, or you can intersperse the METADATA and MERGE lines
by component discriminator.
Either way, you must always specify a METADATA line for a component before providing your MERGE lines
for that component.

Ill explain how to provide valid values for your attributes later in this session.

30
The optional SET command is used to overwrite the default behaviour.

31
Now you have some understanding of the METADATA and data instructions Ill explain how to override
some of the default behavior using the SET instruction.

Any SET instruction must be supplied first in the file, before any METADATA, MERGE or DELETE
instructions.
The SET instruction can be used to override:

32
SET PURGE_FUTURE_CHANGES <Y/N>
We will discuss this during date effective updates topic but this the command for HDL retain\replace mode.
Y Replace, N Retain

SET DISABLE_POST_PROCESS_TASKS - We will discuss this during post conversion programs discussion, the
command is used to stop auto run post HDL.

SET ENABLE_INCREMENTAL_LOAD_EVENTS - Under CA we wont be discussing this today

33
If you want to override the default behaviour with SET commands they must come first
COMMENT lines can be anywhere in the file after any SET commands
METADATA lines must be before any MERGE/DELETE lines for the same discriminator, but you can choose
to either list all METADATA lines first, followed by the data lines, or intersperse the METADATA lines with
the data lines.

You can supply the data lines by component type, or by logical object, e.g. all data lines for Job Accountant,
followed by all data lines for Job Administrator.

34
35
36
37