E1: DB: Case Study on Deadlocks in EnterpriseOne Applications
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later
Information in this document applies to any platform.
*** check for relevance 9-APR-2012 ***
Through this case study, an actual implementation is discussed to minimize potential deadlocks in EnterpriseOne Distribution, Manufacturing and Financial Modules.
Below are two common tables that can be used to isolate certain transactions:
- F0011 (Batch Header Control Records) Batch header is to be written, when a certain transaction affects General Ledger; to set boundary of transaction
- F00095 (Business Object Reservation) Maintain higher integrity by preventing other users/processes from accessing a certain table simultaneously by recording data into the F00095 - Business Object Reservation table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms