What's new in Customer Journeys?

Connect and learn more!
Migration of seniority dates from V2 to V3 — 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

Migration of seniority dates from V2 to V3

Received Response
edited Apr 3, 2020 6:11PM in Human Resources 5 comments


Hi All,

We are in the process of migrating the seniority dates from V2 to V3.

On Technical side, what will be the impact to our objects like Custom Fast Formula,Bi Reports and HCM Extracts Where seniority date field is used.

Do we have to modify all the places with the new fields?

Also DBI - PER_ASG_ORIGINAL_DATE_OF_HIRE is used for capturing seniority dates in custom FF.

After moving to V3, there will be new DBI or the same DBI will remain eventhough table is changed?

Please provide your inputs on this. what are the steps you have done for migrating from V2 to V3.

Howdy, Stranger!

Log In

To view full details, sign in.


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