Upgraded from Version 1 to 3. PER_SENIORITY_DATES_F - How is it Populated? — 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
Get Started with Redwood: Oracle Cloud SCM and Purchasing

Upgraded from Version 1 to 3. PER_SENIORITY_DATES_F - How is it Populated?

in Reporting and Analytics for HCM 1 comment

Summary: New table PER_SENIORITY_DATES_F created as part of upgrade to version 3. Can any one share the details of the data migration to this table?


Content (required):

From what I can tell - and in the context of the ORIGINAL_DATE_OF_HIRE, data was migrated from PER_PERIODS_OF_SERVICE into PER_SENIORITY_DATES in version 1 or prior (perhaps this was done manually?)

Then, as part of the version 3 upgrade, ORIGINAL_DATE_OF_HIRE data was migrated from PER_SENIORITY_DATES to PER_SENIORITY_DATES_F (as well as from PER_PERIODS_OF_SERVICE to PER_SENIORITY_DATES_F, in the case of prior periods of service).

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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