Description and Definition of HCM Data Loader

DESCRIPTION AND DEFINITION OF HCM DATA LOADER
Author: Ashish Harbhajanka
INTRODUCTION
HCM Data Loader also referred to as HDL ( abbreviated form) is the next generation tool from Oracle for loading legacy HCM data
into Fusion Applications.
Starting with Release 9 July Monthly Update (Monthly Update Bundle 9.7).
Oracle strongly recommends that all NEW Customers begin using HDL.
Customers currently provisioned on Release 9 will require a configuration change.
All environments provisioned in Release 10 will be defaulted to HDL.
Existing Customers may continue using File Based Loader (FBL) but should begin evaluating HDL to plan a migration in the future,
where applicable.
There are a few scenarios where HDL may not be recommended, and an exception may be considered, for both, existing and new
Customers.
SITUATIONS WHERE HCM DATA LOADER MAY NOT BE RECOMMENDED
a) An existing customer using File-Based Loader who purchases additional test environment that is created on R10.
b) The customer must log an SR to change the default setting of Full to Limited to match other environments.
c) Customers with PeopleSoft Integration.
d) Customers with Taleo Integration via Taleo Connect Client (TCC) and File-Based Loader.
MIGRATING FROM FILE-BASED LOADER TO HCM DATA LOADER
1. Is File-Based Loader used for migration only? If so, once migration is complete, then HCM Data Loader could be considered.
2. Is File-Based Loader used for ongoing integration? If so, then there will need to be rework of processes and a cutover decision.
3. How are File-Based Loader data files generated? Whatever method is used for generating the File-Based Loader data files will
need to be reworked to generate the correct HCM Data Loader format.

4. The complexity of the integration will need to be taken into account to determine who does the rework of the extract
mechanism.
5. Are you loading objects outside of File-Based Loader and HCM Spreadsheet Data Loader (via SR requested scripts)? If this is
causing delays and issues related to lack of automation, then HCM Data Loader should be considered.
6. Are there users who load data using HCM Spreadsheet Data Loader? A move to HCM Data Loader in R10 would disable
this
7. Functionality, so it would probably be worth waiting for spreadsheet support. HCM Data Loader migration should be treated
as an implementation with a proper project plan. File-Based Loader GUID values can continue to be used with HCM Data
Loader. A process can be run to convert the File-Based Loader GUID into a source key that HCM Data Loader can recognize.
8. HR spreadsheet loaders in the Data Exchange work area will not be available to use in conjunction with HCM Data Loader
9. HCM Data Loader and File-Based Loader cannot be used at the same time for objects supported by both.
10. Payroll batch loader is still required for some payroll object loads.
11 Environment refresh will overwrite HCM Data Loader settings if the source environment uses File-Based Loader. You will
have to follow the process again to enable HCM Data Loader and convert File-Based Loader GUIDs and source keys.
12. Once HCM Data Loader is enabled in a test environment, no additional File-Based Loader load testing will be possible
NEW IMPLEMENTATION CONSIDERATIONS
1) Customers who have recently started implementing and have not yet gone live should consider switching to HCM Data Loader
if their timelines can accommodate it.
2) This will mitigate the need for conversion to HCM Data Loader later in the project lifecycle. Project plans should be reviewed
to incorporate the migration to HCM Data Loader, taking into account:
3) Training on the new tool
4) Rework of the extract mechanism to get data in the HCM Data Loader format
5) The need to test the migration and integration processes using HCM Data Loader instead of File Based Loader
6) The need to fit in with major implementation milestones
CONSIDERATIONS FOR EXISTING CUSTOMERS
1. Existing live customers already using File-Based Loader and HCM Spreadsheet Data Loader should defer the switch to HCM
Data Loader.

