Fusion Absence Management - Carryover Not Correctly Calculated When Initial Balances Uploaded via HCM Data Loader (HDL)
Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Fusion Absence Management Cloud Service - Version 220.127.116.11.0 and later
Oracle Fusion Absence Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Absence balances were loaded on the last day of the previous absence term year, to create an initial carryover balance.
When the employee has a balance to be carried over from the legacy system of less than 5 (e.g. 3 days, or 0 days), the carryover is still being calculated as 5.
When the carryover expires, the correct amount is being expired (e.g. 3 days).
The issue can be reproduced at will with the following steps:
1. Load closing balance from legacy system on last day of plan year, using HCM Data Loader (HDL).
2. Run the accrual process for current plan year to calculate carryover
3. Observe that the carryover is 5, if the employee has less than 5 days to carryover.
4. When the carryover expires, the correct amount is expired.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms