My Oracle Support Banner

ABMGT - Modified Expected Return Date Does Not Persist For Approved FMLA Absence (Doc ID 2804679.1)

Last updated on SEPTEMBER 07, 2021

Applies to:

PeopleSoft Enterprise HCM Absence Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Extended absence requires modification to end date.  Administrator changes the date and saves for later.  When re-accessing the event, the changed date did not persist.

1. Signed into environment as the admin and accessed extended absences via 'Administer Extended Absences" navigation.
2. Via the 'edit' button, opened one of the existing approved absences.
3. Changed the expected return date to reflect one week later (from 30 April to 7 May).
4. Validated the event (successfully)
5. Clicked 'save for later'.
6. The save was successful and the new date was reflected after hitting 'ok' and was taken back to the request screen.
7. Re-accessed extended absences via 'Administer Extended Absences" navigation.
8. In the list of approved extended absences, the new expected return date is not displayed on employee's request.
9. Open the request and the old date is displayed.
10. Sign out as admin and now sign in as employee.
11. Click Time Tile
12. Click Extended Absences tile.
13. Old date displayed.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.