Fusion Absence Management: Absence Concurrency Entries - Dates Overlap with Another Absence
(Doc ID 2687172.1)
Last updated on OCTOBER 09, 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.20.01.0. The note has been reviewed and is current for release 11.13.21.01.0.
Symptoms
Enabled concurrent entry for two absence types.
Scenario 1: Absence type A from 4/11/2020 to 6/1/2020.
- Employee has concurrent entries during this same period: Sick 4/13/2020 to 4/17/2020, Sick 4/20/2020 to 4/21/2020, Vacation 4/22/2020 to 4/24/2020, Vacation 4/25/2020 to 5/1/2020.
-Attempt to update the Absence type A entry generates an error message about overlapping dates.
-If the entries with the overlapping dates are withdrawn, the user is able to proceed to change entry.
Scenario 2: Absence type B entry from 4/4/2020 to 7/1/2020.
- Employee has a concurrent entry: PTO from 4/6/2020 to 4/10/2020.
- User updated Absence type B end date to 5/8/2020 successfully (no error message about overlapping dates).
- Note: In some cases the error message is received for this leave type as well, hence the inconsistent behavior observed.
The goal is to set concurrency to manage the current business situation due to COVID19 and be able to modify the end dates as employees as Time Managers (TMs) are returning to work and will need to modify the original entry that was made.
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 |