• Welcome to the upgraded JDELIST forum and thank you for your patience.
    Please restrict discussions and issues regarding the new forum software to the Off Topic forum. We will be monitoring that forum for issues.
    If you have trouble logging in, please reset your password using the forgotten password form: https://www.jdelist.com/community/index.php?lost-password/
    If you are unable to successfully reset your password, please contact us: Click here!
    We hope that you enjoy the upgraded forum.
  • Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

P0911 Logging JEs for previous period errors


My place of employment is currently upgrading from JDE XE to JDE 9.2, so I am fairly new to JDE 9.2.

When a user accesses screen P0010 to open up the previous period for the General Ledger, that user can immediately create journal entries in P0911 for the previous period, but all other users that attempt to create journal entries for the previous period receive the error message "Date is in this Yr but Prior Mth (PBCO)". However, all other users are able to create journal entries for the previous period the next day.

One attempt to resolve the issue was to clear the cache, have everyone log off/in, and try again but that did not resolve the issue.

Does anyone know what needs to be done to immediately allow the applicable users to be able to create journal entries for the previous period?

Any help would be greatly appreciated.





best solution is to remove F0010 From JDE's "Application Caching" table using P98613.
JDE/Oracle has gone kinda overboard on this, particular since caching of frequently accessed data occurs
- At the hardware level (Controller cache)
- At the OS Level
- At the Database Level

and here's Oracle trying to add another layer of caching.

We removed F0010 from the list in P98613 years ago with no ill effects.


Agree with Larry 100%. IMO, the database caching is a vestige from older releases of E1 when the cost of fetching the data was significantly more than pulling it from memory.