ETL9.2: KABA Time Not Updating PUNCH_END Field Correctly

(Doc ID 2352755.1)

Last updated on MAY 08, 2018

Applies to:

PeopleSoft Enterprise HCM Time and Labor - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

KABA Time not updating PUNCH_END field correctly

STEPS
-----------------------

1. Use KABA to interface theTime Clocks with Peoplesoft Time and Labor.
2. An employee had the following punches:
DUR SEQ_NBR PT PUNCH_TIME PUNCH_DTTM PUNCH_END DTTM_CREATED TL_QUANTITY
11/11/2017 90701 1 1/1/1900 7:59:06.000000 AM 11/11/2017 7:59:06.000000 AM 11/11/2017 12:02:08.000000 PM 11/11/2017 4:21:26.475198 PM
4.05
11/11/2017 93402 3 1/1/1900 12:02:08.000000 PM 11/11/2017 12:02:08.000000 PM 11/11/2017 12:32:48.000000 PM 11/11/2017 4:22:32.889415 PM 0.51667
11/11/2017 94003 1 1/1/1900 12:32:48.000000 PM 11/11/2017 12:32:48.000000 PM 11/11/2017 12:32:48.000000 PM 11/11/2017 4:22:47.847513 PM 0
11/11/2017 94603 2 1/1/1900 12:59:52.000000 PM 11/11/2017 12:59:52.000000 PM 11/11/2017 12:59:52.000000 PM 11/11/2017 4:22:46.512585 PM 0

- The punches are in SEQ_NBR order.
- Punch 94003 (an In Punch) did not get the PUNCH_END Date update to 12:59:52 by End Punch 94603 like it should have.
- Punch 94003 was actually created after Punch 94603 according to the DTTM_CREATED time stamp.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms