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.

Conversion from V1 to V3 and implementing V3 Seniority dates for Classic pages

edited Nov 13, 2024 3:49PM in Human Capital Management 1 comment

Summary:

Background: Conversion from V1 to V3 and implementing V3 Seniority dates for Classic pages. We created 2 new rules linked to the Profile and were expecting the migrate process to use those per documentation. The process deleted the custom rules and created the ones with Migrate. The Migrate rules are non-Cumulative and are creating seniority dates for Pending Worker

(1) We wanted to achieve these requirements 2 using our custom rules. How do we ignore creating Pending assignment seniority date and make the rule cumulative?

(2) If we use the oracle created migrate rules to populate the seniority dates for Hire/Rehire. The Enterprise Seniority date is linked to Pending worker (as it’s a Person level seniority date?). When retrieving the seniority date we ignore the Assignment number? Is this expected functionality for Enterprise Seniority Date – Person Level.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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