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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.

Seniority Date considering "Create Offer" date instead of "Hire Date"

edited Nov 30, 2022 1:29PM in Human Capital Management 1 comment

Summary:

Person level Seniority Date should consider "Hire" date of the person but for the people who are hired through recruitment process having seniority date as "Create Offer" date.

Configuration and Version of Seniority Date:

Currently we are using V2 version Seniority Date

Result: System is taking Create Offer 29/09/2022 as Seniority Date – Person Level instead of Hire Date 03/10/2022.

Expectation: As shown in above example System should take Hire Date 03/10/2022 as Seniority Dates-Person Level “continuous start date”.

Additional Info:

For testing we have tried using Worker Type "Employee" filter in the configuration. And we have hired new person using recruitment process but we are facing the same issue.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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