Fusion Absence Management: Unable To Make Absence Type Block Leave Relevant From A Specific Date.
(Doc ID 2228764.1)
Last updated on MAY 08, 2018
Applies to:Oracle Fusion Absence Management Cloud Service - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
You made Absence Type Bereavement-Close Relative as Block Leave Relevant from 01-Jan-2017 . Below are steps followed
1. Navigator > Absence Administration
2. Manage Absence Types > Selected the Absence type Bereavement-Close Relative
3. Display Features tab changed the session effective date to 01-Jan-2017 and then clicked on Update.
4. Changed the Block Leave Status to Display and Edit and then clicked on save and Close.
After this you tried to raise single day Absence(for the same Absence Type ) for an Employee for 14-Sep-2016. Ideally the Block Leave Flag should not be Enabled if we are raising the Absences for the year 2016, but it is enabled and we were able to mark this Absence as Block Leave. You did not encounter any error. Then you checked the configuration for the year 2017 and the Block Leave status was 'Display and Edit'., which is fine.
Then you checked the block leave status from 01-Jan-1951 to 31-Dec-2016 and it was 'Display and Edit' (earlier it was Do Not Display). You then corrected it back to 'Do Not Display' for the period 01-Jan-1951 to 31-Dec-2016 and then you checked it again for the year 2017 and the status got changed to 'Do Not Display '. So, the current system behavior is even if we change the block leave status from 01-Jan-2017 it is changing the status from 01-Jan-1951 .
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!