E1: DB: Transaction, Transaction Processing, Commit and Rollback
(Doc ID 1208208.1)
Last updated on JANUARY 11, 2019
JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later Information in this document applies to any platform.
In industry, a transaction is a transformation of state which has the properties of atomicity (all or nothing), durability (effects survive failures) and consistency (a correct transformation). The transaction concept is key to the structuring of data management applications. The concept may have applicability to programming systems in general.
More commonly, ACID (Atomicity, Consistency, Isolation, Durability) is known as database transaction properties. That is, All or Nothing for critical commitment. So it is important to understand what is a Transaction not only in EnterpriseOne but also industry common. This document contains some possible questions you may have when getting errors such as the ones described here.
Example of Error Message:
Commit Failed or was Cancelled. Transaction not committed. See jde.log for more information.
ASYNCHRONOUS BUSINESS FUNCTION ERROR
And/Or hint in error WEB CLIENT EXCEPTION with xxxEndDocument
Most commonly, <Document 625535.1> Transaction Processing in EnterpriseOne Distribution Applications explains and provides a brief concept on Transaction Processing in EnterpriseOne.
An EnterpriseOne Transaction has to be understood in the context of Transaction File Master Business Function. Refer to <Document 1265902.1> E1: BSFN: Master Business Function in EnterpriseOne.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!