ESS Leave Posted after one year

[Former Member]

Hi

1) We applied leave from dated 22nd Mar 2013 and it was approved by
manager on the same day. However there was an error in PTARQ. But it was posted
after 13 months 22 APR 2014.Can anyone letus know the reason behind it???

2) The other leave– 2013 – this was never posted. Applied leave on 11 JAN 2013, it was
approved, but then there was an error on the record, and it was never deducted
from his leave.

Please someone suggest us on this.

Regards,

Naveen Kumar B

[Former Member]

Execute the report RPTARQERR once u can see the list of employees for whom the status is in ERROR , this will be running by your time administrator who have sufficient authorizations ......and one more thing i need to ask how the salary has been for that employee in that  month did it proceesed corrctly or not ?

[siddharthrajora]

move HCM ESS. Unless the error is fixed, Rptarqpost wont be successful in posting the request, so once the error was fixed probably then it posted the issue check the error in log of rptarqpost on why it failed or in rptarqdbview. and there is a options approved and with errors only? did you change the variant for the report to consider the error records now in rptarqpost? Also note that the reason sometimes leave request are not posted is due to the fact that the current personal number was locked due to payroll, a collision occured etc, You can do foreground run and verify run the rptarqerr or rptarqerr_all to see all error status records and note that error status records are always tried to be posted again by rptarqpost, if they are already posted you can change status via rptarqerr

[Former Member]

I don't know what kind of leave request scenario you are using, but let's assume it is the standard one (or standard with slight modifications). The idea is that employee submits the leave, and then the leave is approved by someone. After this the leave request will get status APPROVED. Now there is a report RPTARQPOST that will go through all the leave requests that are in status APPROVED and tries to post them (normally this report is scheduled as background job). If for some reason the leave request cannot be posted, you should be able to see this in the log of the report RPTARQPOST (or the log of the background job).

1) Perhaps the reason why the leave request couldn't be posted was removed 22 Apr 2014, and now the posting report was able to complete the posting.

2) What is actually the problem reading this second issue? There is an error why the request couldn't be posted to the infotype. This is how it should work, isn't it? You either clear the reason and then complete the posting, or perhaps ask the employee to change the request or submit a new one.

Regards,

Karri

[Former Member]

Hi All,

@ Rick: Yes, When checked in  SWI1 logs related to respective workitem number it gives work item number doesn't exist.it may archived. Is there any other way to find the logs for respective workitem number.

@Pradyp:

1) for only one user

2)No

3)Yes it was posted through background job after 1 year.

4)Yes backgroung exists

5) 15 mins

@Kerri:

1)Can you please eloborate the query regardin first question.

2)The second issue is after approving the leave it went into error status and we couldnt find the logs. Please find the above screen which is in error state and however we could n't find the error log for workitem number.

Regards,

Naveen Kumar B.

[Former Member]

I think you can forget the workflow / work items / workflow logs etc. The problem is purely in the background report RPTARQPOST. The report cannot post the request data into the infotype. Why? Have a talk with a time management specialist - he/she can probably present you lots of ideas why a leave request cannot be posted to the infotype 2001. (Or you could try to manually enter the leave request data to the infotype in PA30, and see what is the possible error.)

It is possible that you will never find a reason for the issues number 1. For the second issue: Execute the report RPTARQPOST  in SE38. Set the flag into the "Display log" checkbox. As far as I remember this will then display a log of the posting run, and possibly show you the error message(s). Or if this "Display log" checkbox has been set up for the variant that is used for the background job, you might be able to find the log in SM37.

Regards,

Karri

[Former Member]

Hey Naveen

This Issue looks completely strange, can you brief me up the issue by answering the following .

Is this happening with only one user or for all??? Is there any specific leave type that is causing the error? Have you checked the RPTARQPOST report? Is this scheduled as a  background job?? Can you let me know what was the frequency applied for it.

Try executing the report manually & check with one scenario.

Hope this Info will be Helpful

Cheers

Pradyp

[former_member185167]

Hello,

Is there a workflow involved? If so, check the log in SWI1 to see if it gives any clues.

regards

Rick Bakker