Transitioning from HCM File-Based Loader to

HCM Data Loader

A Detailed Guide to Migrating to HCM Data Loader
ORACLE WHITE PAPER | NOVEMBER 2018
TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER
Table of Contents

Introduction 1

Planning 1

HCM Data Loader Scope Parameter 1

Spreadsheets 2

Zip File Format 2

Dat File Format 3

Mapping Business Objects 4

Key Types 5

Build 5

Map the HCM File-Based Loader Object File to the HCM Data Loader Component 5

Convert the File Header Line 6

Determine Which Key Resolution System to Use 7

Convert All Dates to the Oracle Fusion Integration Standard Format 8

Add the Business Object Component Discriminator 8

Add HCM Data Loader Instructions 8

Add Source System References (Optional) 9

Generate a Single Business Object Hierarchy File 9

Generate the HCM Data Loader Zip File 9

Web Services 10

Automation 10

0 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

Introduction
This document provides guidance to customers migrating from HCM File Based Loader to HCM Data
Loader.

Planning
It is important to plan the migration from HCM File-Based Loader to HCM Data Loader carefully and fully understand
the scope of work involved. The file format in which HCM Data Loader requires data to be presented is different from
that required by HCM File-Based Loader. This means that the export process that generates the data will need to be
reworked. Customers should create an inventory of interfaces, objects, and attributes used by HCM File-Based
Loader. This inventory should include data loaded using the HCM File-Based Loader spreadsheet loader.

In addition, it is recommended that customers review both current and future HCM Data Loader release
documentation, so that they are familiar with all HCM Data Loader functionality available to them, such as the ability
to load flexfield data or document records.

HCM Data Loader Scope Parameter

The setting of the HCM Data Loader Scope parameter controls the behavior of loading tools in the Oracle HCM
Cloud application. This parameter has two values, Limited and Full.

For customers who upgraded from Release 9 to Release 10, the HCM Data Loader Scope parameter was set to
Limited by default. Since Release 10, the default setting of the HCM Data Loader Scope parameter for all new
customers has been Full.

The effect of these settings of the HCM Data Loader Scope parameter is as follows:

HCM Data Loader Scope Description

Limited You can use HCM Data Loader to load only those
business objects that are not supported by its
predecessor, HCM File-Based Loader.

Full You can use HCM Data Loader to load all supported
business objects. You cannot use HCM File-Based
Loader, which is disabled.

You set the HCM Data Loader Scope parameter on the Configure HCM Data Loader page.

If you are no longer using HCM File-Based Loader or its related spreadsheets, then you should update this
parameter to Full so that you can use HCM Data Loader for future bulk data loading.

Note: The HCM Data Loader Scope parameter cannot be set back to Limited once it has been set to Full. Once
this parameter is set to Full, HCM File-Based Loader and its related spreadsheets no longer function.

An environment refresh can restore your environment to its state before HCM Data Loader was enabled. That is, it
can set the HCM Data loader Scope parameter back to Limited. Plan an environment refresh to revert your
environment to using HCM File-Based Loader before running an end-to-end test of the migration process. See the
document Oracle Applications Cloud Service Definition - Environment Refresh (2015788.1) on My Oracle Support
for more information.

1 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

Spreadsheets
In Release 11 and earlier, customers who have the HCM Data Loader Scope parameter set to Limited have access
to the HCM File-Based Loader spreadsheet loader in the Data Exchange work area. Customers who have the HCM
Data Loader Scope parameter set to Full do not have access to these spreadsheets.

The spreadsheet loader functionality available in the Data Exchange work area was enhanced in Release 12. This
enables customers who have the HCM Data Loader Scope parameter set to Full to access the HCM Spreadsheet
Data Loader in the Data Exchange work area. New tasks and function security to secure these tasks have been
introduced. For more information, see HCM Spreadsheet Data Loader Access Requirements in the Integrating with
HCM guide on the Oracle Help Center.

HCM Spreadsheet Data Loader enables users to design and configure spreadsheet loader templates to suit their
business needs. HCM File-Based Loader spreadsheet users moving to HCM Spreadsheet Data Loader will need to
configure templates to enable users to upload data. See HCM Spreadsheet Data Loader Templates: Explained in
the Integrating with HCM guide on the Oracle Help Center. Sample templates can be found on Cloud Customer
Connect. Under Global Human Resources, select HCM Cloud Integrations. On the HCM Cloud Integrations page,
select HCM Spreadsheet Data Loader in the Integration Resources section.

