E1: BSFN: Record Reservation Related Business Functions in EnterpriseOne
(Doc ID 1289755.1)
Last updated on MARCH 06, 2018
JD Edwards EnterpriseOne Tools - Version 8.98 and later Information in this document applies to any platform.
The purpose of Record Reservation is to maintain higher integrity by preventing other users/processes from accessing a certain table simultaneously by recording data into the F00095 - Business Object Reservation table. By implementing this constraint, two different processes do not compete to update/delete a certain table at the same time.
This document is to explain how EnterpriseOne applications make use of user record reservation across the system.
If there is any application which has to update critical information, record reservation routine will take place. This routine comes in Update Mode of the entry point of a transaction or in an application which updates any transaction created by another application.
A simple rule is to determine the target table and get the primary key of it (or primary key of header file) along with the application ID (or UKID).
For further details, review how the table F00095 is structured and how each business function can be implemented in a certain update routine.
This document is for the EnterpriseOne developer and system administrator for the purpose of:
to understand how standard applications reserve records
to implement custom applications which do not hurt standard routines
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!