In the case of the implementation type unmanaged, the application must implement all significant components of the REST contract itself All required operations (CREATE, UPDATE, and DELETE plus any application-specific actions) must be defined in the associated behavior definition before being implemented in ABAP.
The behavior pool, a special global ABAP class, is used to implement the transactional behavior of a business object. Behavior pools refer to behavior definitions. The actual implementation is based on ABAP and is divided into two phases:
- an interaction phase (implemented using one or more local handler classes)
In this interaction phase, the application performs writes and reads that need to be evaluated and whose effects (if without errors) need to be saved to a transactional buffer.
- a save phase (implemented using a local saver class)
The save phase consists of a sequence of calls to synchronize the involved business objects. The method save is the last call in this sequence, in which changes can and must be written to the database.
The basis class for the handler and saver class is class CL_ABAP_BEHV. It defines data types to be used in the behavior implementation (for example, %CID and %PID). The following classes are derived from the basis class:
The basis class for the handler class. It offers the implementation of methods for handling messages.
The basis class for the saver class. It specifies the signature of all transactional methods that are used to implement the saver sequence.
7.31 | 7.40 | 7.54