Zip File Format

Both HCM Data Loader and HCM File-Based Loader process compressed .zip files. However, the content of these
.zip files differs. HCM Data Loader .zip files contain business-object-hierarchy-specific .dat files directly in the .zip
file, not in subfolders. The only subfolders that are permitted in a HCM Data Loader .zip file are to provide files to
load as attachments or into large object data types. You supply a .dat file for business objects that have changes to
load to Oracle Fusion. The .dat files contain all components of the business-object hierarchy for which the .dat file is
named.

Figure 1. HCM Data Loader Zip File Format

HCM File-Based Loader .zip files contain subfolders for each business object being loaded. Each subfolder contains
a separate file for each business object component to be loaded.

Figure 2. File-Based Loader Zip File Format

2 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

Dat File Format
The HCM Data Loader .dat file can contain all attributes for all components of a business object hierarchy. The HCM
File-Based Loader .dat file is restricted to the attributes for a specific business object component. Both file types
require a definition line that specifies which attributes are included, but, as there can be multiple definition lines in an
HCM Data Loader .dat file, the HCM Data Loader definition line contains an additional component discriminator.

HCM File-Based Loader files can only specify data to be created or updated in Oracle Fusion, but HCM Data Loader
also supports data being deleted. The HCM Data Loader lines therefore also contain an instruction not required in
the HCM File-Based Loader .dat file.

Both .dat files expect attributes to be pipe-delimited. This table provides a comparison of the .dat file components in
HCM Data Loader and HCM File-Based Loader.

TABLE 1. COMPARISON OF DAT FILE COMPONENTS

File Component HCM Data Loader HCM File-Based Loader

Definition Line You supply one definition line for each An HCM File-Based Loader .dat file is specific to a business
Required in both types business object component you are object component. For this reason, you do not need to supply the
of .dat file providing in the file, for example, Worker, name of the component on a definition line within the file, but you
PersonName, WorkRelationship, do need to specify the names of the attributes included in the file.
WorkTerms, or Assignment. Format:
Format: <attribute 1>|<attribute 2>|…|<attribute n>
METADATA|<component
discriminator>|<attribute 1>|<attribute
2>|…|<attribute n>
The METADATA line lists the name of the
component it is for and all attributes that
are included, in the order they are
provided.

Attribute Names HCM Data Loader attribute names are HCM File-Based Loader attribute names are uppercase with
The attribute names mixed-case without spaces or underscores.
are listed on the underscores. They are derived from the Examples:
definition line in both View Object (VO) that supports the
business object component. EFFECTIVE_START_DATE, EFFECTIVE_END_DATE,
types of .dat file. The JOB_CODE
attribute names used Examples:
in both cases are very EffectiveStartDate, EffectiveEndDate,
similar and can be JobCode
easily mapped, but
they have a different
format.

Data Lines HCM Data Loader allows you to specify HCM File-Based Loader has no requirement for an instruction or
whether the data is to be MERGEd into component discriminator.
Oracle Fusion or DELETEd from Oracle Format:
Fusion. All data lines must provide the
correct instruction to specify the required <attribute 1>|<attribute 2>|…|<attribute n>
action. As the HCM Data Loader .dat file
can contain data for any of the
components in the business object
hierarchy, the component discriminator
must also be specified on every data line.
Format:
<instruction>|<component
discriminator>|<attribute 1>|<attribute
2>|…|<attribute n>

Date Format YYYY/MM/DD YYYY-MM-DD

3 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

File Component HCM Data Loader HCM File-Based Loader

Keys HCM Data Loader supports four key types: HCM File-Based Loader uses a GUID that is specific to HCM File-
user key, source key, surrogate ID, and Based Loader. It is the only key mechanism available when
GUID (Globally Unique Identifier). providing data for upload to Oracle Fusion using HCM File-Based
Loader.

Mapping Business Objects

HCM Data Loader supports many more business objects than HCM File-Based Loader. For those business objects
that are supported by both, different components and attributes may be available to each solution.

You will need to map the business objects, components, and attributes that you currently load using HCM File-
Based Loader to the HCM Data Loader files and discriminators, altering the attribute names from the HCM File-
Based Loader uppercase and underscore to the HCM Data Loader mixed-case attribute names. You can identify the
HCM Data Loader attribute names from the business object template files, which you can generate from the Initiate
Data Load user interface in the Data Exchange work area.

When performing this mapping, you can also identify whether there are additional components and attributes that
you wish to bulk load. For example, Job supports the bulk loading of Job Evaluation and Job Extensible Flexfields,
using HCM Data Loader.

Figure 3. Job Business Object, Mapping HCM File-Based Loader Files to HCM Data Loader File Discriminators

Where previously you generated a new .dat file for each business object component and grouped these together in
a folder, now you include all business object components in one business-object-specific .dat file.

Figure 4. Comparison of HCM File-Based Loader and HCM Data Loader Zip Files

It is possible to generate and download templates from the Initiate Data Load page in the Data Exchange work area.
The template file shows all attributes that can be uploaded for each object. It contains flexfield segments that have
been configured in the system and provides the full set of parent and child components for a particular business
object. This feature is available regardless of the HCM Data Loader Scope parameter setting. More information can
be found in HCM Data Loader: Overview in the Integrating with HCM guide on the Oracle Help Center.

4 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

Key Types
HCM File-Based Loader uses a GUID that is specific to HCM File-Based Loader. It is the only key mechanism
available when providing data for upload to Oracle Fusion. It requires that you maintain a mapping on your source
system in order to be able to maintain that data in Oracle Fusion or reference that data from other business objects
loaded using HCM File-Based Loader.

HCM Data Loader supports four key types. To reference data in Oracle Fusion, you are recommended to use the
source key type. This will allow you to continue to use the HCM File-Based Loader GUID values when referencing
existing data, and your own source system ID values for new data being loaded. HCM Data Loader also supports
user keys. These are attributes visible on the Oracle Fusion user interfaces that uniquely reference Oracle Fusion
data, for example, the job code for a Job object.

The Integration Object User Key Map Extract extracts the Oracle Fusion GUIDs, source keys, surrogate IDs, and
user keys for a specified business object. For example, you can extract all key values for all instances of the Worker
business object. To identify the business object, you specify its file discriminator. You can limit the extract to specific
components of the business object by specifying a component file discriminator value. For example, you could
specify the WorkRelationship file discriminator to extract keys for Work relationship component of the Worker
business object.

Before you can use HCM File-Based Loader GUID values as source keys with HCM Data Loader, you must first
copy your HCM File-Based Loader GUID values into source keys. A process is provided to do this for you. For more
information, see the document Copying HCM File-Based Loader GUIDs to HCM Data Loader Source Keys
(2291681.1) on My Oracle Support.

When referencing foreign objects in a record, it is important to consider that the Source System Owner attribute is
common for all source keys supplied in that record. Therefore, the foreign objects referenced by source key must
have the same Source System Owner value.

Build
The following steps explain how to convert an HCM File-Based Loader file to the HCM Data Loader format, to help
you better understand the differences between the two.

Map the HCM File-Based Loader Object File to the HCM Data Loader Component
In HCM File-Based Loader, each object is presented in a separate file. You need to identify which HCM Data Loader
business object component this maps to using the mapping spreadsheet that can be found attached to the
document Transitioning from HCM File-Based Loader to HCM Data Loader (2212149.1) on My Oracle Support.

For example:

HCM File-Based HCM Data Loader

HCM File-Based Loader HCM Data Loader
LoaderTop-Level Business Object
Object Business Object Top-Level Business
Business Object Component (File
Component (.dat file) Object (Folder)
(Folder) Discriminator)

Job Family JobFamily F_JOB_FAMILY_VO.dat JobFamily JobFamily

Employee Person F_PERSON_ADDRESS_VO.dat Worker PersonAddress

Address

5 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

 HCM File-Based HCM Data Loader
HCM File-Based Loader HCM Data Loader
LoaderTop-Level Business Object
Object Business Object Top-Level Business
Business Object Component (File
Component (.dat file) Object (Folder)
(Folder) Discriminator)

Work Terms WorkRelationship F_WORK_TERMS_VO.dat Worker WorkTerms

Contact Email Person F_PERSON_EMAIL_VO.dat PersonContact ContactEmail

Address

The worker object in HCM Data Loader is a combination of the Person and WorkRelationship objects in HCM File-
Based Loader. It is not possible to create a Person object separately from a WorkRelationship object.

Convert the File Header Line

The HCM File-Based Loader header line uses the database-table column names, whereas HCM Data Loader
attribute names are derived from the business object services. You need to convert your existing header attributes
to those supported by HCM Data Loader. These can be found by generating template files for the business objects
you wish to convert on the Initiate Data Load page in the Data Exchange work area.

For example, the HCM Data Loader JobFamily header line contains the following attributes:

Attribute Name Key Type Alternate User Key Type

