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

Attendance/Absence and Clock In/Out Requests Issues

Hi ESS/MSS Gurus,

Good day!

Need your help in determining the root cause of the following concerns encountered while supporting ESS/MSS concerns:

1. For Attendance/Absence Types - Posting is done via a background job running RPTARQPOST. There are two concerns:

a. Approved Attendance/Absences are not posted via the background job but are successfully posted when RPTARQPOST is run in foreground - I was thinking here that this might be a timing issue on the intervals on when the background jobs are being executed. Currently, they are set 30 minutes apart and it would be possible that there might be overlap between instances of the background since there is no checking that the previous run has been completed before the next schedule execution of the job commences. I suggested to either lengthen the interval between the execution of the jobs or provide a checking program which will check whether the old instance has been completed before running the next one. What do you think?

b. Duplicate entries being allowed - In my limited experience in ESS/MSS, the system does not allow the creation of a Attendance/Absence record containing the exact same details as a request that was already entered in the system. For example. if I already filed for a VL for the date 10/20/11, the system will not allow me to create another request for the same date since it will already detect the conflict with the existing record. However, for a specific client, the system allowed such a scenario to occur. Is this the standard behavior of the system or is there any configuration that is done to override the checking of simultaneous requests covering a specific date

2. For Clock In/Out Corrections - Posting is done via background job running RPTCORPOST. The concern here is that during posting, there was an error encountered for the requests resulting in the requests being tagged as error (eventhough if they have already been approved). However, unlike RPTARQPOST which still shows the errors encountered during test run, the erroneous clock in/out entries are not displayed during test run mode. Also, when we tried manually entering the time events in the person's infotype, no error was encountered. Hence, I was wondering if there is a way to reprocess multiple clock in/out requests or is the only recourse to manually enter the time events in the person's master records

Your immediate response is highly appreciated


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Jan 09, 2014 at 01:47 PM

    your in which version of ECC ?

    Check the note 1850514 for test run option not working.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 09, 2014 at 10:22 PM


    a)If you think the jobs are overlapping, check in SM37 and see their runtime, and definitely it would make sense to extend their time interval, but how many entries are they posting, are the jobs running optimally? Check this also, as 30 to 45 min is a decent time interval in this was lot of data is not accumulated to post.

    b) its possible , there was a bug as well, whats your EA HR version and level?

    1771815 ESS LEA: Multiple records generated by RPTARQPOST 1124775 ESS LEA RPTARQPOST: Infotype comparison for appro

    also, try to run rptarspost with POST WITH INFOTYPE MATCH

    Read the reports documentation and field properties also.

    for admin related work check in transaction PTARQ and PTCOR< You ll get all related reports to check and update check for error using RPTCORERR this is for clock in for error status records we have in leave request rptarqerr

    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.