2. Customers who are not yet live should evaluate whether to rework their implementation to use HCM Data Loader or continue
using File-Based Loader and HCM Spreadsheet Data Loader.
3. The main work involved in using File-Based Loader and HCM Data Loader is the extract of the data from a source system to
the correct format ready for loading. Since this is not part of Oracle Fusion, Oracle does not provide a conversion process from
File-Based Loader to HCM Data Loader.
4. Oracle does provide the migration of File-Based Loader GUID values to the HCM Data Loader equivalent, which are referred
to as source keys.
5. Customers using Oracle Fusion Taleo Recruitment Out of the Box (OOTB) V1 Integration are not impacted.
6. If you are using Taleo Connect Client and File-Based Loader or a hybrid with OOTB to integrate with Fusion, you will need to
perform an evaluation and follow the steps to migrate to HCM Data Loader
HCM DATA LOADER COMPATIBILITY WITH FILE BASED LOADER
HCM Data Loader and File-Based Loader cannot be used at the same time for objects supported by both. Either of them should be
picked for conversion.
The setting of the HCM Data Loader Scope parameter on the Configure HCM Data Loader page determines whether HCM Data
Loader or File-Based Loader is used and controls the behavior of the loading tools. The default value of this parameter is Limited for
existing customers. If you attempt to load data for a business object not supported in the Limited mode, your whole data set will fail.
Limited mode Only business objects not supported by HCM File-Based Loader can be loaded using HCM Data Loader. All
objects that can use File-Based Loader must use File-Based Loader. Any objects that are not available via File-Based Loader
should use HCM Data Loader.
Full mode HCM Data Loader is used for bulk-loading data into all supported business objects. HCM File Based Loader and
HCM Spreadsheet Data Loader are disabled.
Important Note: You can switch from Limited mode to Full mode, but you cannot switch from Full mode to Limited mode. This is a
one-time switch from File-Based Loader to HCM Data Loader.
Once you migrate to HCM Data Loader, HCM Spreadsheet Data Loader is also disabled because it relies on the File-Based Loader
engine to load data to Oracle HCM Cloud. This restriction applies only to the spreadsheet loading that is launched from the Data
Exchange work area. Other spreadsheet data loaders are not impacted by the uptake of HCM Data Loader.

IMPACT OF UPGRADE TO RELEASE 10
HCM Data Loader will be Generally Available in R10 ( also in Release 9 Patch Bundle 7 and above ) but there is no immediate
requirement to migrate to HCM Data Loader.
HCM Data Loader and File-Based Loader cannot be used at the same time for objects supported by both.
On upgrade to Release 10 you will see the HCM Data Loader options available in the application but you should not use HCM Data
Loader if you are an existing File-Based Loader customer until you have completed an evaluation of HCM Data Loader.
Important Note:
There are differences in file format and key structures.
Once the switch to HCM Data Loader has occurred, you will no longer have access to File-Based Loader or HCM Spreadsheet Data
Loader.
If you have a requirement to load documents of record or areas of responsibility, then you can use HCM Data Loader in Limited mode
with no impact on File-Based Loader or HCM Spreadsheet Data Loader, since these objects are not currently supported by File-Based
Loader
ENVIRONMENT MANAGEMENT CONSIDERATIONS
If you are live with File-Based Loader and testing HCM Data Loader in a nonproduction environment, then you should plan your
environment refresh (P2T) requests carefully.
When you request an environment refresh, the HCM Data Loader settings will be overwritten, and the environment will revert to the
default Limited mode.
You will need to go through the same steps as before to switch back to HCM Data Loader. That is, you must convert File-Based
Loader GUIDs to HCM Data Loader source keys and switch HCM Data Loader Scope to Full.
During the HCM Data Loader migration validation and testing, important testing considerations must be included in your planning.

HCM Data Loader in Full mode is not compatible with File-Based Loader; therefore, it is not possible to have an environment with
both HCM Data Loader and File-Based Loader at the same time.
This will impact your ability to test File-Based Loader transactions in your nonproduction environment while you are in the process of
validating HCM Data Loader.
Important Note: You will need to ensure that the HCM Data Loader enabled environment is not required for any File-Based Loader
testing prior to setting the HCM Data Loader Scope to Full.
MIGRATION STEPS FOR MOVING FROM FILE BASED LOADER TO HCM DATA LOADER
It is not possible to move to HCM Data Loader for individual core objects on an incremental basis. It is a one-time migration and
requires careful planning and preparation to ensure a smooth transition.
CHOICE OF KEYS
One of the most important decisions when considering the upgrade from File-Based Loader to HCM Data Loader is whether to
continue to use the same key mechanism as is used in File-Based Loader (GUIDs) or whether to take advantage of the user key
support that is available in HCM Data Loader.
User keys allow objects to be identified in HCM Data Loader using their natural key; for example, Job Code, Person Number, and so
on.
File-Based Loader GUIDs have an equivalent in HCM Data Loader known as source keys. These are values that are defined in the
source system and stored alongside the Oracle Fusion surrogate keys when objects are created in Oracle HCM Cloud. Source keys can
be used to reference objects when loading related data or to identify specific objects when performing updates or deletes.
Within HCM Data Loader, each object can use different types of keys, so a decision needs to be made on an object-by-object basis to
determine whether a user key or a source key will be used.
CONVERSION OF GUIDS
In order to facilitate the upgrade from File-Based Loader to HCM Data Loader, a process is provided to migrate the File-Based Loader
GUIDs to HCM Data Loader source system IDs. Regardless of whether user keys or source keys will be used, it is recommended that
this process be run as the first step

