My Oracle Support Banner

E1: 31A: No Accounting Batch is Created (Doc ID 2126405.1)

Last updated on AUGUST 03, 2020

Applies to:

JD Edwards EnterpriseOne Engineer to Order - Version 9.0 and later
JD Edwards EnterpriseOne Shop Floor Control - Version 9.0 and later
Information in this document applies to any platform.


Running manufacturing accounting R31802a in final mode over records with one or more errors or over records with numerous warning errors, the system generates the PDf report with the batch number, but no accounting records are created in F0911.

After applying the fix for a doubling issue as reported in solution E1: 31A: Open Cursor for Cache Error in R31802A Prevents Creation of G/L Batch Despite Valid Transactions (Doc ID 2040432.1), when running manufacturing accounting R31802A and encountering an AAI error, all remaining work orders do not post and are left in the same state as they were before the run. The Employee Work Center (P012503) displays a message referring to: cursor was not able to be opened because the cache Init was not successful or cache Init I09UI002 was empty.  For release 9.0, ESU JL23536, containing Bug 21843181, has been applied. For release 9.1, ESU JM18729, containing Bug 21554838, has been applied.

cursor was not able to be opened because the cache Init was not successful
cache Init I09UI002 was empty

Errors found in the log provided:
ERROR INFO JDEERR - ID= 2, Error= 4473 - x0903.c, Line= 1068
ERROR INFO JDEERR - ID= 1, Error= 029P - b4000350.c, Line= 684
ERROR INFO JDEERR - ID= 0, Error= 078M - b0900049.c, Line= 2770
Entering jdeCacheTerminate
hCache:[] Nm:[] Recs:0 Curs:0 Hnds:1 Cchs:13 TERM one




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.