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
|