Mobile Absence Management For Employee (HR_MOB_LOA_ESS) REST Service Function - Absence Category is Not Correct Before Transaction Approve
(Doc ID 2628898.1)
Last updated on JULY 07, 2020
Applies to:
Oracle Self-Service Human Resources - Version 12.2 HRMS RUP13 and laterInformation in this document applies to any platform.
hrabsmobss.pkb
hrabsmobss.pkh
Symptoms
On : 12.2 HRMS RUP13 version, Mobile Applications
ACTUAL BEHAVIOR
---------------
Mobile Absence Management for employee (HR_MOB_LOA_ESS) API creates the absence based on the supplied Absence Type and proceeds to ‘Pending Approval’ as if it was created though ESS (Employee Self-Service).
The Absence Category is also set to the same value as Absence Type which is not correct.
EXPECTED BEHAVIOR
-----------------------
Once the absence is approved the Absence Category is set correctly. This should be ‘Annual Leave’ before and after approve.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Mobile Absence Management For Employee (HR_MOB_LOA_ESS) API creates the absence record.
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 |