My Oracle Support Banner

ETL9.2: ESTIMATED_BATCH_TIME App Message Results In Invalid Accounting Date Sent To Project Costing. (Doc ID 2172267.1)

Last updated on FEBRUARY 04, 2019

Applies to:

PeopleSoft Enterprise HCM Time and Labor - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


ESTIMATED_BATCH_TIME app message results in invalid accounting date sent to Project Costing

The accounting date shouldn't be set to 01-01-1900.


1. The estimated time batch process (TL_PUB_TM_AE) is ran in HCM. -   Time and Labor > Process Time > Publish Estimated Payable Time.  Use 7/1/7/16 as Accounting Date.
2. This triggers the PC_TL_TO_PC process to run in FSCM.
3. Getting warnings in FSCM (from the PC_TL_TO_PC process) that the accounting date is not open and is set to 01-01-1900 in the data that is sent to FSCM.
NOTE: The PY_PULL_COST process (when it is ran in FSCM) is used to retrieve the actual batch time from HCM. The accounting date that comes over via that process is correct.

Due to this issue, The Accounting date of the Time and Labor cost transactions are not synchronized with the accounting period in Project Costing, as well as with the accounting period for other costs that are posted in General Ledger.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.