Skip to Content
avatar image
Former Member

Error in Multi Level Approver Scenario in Leave Request

Hi ,

In Case of multi-level leave request  approval once the first level approves the leave a record with 'SENT' status is inserted in the PTREQ_HEADER thereby stopping the RPTARQPOST program which is running in background from posting the leave details into the leave infotype.

Issue

But in some cases the 'SENT' status is not inserted in the PTREQ_HEADER and after the first level of approval the leave details is updated in the leave infotype by the RPTARQPOST program .

At the same time there is a short dump in the system related to the database .

PFA related to the short dump.

Regards,

Dwity Krushna

leave.txt.zip (10.0 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Dec 28, 2014 at 09:10 PM

    Hello,

    PFA?

    How often does this happen? Could it be a problem at the OS level, e.g. file system full?

    Seems to be SAP-standard programs, you should search for any support notes.

    regards

    Rick Bakker

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 29, 2014 at 06:06 AM

    These types of errors are many times very difficult to solve.

    You didn't give much details that how the SENT status is inserted into the database. Since this happens rarely, I would consider things like could things sometimes be happening too fast (or slow). Could the PTREQ_HEADER table be still locked (by approval?), etc.? 

    I can also see from your dump that there is a call to an Z-object ZCL_PT_GEN_REQ_EXIT (BAdI?). Could there be some problem with the code in that object?

    Regards,

    Karri

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Check Rick's answer (and the notes mentioned in that thread). Could be a bug in the standard code.

      Also check if the users have done some changes to the leave after sending it for approval. It could be there is something common in these cases - e.g. user changes leave details etc. and your (or SAP's) code cannot handle the situations properly.

      Regards,

      Karri