Fusion Australia Absence Management: Accrual Mismatch Caused by Incorrect Forfeit Remaining Values that Do Not Match Total Carryover Value for Employee and Orphan Records Found
(Doc ID 2525169.1)
Last updated on APRIL 04, 2024
Applies to:
Oracle Fusion Absence Management Cloud Service - Version 11.13.21.01.0 and laterOracle Fusion Absence Management - Version 11.12.1.0.0 and later
Information in this document applies to any platform.
This note was created for Release 11.13.19.01.0. The note has been reviewed and is current for release 11.13.21.01.0.
Symptoms
Employee Accruals are incorrect due to Forfeit Remaining values being generated that do not match the Total Carryover Accrual for an employee.
The leave plan is set up to be in line with Australian legislation where leave accruals are incremental without any expiry or limits.
- Carryover element is not being generated from 2017->2018.
- Employee has "Forfeit Remaining" elements which do not align with the closing balance of the previous calendar year.
Example: As of 31/12/2017 the employee has a balance of 109.77 hours, but there is a Forfeit Remaining for -124.77 hours for 1/1/2018. Problem is repeated again for 2018 to 2019. The employee tried to withdraw the accruals to the 30/11/2017 and then Calculate Accruals through to 2019, but it does not seem to fix the problem.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |