Differences between PA30 and Leave

Request Application
Purpose
The purpose of this Support Content page is to explain why sometimes we experience
different system behavior between transaction PA30 and the Leave Request Application
(LEA).

Overview
Sometimes customers get some warning/error messages in the ESS (Employee Self Service)
LEA whereas in the transaction PA30 the same action/task does not show the same message.
In this page we will explain why this occurs, why this does not affect the functionality and
how to avoid such inconsistencies.

Explanation
ESS users should not be allowed to use PA30 to book absences directly in the infotype 2001.
This transaction should be only used for the Leave Request Administrator (Admin). Since
PA30 is a framework and Leave Request is one of the applications developed on the top of it,
while booking an absence directly in PA30, it cannot verify with applications which are built
on top of it. Such checks could be done if it would have been another application.

Why this is not a problem?

This system behavior will not affect the business processes. Let's explain the application
behavior for possible scenarios:

 Employee has requested a leave via web application - current status: SENT
(Pending for approval):

In the mean time Admin has booked an absence in PA30 (IT 2001). In normal case, Approver
will approve the request via leave request application and will get the collision error. In such
case approver should inform this and ask the employee to withdraw the request as admin has
already applied and employee also can confirm this before withdrawing the request.

To avoid any inconsistency the best solution would be the admin to first check the status of
request in Leave Database before booking any absence in the Infotype.
  Employee has requested a leave via web application and approver has approved
- current status: APPROVED (Next step is Posting):

In the mean time Admin has booked an absence in PA30 (IT 2001). During the next run of
RPTARQPOST report select the option "Post with Infotype Match" if you would like leave
requests that have already been set as absences to automatically be shown as posted.

 Employee has requested a leave via web application and approver has approved
and POST report has used - current status: POSTED:

If Admin tries to book the absence, he/she will get a collision error message in PA30. Please
note that it does not make sense that Admin books absence without checking if employee has
already requested it.

How to avoid such inconsistency

There is a report available and Admin can make use of it to avoid such inconsistency. You
can use the report RPTARQDBVIEW to view the database of leave requests that your
employees have submitted in the Leave Request Web Application. The Admin needs to run
the report for the employee(s) for which he/she is going to book an absence in PA30. If there
is already a request in leave request database, he/she can take the decision accordingly.