ETL9.2: Change to Outpunch Seconds does not Update the Corresponding in Punch End Field. (Doc ID 1963745.1)

Last updated on SEPTEMBER 14, 2016

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

On : 9.2 version, Time Reporting

When an out punch is changed the corresponding In punch is not updated to reflect the new out punch time in the punch end field.

If the out punch is updated with a new value not only should the out punch row contain the new values but the corresponding IN punch row should be updated to reflect the correct end punch value that matches the new out punch.


The issue can be reproduced at will with the following steps:
1. report in and out punches: 12:33:45AM and 05:33:45AM
2. submit the time and verify the results in the physical table
3. change the outpunch to have 05:33:40AM instead
4. check data in table and only the out punch row is updated the in punch end time is not corrected to reflect the new value

The issue has the following business impact:
Due to this issue the end punch on the first in punch doesn't reflect the correct time.

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