HDL: Changing Non-Primary to Primary Work Relationship Creates Extra Effective Sequence — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

HDL: Changing Non-Primary to Primary Work Relationship Creates Extra Effective Sequence

in HCM Data Loader (HDL) 1 comment

Summary:

Changing Non-Primary to Primary Work Relationship Creates Extra Effective Sequence

Content (please ensure you mask any confidential information):

Hi Team,

We are attempting to change a non-primary work relationship to primary using HDL. However, the system is generating an additional effective sequence for this change, even though we have set the DateForPrimaryFlagChange to the hire date.

Is this expected behavior? If so, could someone please point me to an Oracle document or note that explains this.

Has anyone else encountered this issue? Appreciate your insights or any workarounds you might have used.

Version (include the version you are using, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!