HDL - FblToHdlKeyCopyJob Found Duplicate Values And Created # Suffix

(Doc ID 2121249.1)

Last updated on MARCH 28, 2016

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version and later
Information in this document applies to any platform.


On : version, HCM Data Loader

After moving from FBL to HDL, executed the "Copying Oracle Fusion File-Based Loader GUIDs to HCM Data Loader Source Keys" scheduled processed which resulted with a warning.
In the log file attached we can see the following:
"This process has completed in warning because duplicate values were found in your existing Oracle

Fusion GUID values for WorkTerms and Assignment records. In order for your Oracle Fusion GUID values
to be used as source keys with HCM data Loader the values must be unique. To achieve this a suffix has
been applied to the original value. WorkTerms values have the #W suffix. Assignment values have the #A
suffix. For example, 193042#A where 193042 is your original value."

The WorkTerm and assignment records do not share the same key (FBL) so we wonder why it says they share it. Besides, we executed the same process on another pod with same data in December and it worked perfectly fine. The integration key map table is now full of Assignment and WorkTerm records suffixed by # something.

The business impact is we can not perform data load anymore either in pre-production or production pod. Indeed, keys in the customer database are desynchronized with fusion database.

keys in the customer database should be synchronized with fusion database.

The issue can be reproduced at will with the following steps:
1. FBL to HDL migration .


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms