How to Create a .dat File Which Will Be Used to Load the Changes Suggested by the "Incorrect Assignment or Terms Numbers" Diagnostic Test via HDL
(Doc ID 2555311.1)
Last updated on DECEMBER 28, 2020
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
When the "Incorrect Assignment or Terms Number" Diagnostic Test is run, it generates a list of Employee's whose Assignment and Work Terms numbers have not been created in accordance with the suggested naming convention/standard. The suggested standard naming convention is either:
The Assignment Type (eg. "E","ET", "CT", "C") followed by the Employee Person Number. For example:
Or, if the employee has more than one assignment then the suggested standard is:
The Assignment Type (eg. "E","ET","CT","C" etc.) followed by the Employee Person Number followed by "-" and then the assignment sequence number. So the second assignment would take the "-2" and if there was a third assignment that would be "-3". For example:
ET123-2/E123-2/ CT456-2/C456-2 etc
The "Incorrect Assignment or Terms Number" will look for people whose Assignment Numbers do not match this convention. When the "Incorrect Assignment or Terms Number" diagnostic test runs, it will output the proposed assignment numbers (to be changed according to this convention), but it does not do this for you. It says:
"The user can resolve this issue via the UI by correcting the Assignment / Term Numbers from Manage Employment -> Edit -> Correct.
Terms Numbers can only be corrected from the UI if the Employment Model is 3 tier"
For 2 tier employment models, it recommends that you load the changes via HDL but only gives an example script. This means, it's necessary to create your own Worker.dat file which can be loaded in via HDL (HCM Data Loader) in order to make the change.
The Goal of this article, is to create a HDL script (by pulling the current data out of the database alongside the suggested changes to implement the naming convention standard).
ER:29930994 has been created to request that this be implemented in the product long term.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document