Skip to Content

Errors in B1 Cluster causes time evaluation to retro.

Hi all,

We have a situation in that employees' have errors in the B1 cluster data for missing punch out or in. Of course these errors are causing time evaluation to run retro processing during time evaluation. One Employee I am researching has a mismatch back to 2009. His scheduled work time was 23:59:00 through 7:59:00. In the report, RPCLSTB1, the error message is No Clock-out entry for this date 5/13/2009.

When I look in TEVEN, I see to records for 5/13/2009. Both are P10 or punch in records. one is at 8:02 on 5/13 and the other is 23:37 on 5/13. When I check CATSDB for this date, the punch in and out appear to be matched properly or the supervisor conditioned it to match. I am not sure which.

Further research shows that the employee was paid properly for this time period. Should we be conditioning time and making corrections to the cross application data somewhere other than CAT2 transaction? Should I correct the errors via program RPTERR00? Could there be a flag missing in configuration that is not updating B1 after time punches are corrected?

Thanks,

Connie

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on Aug 19, 2013 at 08:34 PM

    Hi Connie,

    Are you getting any mismatch output due to this retro run in time evaluation, you can try by stopping retro through it0003 retro date under time evaluation,

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 19, 2013 at 09:09 PM

    If Time Evaluation goes back to 2009, it means that some change in Master Data has brought that retroactive calculation. If configured, use the Audit Report (program RPUAUD00) to identify if the change was captured by it.

    To your Business Process, add the execution of an Ad-hoc Query on IT0003 before processing Time Evaluation and Payroll Calculation to identify the employees for whom a retroactive calculation is planned, and confirm the necessity of the retroactive calculation beforehand, correcting the IT0003 retro date when required.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 20, 2013 at 12:38 AM

    Plz check link below to understand how Time Evaluation decide the 1st date to run: How PT60 start

    And if you wanna clear data in cluster plz use RPUP1D00 - using this progam to delete NT2

    Hope it's useful.

    Regards,

    Woody

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 14, 2014 at 07:12 PM

    Hi Kedhar, Woody and Remi,

    Sorry to be away so long, we have had lots of things going on. I have been 'bulldogging' this problem for several days again. I have found that if i change the field for time evaluation retro date on Info type 3, to a more current date, that PT60 issues a warning message: Period to be evaluated 20090827 before earliest recalculation period 201307.

    I have found that I can get rid of the warning if I use RPTERR00 (zrpterr00 - tcode) and 'fix' any mismatches on P10 and P20 punches.

    I am not sure but I think that when our EE 'punches' the time clock they are supposed to press a green button for the punch in and a red button for the punch out. If they press the wrong button,.... green when they leave for the day, this causes an error in the tables TEVEN and CATSDB. Our supervisors correct the punches in CAT2 transaction, which in turns updates CATSDB. However.. the correction for this mistake does not get updated to the B1 Cluster table.

    In QAS I have tested the delete b1 cluster program, RPUP1D00 on one employee who had b1 cluster errors. His PT60 works great and he does not retro in time. I am concerned though if I delete all B1 Clusters. What would the ramifications be?

    Am I missing an update program? is there any way to transfer the fixes made to the punches in CAT2, on to the B1 CLuster?

    Thanks,

    Connie

    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.