Get Started with Redwood for Oracle Cloud HCM Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Mapping of Seniority dates after V3 Seniorty Dates migration
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):
0