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 Date UI displays hire date instead of calculated seniority date.

edited Sep 16, 2024 9:43AM in Compensation 2 comments

Summary:

We are having an issue where the seniority date UI is not reflecting what is returned in the fast formula used to calculate this seniority date. This is only happening, from what we can tell, to workers that have been created since we went live with Oracle cloud fusion HCM.

Content (please ensure you mask any confidential information):

We migrated to Oracle cloud fusion in May of 2023. We use a seniority date, evaluation due date, that uses a fast formula to calculate when an employee's evaluation is due. The seniority date is set to person level, not cumulative, and Employee worker type only. For employees that have been hired since we went live, meaning, employess not loaded during conversion, this seniority date does not consider the returned value from the fast formula. The formula calculates the correct value, but the UI reflects their hire date. Another detail, if we run Calculate Seniority

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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