Fusion Global HR: Calculate Seniority Date Process Does Not Return Correct Results
(Doc ID 2850729.1)
Last updated on FEBRUARY 25, 2022
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
After running the Calculate Seniority date process using a custom role, the process does not update the seniority date to correct values.
i.e. Seniority Date: 12/31/4712 and Total Seniority Date Adjusted: -984,999.
This is happening only for one rule - Benefit eligibility date.
The rule is using a fast formula in place for this benefit eligibility date seniority date calculation.
The issue can be reproduced at will with the following steps:
1. Seniority Dates page:
Rule: Benefit Eligibility Date
Seniority dates were last calculated on 1/10/2022
Seniority Date: 2/29/2016
Length of Service: 5 years 10 Months 14 Days
Total Seniority Days Adjusted: 0
Click on "Recalculate Seniority" button > Confirmation - The request was submitted, Process Request ID: 684487
2. Monitor Processes Schedule Processes page
Submit new ESS job: Calculate Seniority Dates > Request ID = 684487 (completed with Succeeded)
Person Number: xxx
Past Period in Days: 25550
Include Terminated Work Relationships: Yes
Include Complete Assignment History: Yes
Selected Seniority Date Rules: Benefit Eligibility Date, Time Accrual Date, Cumulative Hire Date, Most Recent Hire date
3. Go to Home > Employment > Seniority Dates > Search for person xxx >
Result: Wrong Seniority Date
Seniority Date: 12/31/4712
Total Seniority Date Adjusted: -984,999
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document