JobFamilyId Oracle Fusion surrogate ID JobFamilyName Number

JobFamilyName User key String

JobFamilyCode User key String

ActiveStatus String

ActionReasonCode String

EffectiveStartDate Date

EffectiveEndDate Date

SourceSystemId Source key String

SourceSystemOwner Source key String

GUID Oracle Fusion GUID Raw

These attributes map to the existing HCM File-Based Loader attributes:

HCM Data
HCM File-Based Loader Attribute
Loader Attribute

JobFamilyId The Oracle Fusion surrogate ID attribute is

not used by HCM File-Based Loader

JobFamilyName JOB_FAMILY_NAME

JobFamilyCode

ActiveStatus ACTIVE_STATUS

6 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

HCM Data
HCM File-Based Loader Attribute
Loader Attribute

ActionReasonCode User key for ACTION_OCCURRENCE_ID

EffectiveStartDate EFFECTIVE_START_DATE

EffectiveEndDate EFFECTIVE_END_DATE

SourceSystemId *1 JOB_FAMILY_ID

SourceSystemOwner New attribute for the source system owner

GUID N/A

*1 Using the Copy HCM File Based Loader GUID values to HCM Data Loader Source Keys process, you can
continue to use HCM File-Based Loader GUID values by supplying them as source keys.

Any HCM File-Based Loader attributes that are not being mapped to HCM Data Loader attributes, or are never
supplied with values, should be removed from the file.

These examples show the differences between the two header lines.

Current data file:

JOB_FAMILY_ID|EFFECTIVE_START_DATE|EFFECTIVE_END_DATE|JOB_FAMILY_NAME|BUSINESS_
GROUP_ID|ACTION_OCCURRENCE_ID|ACTIVE_STATUS|ATTRIBUTE_CATEGORY|ATTRIBUTE1|ATTRI
BUTE2|ATTRIBUTE3|ATTRIBUTE4|ATTRIBUTE5|ATTRIBUTE6|ATTRIBUTE7|ATTRIBUTE8|ATTRIBU
TE9|ATTRIBUTE10|ATTRIBUTE11|ATTRIBUTE12|ATTRIBUTE13|ATTRIBUTE14|ATTRIBUTE15|ATT
RIBUTE16|ATTRIBUTE17|ATTRIBUTE18|ATTRIBUTE19|ATTRIBUTE20|ATTRIBUTE21|ATTRIBUTE2
2|ATTRIBUTE23|ATTRIBUTE24|ATTRIBUTE25|ATTRIBUTE26|ATTRIBUTE27|ATTRIBUTE28|ATTRI
BUTE29|ATTRIBUTE30|FT_ALTERNATE_REC|FT_ALTERNATE_KEY
e836fd6a0b8f4dbfa075b8db7289bc23|1900-01-01|4712-12-
31|Recruiting|||A||||||||||||||||||||||||||||||||JOB_FAMILY_TBL|NRS001::1900-
01-01
e836fd6a1c804dasdf07fad9bc223ax3|1900-01-01|4712-12-
31|Analysis|||A||||||||||||||||||||||||||||||||JOB_FAMILY_TBL|NRS002::1900-01-01

New data file:

JOB_FAMILY_ID|EffectiveStartDate|EffectiveEndDate|JobFamilyName|ActiveStatus
e836fd6a0b8f4dbfa075b8db7289bc23|1900-01-01|4712-12-31|Recruiting|A
e836fd6a1c804dasdf07fad9bc223ax3|1900-01-01|4712-12-31|Analysis|A

Determine Which Key Resolution System to Use

The most natural key type for continuing the use of HCM File-Based Loader GUIDs is to use it as a source key. To
achieve this, change the attribute name for the existing GUID attribute to SourceSystemId. You will need also to add
the SourceSystemOwner attribute to the beginning of the file header and the source system owner value to each
line.

Current data file:

JOB_FAMILY_ID|EffectiveStartDate|EffectiveEndDate|JobFamilyName|ActiveStatus
e836fd6a0b8f4dbfa075b8db7289bc23|1900-01-01|4712-12-31|Recruiting|A
e836fd6a1c804dasdf07fad9bc223ax3|1900-01-01|4712-12-31|Analysis|A

New data file:

7 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|JobFamilyN
ame|ActiveStatus
EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900-01-01|4712-12-31|Recruiting|A
EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900-01-01|4712-12-31|Analysis|A

Convert All Dates to the Oracle Fusion Integration Standard Format

HCM File-Based Loader files require dates to be in the format YYYY-MM-DD. Each hyphen (-) must be replaced
with a slash (/).

Current data file:

SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|JobFamilyN
ame|ActiveStatus
EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900-01-01|4712-12-31|Recruiting|A
EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900-01-01|4712-12-31|Analysis|A

New data file:

SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|JobFamilyN
ame|ActiveStatus
EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recruiting|A
EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Analysis|A

Add the Business Object Component Discriminator

You will need to add the correct file discriminator for the business object component that you are converting.

The discriminator should be added to the beginning of each line along with the pipe delimiter.

Current data file:

SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|JobFamilyN
ame|ActiveStatus
EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recruiting|A
EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Analysis|A

New data file:

JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|
JobFamilyName|ActiveStatus
JobFamily|EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recruiting
|A
JobFamily|EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Analysis|A

Add HCM Data Loader Instructions

The header line must be prefixed with the METADATA instruction and the pipe symbol. The data lines must be
prefixed with the correct data line instruction along with the pipe symbol.

Current data file:

JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|EffectiveEndDate|
JobFamilyName|ActiveStatus
JobFamily|EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recruiting
|A
JobFamily|EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Analysis|A

8 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

New data file:
METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Effectiv
eEndDate|JobFamilyName|ActiveStatus
MERGE|JobFamily|EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recr
uiting|A
MERGE|JobFamily|EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Analy
sis|A

Add Source System References (Optional)

HCM Data Loader supports you in specifying references from the source system to allow you trace this file line back
to the source system record. These references can be added anywhere in the line.

Current data file:

METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Effectiv
eEndDate|JobFamilyName|ActiveStatus
MERGE|JobFamily|EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recr
uiting|A
MERGE|JobFamily|EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Anal
ysis|A

New data file:

METADATA|JobFamily|SourceSystemOwner|SourceSystemId|EffectiveStartDate|Effectiv
eEndDate|JobFamilyName|ActiveStatus|SourceRefTableName=PER_JOBS|SourceRef001=JO
B_ID|SourceRef002=EFFECTIVE_START_DATE
MERGE|JobFamily|EBS|e836fd6a0b8f4dbfa075b8db7289bc23|1900/01/01|4712/12/31|Recr
uiting|A||NRS001|1900-01-01
MERGE|JobFamily|EBS|e836fd6a1c804dasdf07fad9bc223ax3|1900/01/01|4712/12/31|Anal
ysis|A||NRS002|1900-01-01

Source reference attribute values can take any string value. If you are supplying date values, then supply them in
the format in which you want to see them displayed on the user interface and in error reports.

Generate a Single Business Object Hierarchy File

Add the transformed file lines for all components of a business object hierarchy to a single business object .dat file.
Ensure the name has the HCM Data Loader specified file name for your business object hierarchy.

Current data file name: F_JOB_FAMILY_VO.dat

New data file name: JobFamily.dat

Generate the HCM Data Loader Zip File

You can choose how to deliver your data, either by individual business object or with multiple business objects to be
processed together. Compress the business object .dat files as required into .zip files, ensuring that the .zip file
contains the .dat files in the root directly. Business object .dat files are not to be included in subdirectories within the
.zip file.

9 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

Current data file:

New data file:

To help validate files before loading them, you can use the HDL Offline Validator tool. This tool enables you to
perform most of the data formatting validations, even before loading the data to Oracle HCM Cloud. See the
document Data File Validator Tool for HCM Data Loader (2022617.1) on My Oracle Support.

Web Services
Both HCM Data Loader and HCM File-Based Loader provide web services to initiate loading of your file. However,
different services with different parameters are provided for each.

The web services and instructions for using them are documented in these whitepapers on My Oracle Support:

» Automating HCM Data Loader R11, which is an attachment to the document Oracle HCM Data Loader: User
Guide (1664133.1) on My Oracle Support.
» Integrating File-Based Loader with Oracle WebCenter Content (1595283.1)

Automation
To automate the loading of HCM Data Loader files, see Automating HCM Data Loader R11, which is an attachment
to the document Oracle HCM Data Loader: User Guide (1664133.1) on My Oracle Support.

10 | TRANSITIONING FROM HCM FILE-BASED LOADER TO HCM DATA LOADER

 Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200

CONNECT W ITH US

blogs.oracle.com/oracle
Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
facebook.com/oracle warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.

oracle.com Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 1118

Transitioning from HCM File-Based Loader to HCM Data Loader

November 2018