Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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. (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.

Queries for Seniority Dates V3 Migration

Summary:

As per the query to find out which Version we are currently in, the result shows V2. As per Oracle document, all existing V1 and V2 seniority data are retained in the PER_PERIODS_OF_SERVICE and PER_SENIORITY_DATES tables respectively. Hence, as we are in V2, the data must be available in PER_SENIORITY_DATES but there is no data available in this table when queried. Instead, we can query data from PER_PERIODS_OF_SERVICE table.

Any idea how to know for sure which version we are actually in?

Content (required):

N/A

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!