Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
V3 Seniority Date - Impact of Cumulative option
Summary
Need some explanation on Cumulative optionContent
I went through the document Document 2476188.1 - Common Use Cases Configured Using V3 Seniority Dates. In this, it is mentioned that if Cumulative option is enabled for any rule, then break in service will be excluded and only the net service period will be considered. However I see that the Enterprise Seniority Date gets changed accordingly.
I need some clarification on this.
Example:
- Cumulative option is enabled at Enterprise Seniority Date at Person Level
- Employee was hired to LE1 on 01/01/2014 and termed on 12/31/2015. Now the Enterprise Seniority Date will show as 01/01/2014 with Length of Service as 2 years.
Tagged:
0