Last updated on JUNE 12, 2017
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.2 and later
Information in this document applies to any platform.
We have implemented the oracle's recommended solution to process PUNCH ( Elapsed are still processed via TL_ST_LOADER Process ) Transactions from TCDs using TL_ST_LD_DMN process instead of TL_ST_LOADER.
One Instance ST_LOADER Fails with Unique Constraint Error and other duplicate errors.
Here's our observation so far,
While, the no success scenarios related to TL_ST_LOADER have significantly gone down, We no more see the typical temp table errors with TL_ST_LOADER.
- We had a couple of instances where an instance of the TL_ST_LOADER that we still use to process elapsed punches has picked up the Punch Transactions from the Daemon Process.
One such instance has led to duplicate Punches on timesheet.
On another instance, this has led to cause some Punch transactions deleted from the timesheet. This is very detrimental and is unacceptable to the commonwealth.
- Also, We are seeing occasional Errors, where the DAEMON Process abends on a peoplecode step with no details of the error. In this scenario we just had to resubmit the schedule and it would pick up and process with no issue.
Overall, the new TL_ST_LD_DMN process proved to be much stable and seem to have mitigated most of the issues with the TL_ST_LOADER process. We there fore would like to implement the new DAEMON Job to process Elapsed Transactions as well and would need your guidance and details on how to implement it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms