Skip to Content
author's profile photo Former Member
Former Member

ERROR STATUS IN PTARQ.

Hi,

We had gone live 6 months back and from past few days we are getting issues related to "ERROR" status in ptarq as well as "PTREQ_HEADER" table after the manger approves the leave request. Unable to find the cause of this error. Solution will be appreciated.

Regards,

Abdullah khan

ERR2.PNG (39.0 kB)
ERR1.PNG (18.9 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Mar 12, 2014 at 01:38 PM

    Hi Abdullah

    There are reasons as to why a leave request goes into error and the reasons are as follows:

    There is not enough quota for the leave to be posted/booked on SAP

    Or

    There is a collision with another absence or attendance

    The report RPTARQERR should be run on a regular basis to clear errors of this type. We also run transaction SWPR to restart any workflow that may have gone into error normally due to missing data that is required by the workflow etc.

    The report RPTARQPOST should be set up to run regularly to post the leave and there is now a field 'Post with infotype match' that can be used to reduce the amounts of errors when an identical leave request is found instead of an error it will complete the workflow.

    Best wishes

    Julie

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 11, 2014 at 08:50 AM

    hi abdul ,

    by seeing ur screen shots i came know there is conflict in absence type it is having with same ID over there chk in se38 : - rptarqdbview ...whether there are any conflict types for the same dates over there ... go to ptarq and check in display documents --rptarqdbview . and come to rptarqdel --delete docuemts and delete which are in sent and error status and check again by applying once in portal another leave ..... in portal wat is the status it is showing and in 2001 is it updated or not for that leave types ...

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      ok fine ...go to t-code swia and give the date on the creation date and dont give the time which you got errors u will get there list all with errors and filter them over there and check but this is highly not advisible as you are in production system and i think so you can there get a permanent solution , but check the workflow settings and status after approval the leave requests

  • Posted on Mar 11, 2014 at 10:58 PM

    you can remove error status using rptarqerr and but make sure this leave is already availabke in 2001 as it didn't post it just changes the status and also run rptarqpost with post with infotype match rptarqpost also posts requests with error status

    Add a comment
    10|10000 characters needed characters exceeded

    • In rptarqpost, when it changes status from Error to post, it ll definatey post The report rptarqerr changes only the status from error to post and doenst actually post, read the reports documentation You can check the note and follow the steps, it ll avoid error status when there are no actual errors 1113397 - ESS LEA: Leave records not posted to Infotype 2001/2002

  • author's profile photo Former Member
    Former Member
    Posted on Mar 21, 2014 at 02:19 PM

    Hi

    I note in the screen shot the leave is for year 2013 so is this the issue as we are in 2014. So all the quota would have been used for 2013?

    Best wishes

    Julie

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.