Start of Content Area

Component documentation Transactional Area  Locate the document in its SAP Library structure

An area instance version of a transactional area is not active immediately after a change lock is removed using the DETACH_COMMIT method of the area handle; it becomes active after the next database commit instead. The area instance version looks like it is building between the time when the lock is removed and the database commit. No new change locks can be set on the area instance, and read locks access the previous active version. In the case of non-transactional areas, the state of the area instance version is set to active as soon as the DETACH_COMMIT method is executed.

Transactional areas enable data or objects in the area instance versions to join such areas to database contents.

 

Caution

So that the reference between database contents and shared objects is not damaged, changes to the shared objects should be made only in contexts in which the database changes were also made in the current application. During updating, for example, changes to the shared objects should only be made as the corresponding update functional module is being executed.

 

End of Content Area