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.

Seniority Migration V2 to V3: Override Seniority Basis

edited Jun 26, 2023 2:22PM in Workforce Management 3 comments

Summary:

  1. If Override Seniority Basis is populated as "Days" for each Seniority Date Rule, is is required to populate "Basis for Seniority Calculation" for each worker's assignment?
  2. I'm missing several columns on the Seniority Date Rule page.


Content (required):

Hello Experts,

Two part question. We are migrating from V2 of Seniority Dates to V3. Our seniority date rules are quite straightforward and we are not looking to make any changes at this point.

Current Rules:

Enterprise Seniority Date-Person Level

Legal Employer Seniority Date-Work Relationship

From 23B document "How to Override Seniority Basis" (https://docs.oracle.com/en/cloud/saas/human-resources/23b/faigh/how-to-override-seniority-basis.html#s20068608),

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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