Problems with RPTARQPOST

SAP's leave posting job (RPTARQPOST) has many problems. It is a nightmare to work with those problems.

Here are they.

1. Maximum number of requests that can be processed at a time:

This is equal to number of lock entries the system can hold (or till "lock table over flow" happens in the system).

As you can see in the pseudo-code in my previous post, the program creates locks into the table PTREQ_HEADER, but clears them only at the end of the program. So teh lock entries keep on cumulating.

Consider an example where your system can give only 8000 locks, and later lock table overflows. In such a case, only first 8000 entries will get a lock and only those will be tried for posting.

2. Deletion of Leave requests:

Many a time, this program has problem with Deleting a leave. The request will get POSTed, but it will not delete a leave.