ETL9.2:How to Determine What Date Range TL_TIMEADMIN is Processing and How to Correct Calendar with Period ID not Built Error?
(Doc ID 2443059.1)
Last updated on JULY 21, 2020
Applies to:PeopleSoft Enterprise HCM Time and Labor - Version 9.2 and later
Information in this document applies to any platform.
On : 9.2 version, Time Administration
TL_TIMEADMIN Fails ,
TL_TIMEADMIN is scheduled to run every half hour and has been successfully doing so. It ran successfully at 9.00AM but then failed at 9.20am with the following message:
Calendar with Period ID not built out to cover 2010-10-08 through 2018-08-30.
It's true that period does not go back to 2010 but why is that suddenly a problem? Why is TIMEADMIN looking back that far?How should we determine the cause and resolve this issue?
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