E-AM: New Component to Properly Update Workflow Status When Absence Administrator approves an Employee Self Service Absence.
(Doc ID 2088835.1)
Last updated on APRIL 23, 2019
Applies to:PeopleSoft Enterprise HCM Absence Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The "Absence Event" screen (Global Payroll and Absence Management, Payee Data, Maintain Absences. Absence Event) was not designed to integrate with the workflow associated with Self Service (Employee or Manager) absence requests.
1. Employee submits absence request through Employee Self Service pages (Self Service>Report Time>Time Reporting>Absence Request.
2. Absence Administrator approves the absence through the Absence Event pages (Global Payroll and Absence Management>Payee Data>Maintain Absences>Absence Event or Global Payroll and Absence Management>Payee Data>Maintain Absences>Create and Maintain Absences).
3. Employee reviews his Absence Request History: -Self Service>Time Reporting>View Time>Absence Request History. On this main page, the status of the particular event displays as 'approved', however if the user hits the hyperlink for the specific absence, the individual page shows the status under Workflow is "Approved" but the status under "Request History Status" displays as "Submitted-Saved for Later"
4. Under the approval monitors screens (Workforce Administration>Self Service Transactions>Approvals and Delegation>Monitor Approvals), if the Administrator chooses to review transactions under the approving manager, these approved absences display as still 'pending' for that manager.
NOTE: This is a display issue only and does not impact absence processing. If the absence take process is run, the absence is considered approved and the take will be calculated.
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