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 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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.

Seniority Dates in 23B

edited Jun 14, 2023 3:25PM in Human Capital Management 3 comments

Summary:

Hello, 

Currently we are in 23A using V2 and It co-exists with V1.  Based on our business requirement we would like to continue to use V1.

1. The SQL query determines V2

2. The tables that stores Seniority Dates is PER_PERIODS_OF_SERVICE which is of V1

3. From the UI the Enterprise and Legal Employee Seniority Date defaults the Hire date in the Hire flow and other employment flows.

4. Both the above dates are visible and can be managed from the Quick Action < Work Relationship >

If we chose not to migrate to V3 when V2 is decommissioned in 23B , I understand that V1 will remain.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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