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.

How to limit Enterprise Seniority Date to one record?

Summary:

The enterprise seniority date needs to be limited to only one record per employee, however, this is being split due to a condition we have put into the seniority date calculator formula to gather the correct date.

Content (required):

The seniority dates have been configured as version V3, allowing for advanced configuration options. However, there is no configuration option to limit the number of records for seniority dates. The seniority date calculation needed adjusting for the 'Enterprise Seniority Date', therefore fast formula was used to configure this. However, since configuring this there is an issue where a few employees are having their seniority date split. The following message appears in the ESS Logs for the 'Recalculate Seniority' job:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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