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

Mapping of Seniority dates after V3 Seniorty Dates migration

Received Response
125
Views
3
Comments

Summary:

We are using PER_PERIODS_OF_SERVICE table's - ORIGINAL_DATE_OF_HIRE( as Enterprise Seniority Date) & ADJUSTED_SVC_DATE (as Legal Entity Seniority Date).

After V3 we should be using PER_SENIORTY_DATES_F table and we are thinking of replacing ORIGINAL_DATE_OF_HIRE( as Enterprise Seniority Date) with BASE_SENIORITY_DATE and ADJUSTED_SVC_DATE (as Legal Entity Seniority Date) with SENIORTY_DATE columns from PER_SENIORTY_DATES_F

Content (required):

Kindly advice whether our mapping's are correct or we should be using any other column from PER_SENIORTY_DATES_F.

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!