FUSION ABSENCE ER Duration Is Not Changed According To Calendar Events (Doc ID 2153389.1)

Last updated on JUNE 24, 2016

Applies to:

Oracle Fusion Absence Management Cloud Service - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.10.0.0 version, Absence Processes

ACTUAL BEHAVIOR
---------------
2 Calendar Events have been created and assigned to Work Schedules as Exceptions.
The workschedule is assigned to employee.
When recording an absence both event exceptions are considered and absence duration is calculated as expected.
When removing the calendar event from workschedule the absence duration is not recalculated

EXPECTED BEHAVIOR
-----------------------
The absence duration to be recalculated based on the events assigned to workschedule
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create workschedule: Test_Work Schedule Time and add 2 calendar events as exceptions:
Exceptions:
  Test Holiday4 1 Jul- 8 J ul 2016
  Test Holiday2 2 Jun 8 Jun 2016

2. Add absence for an employee (i.e 31 May to 10 Jun 2016), notice the absence duration = 2 which is correct
3. Remove one calendar event (i.e 2 Jun 8 Jun 2016)=> the absence duration remains 2 => this is not correct
4. Run the evaluate absence process => the absence duration remains 2 => this is not correct, absence duration expected is 7

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Absence Duration is not correct after removing the event attached to workschedule

Cause

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