Create Accounting keeps reporting Error 95937 Or keeps processing the records even even after the ERROR COUNT exceeds the value defined for ERROR LIMT in Accounting Options screen
(Doc ID 1302612.1)
Last updated on SEPTEMBER 21, 2017
Applies to:Oracle Subledger Accounting - Version 12.1.3. and later
Information in this document applies to any platform.
Checked for Relevance on May-15-2013
ConcurrentProgram:XLAACCUP - Create Accounting Program
Create Accounting keeps processing the records even even after the ERROR COUNT exceeds the value defined for ERROR LIMT in Accounting Options screen
Create Accounting keeps reporting Error 95937 in the Output that says
"There are either non-accountable events existing in the system, or events which could not be processed because no data could be found on transaction objects. Please enable the profile option SLA: Enable Diagnostics,create accounting again, and run the report Transaction Objects Disagnostics to identify the problem."
A new feature namely "Connection Tagging" has been introduced into 12.1.3 which is meant for auditing or managing the resources efficiently.
Profile FND_CONNECTION_TAGGING by default have value ENABLED from R12.1.3 onwards.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!