E1: ENV: Automatic / Dynamic JDB Table Cache Refresh Does Not Clear the Cache Successfully, Leading to Application Errors Such as PBCO Error After Period Change in P0010
(Doc ID 2759925.1)
Last updated on JULY 20, 2022
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Automatic / Dynamic JDB Table Cache Refresh does not work successfully and table caches are not cleared automatically from applications. Preconfigured applications which are supposed to trigger automatic clearing of cache, fail to clear the cache successfully. This leads to various errors in applications which still read the old data from cache. Hence, it becomes necessary to clear/reset the JDB cache manually using P986116D application which should not be required as per the Automatic / Dynamic JDB Table Cache Refresh functionality.
For example :
P0010 (Company Constants) is configured in UDC 00/RF so that any change of company constants (e.g. Current GL Period) takes effect immediately without having to manually reset the cache . However, when GL period is changed to some period in past and an attempt is made to enter a Journal Entry for this period, a PBCO error is received on screen.
Steps to replicate this issue are given below:
- SETUP DYNAMIC CACHE REFRESH:
- TEST DYNAMIC CACHE REFRESH:
- Ensure P0010 is listed in UDC 00/RF
- Open P0010 and change the GL Period to Current Period -2
- Press OK
- Try to create a Journal Entry with GL Date in Period set above.
- Notice PBCO Error on Screen .
- Ask Administrator to Clear the F0010 Cache Manually and then repeat the test above to notice that no error is received.
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