TEMPLATE GENERATION
Before reworking the export processes, you can download a template for each business object supported by HCM Data Loader. These
templates take into account any flex-field structures that are already in place. By using the templates, you can accurately outline the
shape of the data that needs to be generated by the reworked export processes.
REWORK OF EXPORT PROCESSES
The main task required for migration to HCM Data Loader is the rework of the export process that generates the data for loading to
Oracle HCM Cloud. This process needs to take into account the correct attributes for the HCM Data Loader objects as well as
preparing the files in the format expected by HCM Data Loader.
The attached spreadsheet provides a mapping between the HCM Data Loader data file name, file discriminator, and attribute name to
the HCM File-Based Loader data file and attribute name.
HCM Data Loader only supports files loaded via Oracle Web-Center Content. If customers are currently using SFTP, then the
processes will need to be changed.
Similar to File-Based Loader, HCM Data Loader has a web service that can be used to invoke the HCM Data Loader processing.
HCM_Data_Loader_
to_File-Based_Loader_Field_Mapping.xlsx
Sample Screenshot (Mapping Sheet)

OFFLINE VERIFICATION USING HDLDI
The offline Data File Validator Tool (HDLdi) and used in the extract process to ensure that the data files being prepared are valid in
terms of the data format. It also checks any business rules that apply to the data contained in the data file where other Oracle HCM
Cloud data is not required as part of the validation.

HCM DATA LOADER PROCESS FLOW DIAGRAM

HDL (HCM DATA LOADER) VS FBL (FILE BASED LOADER) COMPARATIVE ANALYSIS (TOP 10 POINTS)
HCM DATA LOADER ( HDL ) FILE BASED LOADER ( FBL )
HAS NEW FEATURES CUSTOMERS ALREADY ACCUSTOMED TO USING FBL
SINGLE WORKER FILE MULTIPLE FILES TO LOAD WORKER DETAILS
ALLOWS BULK AND DELTA LOAD SPECIAL CONSIDERATIONS REQUIRED FOR DELTA LOAD
ERROR HANDLING MECHANISM IS EASY ERROR HANDLING TAKES LOT OF TIME AND EFFORT
ALLOWS DATE EFFECTIVE HISTORICAL DATA LOAD. NEED TO PASS ONLY
THE (N + 1 )TH RECORD
ALLOWS DATE EFFECTIVE HISTORY LOAD. IN CASE YOU NEED TO LOAD (N + 1)TH RECORD
ALL RECORDS STARTING FROM 1 TO N ALSO NEEDS TO BE PASSED
ORACLE RECOMMENDS FOR ALL NEW IMPLEMENTATIONS ONLY RECOMMENDED FOR EXISTING CUSTOMERS
ENSURES EITHER COMPLETE DETAILS GET LOADED OR NONE. NO PARTIAL
CONVERSION ALLOWED. ALL OR NONE APPROACH
CUSTOMERS ALREADY ACCUSTOMED TO USING FBL. PARTIAL LOAD HAPPENS CAUSING
SYNC ISSUES. MAJOR SETBACK FOR ALL IMPLEMENTATIONS
USES SOURCE SYSTEM KEYS APPROACH. USER FRIENDLY PRIMARY KEYS FOLLOWS GUID APPROACH. PRIMARY KEYS ARE NOT USER FRIENDLY
HDL TEMPLATES ( DATA FILE FORMAT) REQUIRED FOR CONVERSION CAN
BE DOWNLOADED FROM THE APPLICATION INSTANCE ( COMMONLY
REFERRED TO AS POD) ITSELF. NO ADDITIONAL SR (SERVICE REQUESTS)
NEEDS TO BE RAISED
FBL TEMPLATES ARE MADE AVAILABLE ON REQUEST ( VIA SR)
TODAY OR TOMORROW YOU HAVE TO ACCEPT USING HDL. YOU MAY
DELAY USING IT BUT CANNOT AVOID IT.
FBL IS AGE OLD TECHNOLOGY NOW. YOU CAN USE IT FOR NOW BUT IT IS ON THE VERGE OF
EXTINCTION.

SAMPLE HDL FILES
Worker.dat
Worker.dat

Description and Definition of HCM Data Loader

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Description and Definition of HCM Data Loader

Similar to Description and Definition of HCM Data Loader (20)

Description and Definition of HCM Data Loader