ETL: Duplicate Payable Time With Failed Processes and Employee Reporting More Time.
(Doc ID 1636016.1)
Last updated on FEBRUARY 01, 2018
Applies to:PeopleSoft Enterprise HRMS Time and Labor - Version 9.1 and later
Information in this document applies to any platform.
On : 9.1 version, Time Administration
Duplicate payable time is created in error. On Thursday we run TA every hour so payable time is generated for the period which ended the day before( Wednesday). We run it frequently on Thursdays so mgrs can approve generated payable time. Our noon run abended with a deadlock- TA was the victim.(see attachment) We were unawares for an hour. Meanwhile, a user was running time admin ad hoc. I noticed that two were kicked off within seconds, which isn't good. At 1:10 we restarted the noon run. It finished immediately. I waited a few minutes before kicking off the 1 am run. It took ten minutes to finish. Please see attached for screen print of error in log from noon TA run and the process monitor showing the run times.
During our deep dive on one employee who had duplicate hours, we noticed the process instance in TL_TR_STATUS matched another process being run at 12:43.
Payable time should only be created by one process being run and the other processes should not pick up the same employee already being run.
The issue cannot be replicated easily as it is definitely related to multiple processes being run close together, insufficient temp table instances and one of the processes abending due to a deadlock error with the temp table being locked.
They cannot be certain that employees aren't being overpaid during normal payroll processing.
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