My Oracle Support Banner

ETL9.2:TIME ADMIN NOT MATCHING OUT PUNCH TO IN FOR TCD TIME REPORTED IN DIFFERENT TIMEZONE THAN BASE CAUSING TLX1540 EXCEPTION (Doc ID 2445906.1)

Last updated on NOVEMBER 26, 2021

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

For employee punches in a Timezone different from the server Timezone, punches with a duration exactly the offset of the Timezone difference are not matching the correct OUT punch to the IN punch.  This causes problems with over 24 hour exceptions, etc.  Our specific example comes up when punches with the EST Timezone have a duration of exactly 2 hours (i.e. 8:00AM to 10:00AM).  Since our server time is MST, the difference to EST is 2 hours.  I have tracked this to TL_TA000600.GA000.Step035.SQL, where the PUNCH_END is compared to PUNCH_DTTM (in the temporary table instance for TL_PMTCH1_TMP).  The table has datetime values that are not adjusted for timezone difference in PUNCH_DTTM; however the values in PUNCH_BEGIN and PUNCH_END are adjusted for timezone difference.
Time Admin not matching OUT punch to IN punch causing payable time to not get created correctly.
 

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

1-Turn on validation for TLX1540 during Time Admin run
2-In Time and Labor Installation add the 'Validation Set'
3-In Time Reporting Template TCD_ID filed needs to be chosen
4-Report time for the employee 1 hour for sep/25 and 4 hours for sep 26 and
make sure TCD_ID field is not empty
5-Run Time Admin for the period of interest.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


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