ETL92: Punch End And Punch End R Dates From IPT Tables Are Different From Reported Time. (Doc ID 3079459.1)

Last updated on APRIL 07, 2025

Applies to:

Symptoms

The Issue is with how the Punch End and Punch End R dates are being modified and updated by the Time Admin 9.2 codeline.
The Reported Time does have a value when it is submitted and these values should not be modified or updated as it is effecting the processing of the client rules.

Steps to Recreate:
1: Entered Time for Feb 25th, Start Time = 8AM, End Time = 5PM, TRC = KUREG.
2: Submitted Time.
3: Entered Time for Feb 24th, Start Time = 8AM, End Time was not entered, TRC = KUREG.
4: Save for Later (This would allow the entry to be saved to Reported Time as an SV entry for Reported Status).
5: Ran SQL for the Employee’s Reported Time (Feb 24th Reported Status = SV, Punch_Dttm = 24-FEB-2025, 8 AM, Punch End = 25-FEB-2025, 8AM) This simulates what the Kronos Time Clocks would send to Reported Time via Integration Broker to the PeopleSoft T&L system).
6: Updated the Reported Status for 24-FEB-2025 from SV (Saved) to SB (Submitted). This status also represents how the Kronos Integration sends the Reported Time to PeopleSoft.
7: Ran SQL on the Reported Time row for the employee after the update to Reported Status.
8: Ran Time Administration for this employee.
9: Queried the Reported Time, IPT, and Punch Match Tables
NOTE: The Punch_End and the Punch_End_R have been updated to 24-FEB-2025 8AM which is different than the original reported time.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.