You are on page 1of 3

Oracle Fusion HCM Data Loader (HDL) Keys Significance

HCM Data Loader (HDL) Keys


Supported Key Types:
HCM Data Loader (HDL) supports 4 different types of keys as listed below

1. GUID – Oracle Fusion Global Unique ID


2. Oracle Fusion Surrogate ID
3. Source Keys
4. User Keys

Key Resolution Sequence (Key references are resolved) in the following order:

1. Oracle Fusion GUID

2. Source key

3. Oracle Fusion surrogate ID

4. User key

Important Notes
1. While Create/First time Loading any object(s) we have to consider only SOURCE KEY /
USER KEY no need to think about GUID or Surrogate ID (because those are created only
after an object created in fusion).
2.While Modify/Updating/DELETE any object then all four keys comes into picture.

If you supply multiple key values, then they are used in this order with no cross-validation.
For example, if you supply both a GUID and a source key, then the GUID is used to identify
the record and the source key is ignored. If the source key references a different record from
the GUID, then no error is raised.
These key types are explained below:

Oracle Fusion GUID Oracle Fusion Surrogate ID


Integration Key Generated by Fusion Fusion Generated Unique ID

 Generated in Oracle Fusion when a  Generated in Oracle Fusion


record is created when the record is created
 Hexadecimal value  Numeric value
 Unique across all objects  Unique only for the object
 Held in Integration Key Map type
 Held on the object
Source Keys
Source System Key Information User Keys
User Readable and Generated Keys
 Two values combined:
o SourceSystemOwner  Natural values
o SourceSystemID  One or many attributes
 Held in Integration Key Map  Sometimes alternatives
 Sometimes updateable
 Held on the object definition

Held on Generated
Key Type Create Update Type
Object Automatically
GUID No Yes No Hexadecimal Yes
Surrogate Yes (see note
No Yes Numeric Yes
ID #1)
Conditionally (see note
Source Key Yes Yes No Alphanumeric
#2)
Yes (see note
User Key Yes Yes Alphanumeric No
#3)
Notes:-

1. You can use surrogate IDs when updating objects, but the IDs may not be readily
available to Oracle HCM Cloud users.
2. Default source keys are generated only if you don't supply a source key when creating
an object.
3. You can't use user keys alone when updating some objects because their values are
subject to change.
4. Keys that aren't held on the object exist in the Integration Key Map table.

Integration Key Map table


Keys that aren’t held on the object are stored in the HDL integration key map table
- HRC_INTEGRATION_KEY_MAP. You should be able to use BIP to fire up a SQL
statement and view the contents of this table. e.g.
/* Formatted on 2017/09/12 14:25 (Formatter Plus v4.8.8) */
SELECT object_name
,source_system_id
,source_system_owner
,surrogate_id
,RAWTOHEX (guid) guid
FROM fusion.hrc_integration_key_map
WHERE source_system_owner = 'STUDENT1'

Business
Fusion GUID Source Key Surrage ID User Key
Object
(Set code and
Location 88ABCD164738983 STUDENT1_LOC1 8899933355517 Location Code)
COMMON, HQ1
 Fusion GUID: System generated GUID
 Source Key: Source System Owner is the reference to source application like PS or
EBS, Source System Key is the actual key\id provided in the Location.dat file.
 Surrogate ID: System generated. In this case it is the primary key from locations
record. e.g. select * from PER_LOCATION_DETAILS_F_VL where location code =
'STUDENT1 Location1‘ (Result Location ID = 8899933355517)
 User Key:- Best way to get this info is the Business Object Documentation from MOS
or other option is UI as shown below. Online page should highlight user keys with

There are some amendments in User Account on PROD environment for attached employee list.
Please have a look and take appropriate action.

Best Regards,

Oracle Support Team