ETL 9.2: Performance Issues With TL_RAPIDTIME.
(Doc ID 1928012.1)
Last updated on JUNE 23, 2023
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
Rapid Time (TL_RAPIDTIME) process took approximately 25 minutes to run 1 employee with only 1 reported time data. Trace was ran in online environment to determine at which step took the longest time to process. From the generated trace file, it was determined that the step TL_ST_LIB GA000_E Step121 had the longest processing time. This step did not exist in the original PS9.2 Vanilla copy, and is determined to be added as part of the PUM Image #5 update. In addition to this, the step TL_ST_LIB GA000_P Step151 for punch employees processing also did not exist in the PS9.2 Vanilla copy, and is part of the PUM Image #5 update.
The process should run in an acceptable time
STEPS
-----------------------
1. Navigate to Time and Labor-> Report Time-> Rapid Time
2. Select a Elapsed Time Reporter for Template Type
3. Input Elapsed employee
4. Input date, TRC type, and number of hours
5. Save and submit to begin processing of TL_RAPIDTIME
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 |