Changes to an approved Absence Request can only be entered on or before the leave end date. Changes after the leave end date must be processed by the SPO using the DA I Vacation Request and they will not be reflected in the Absence Request history or the unit report.
The Absence Request cannot be updated after the absence end date has occurred and only the SPO will be able to make the change to the absence period in Direct Access I.
Example: Member's approved Absence Request has an absence begin date of 12 April 2012 and an end date of 16 April 2012. Duration of absence is 5 days. Today's date is 19 April 2012 and it is determined that the member returned on 15 April 2012 vice 16 April 2012. Since the member's absence end date has passed already and the Absence Request is locked down due to it already being processed, the SPO will need to make the changes in Direct Access I Vacation Request.
Corrections, such as in the example above, or deletions, where an Absence Request was entered, approved and transmitted to DA I Vacation Request erroneously, must be deleted from the DA I Vacation Request and, if necessary (in the case of a correction), resubmitted by the SPO in the DA I Vacation Request.
If you, the SPO user, are deleting a row of leave data in order to resubmit it with the correct date(s), you must complete the resubmission IMMEDIATELY after the deletion. The edit, which prevents the creation of new leave requests in DA I, will not permit you to enter the corrected absence request if it does not detect the deletion. Do not exit the DA I Vacation Request, without entering the corrected leave entry. If you have exited the component or your DA connection is broken, and you cannot enter the corrected leave entry, contact PPC Customer Care. The corrected entry can only be entered by PPC (mas) if the SPO deletes a row and does not immediately enter the corrected leave data.