My Oracle Support Banner

E1: 31A: Open Cursor for Cache Error in R31802A Prevents Creation of G/L Batch Despite Valid Transactions (Doc ID 2040432.1)

Last updated on APRIL 24, 2021

Applies to:

JD Edwards EnterpriseOne Shop Floor Control - Version 9.0 to 9.1 [Release 9.0 to 9.1]
Information in this document applies to any platform.


R31802A - Manufacturing Accounting

When running R31802A, if there is a work order with errors in the batch of work orders being processed, for example a work order has a DMAAI error, all of the work orders error out with a cache error.  In addition, the F3102 table gets corrupted.

F3102 gets corrupted because the F3102 table is updated with costs incurred, but the transactions are not truly posted - the work order is not updated, the G/L is not updated and so next time R31802A runs, it incurs the costs again and if the error still exists in the batch, the same thing happens and what ends up happening is Actual costs are doubled or tripled than what they actually are. Basically it keeps accumulating until the error is fixed.
The corrupted F3102 can go undetected until the work order variance is run and the variances are all incorrect.
The work center error messages shows the Open Cursor for cache error in R31802A. This error in R31802A prevents creation of G/L batch despite valid transactions.

If there are any errors at the beginning of the batch such as a business unit with PEC = N, this generates a valid error but then the program goes into a loop and generates open cursor cache errors and never finishes and never posts anything in the batch when there are in fact valid transactions in the batch that should get posted to the G/L. All of the work order transactions print on the PDF but NONE of them post because there are errors on the first few work orders. (This issue may have started after taking Update 2).

Another example is with IM transactions. Each time the R31802A was run with the error present, the F3102 was updated with Actual units and Amounts but the G/L was not getting created.  The same open cursor cache errors were generated.  This does not become evident until the work orders go through Variance Accounting (R31804).

Open Cursor for cache IO9UI002 failed


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.