AM Self Service forecasting or balance inquiry does not take future forecasted absences into consideration.
(Doc ID 954900.1)
Last updated on MAY 29, 2019
Applies to:PeopleSoft Enterprise HCM Absence Management - Version 9 to 9.2 [Release 9]
Information in this document applies to any platform.
All entitlements are granted at the beginning of the year.
In the beginning of the year, an employee submits requests, for various points in time, using up all his entitlement. The last two separate requests, spending the last two days of entitlement were for November 5 and December 11.
Some time before November 5, the employee decides he would like to request a day off on December 17. He enters the request, forecasts the absence and it is deemed ineligible. This is correct because the last submission was for the 11th and as of that date, the entitlement would be depleted.
However, if he were to put in a request for December 10th it would be deemed eligible. This is also correct, because the self service system does not regard the later date, it looked at the balance as of the November 5 request, which was one day.
The system looks at 'today' or the balance as of the most current previous request, and not future requests.
Likewise, future-dated, non processed absence requests will not be considered in Absence Balance inquiries, using an 'as of date' which precedes the begin date of the future dated absence. The available balance will show what is available 'TODAY'. Thus, if the employee has 20 days available as of January and requests 5 days in November (say, November 14-18, which, although approved, will remain unprocessed until that pay period) and he requests a balance inquiry for an as of date for any day prior to November 14, the balance is still going to be displayed as 20, because the November request has not been processed and has not decremented the available balance.
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