ETL9.2:TCD Load Creates Invalid Sequence Number When Process Instance Ends In 000
(Doc ID 2133811.1)
Last updated on JUNE 13, 2019
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.2 and later
Information in this document applies to any platform.
Sequence number 0 is invalid for Reported Time and creates several online page buffer problems and causes time admin to fail in some cases.
The app engine TL_ST_LIB that is called from TL_ST_LOADER AE, includes logic to calculate the unique TL_RPTD_TIME.SEQ_NBR based on the process instance. It takes the last three digits of the process instance and multiplies by 100. See the screenshot of app engine peoplecode attached.
This occurred for one of our TCD loads in this current pay cycle. The workaround was to back out the TCD and reload. The new process instance did not end in 000 and the reported time issues were gone. Here are details from our problem load:
they was first loaded on 11/23/2015 and the process instance is 1820000. This load had issues in production due to zero seq number getting written to TL_RPTD_TIME. The seq number is calculated based on the attached logic. Last three digits of process instance number 1820000 * 100 = 000*100 = 0.
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