Description

The entity behavior body can consist of the following elements:

• FieldCharacteristics: RAP field characteristics define properties for RAP BO fields that restrict access to the fields in question. For example, a field can be defined as mandatory read-only.
• FieldNumbering: Defines managed internal numbering for key fields.
• RAP BO operations: RAP BO operations implement the RAP BO behavior.
• validation: Validations check the consistency of a RAP business object instance.
• determination: Determinations calculate or determine field values at runtime.
• Events: RAP business events are events that can be used for asynchronous communication.
• side effects: RAP side effects define interdependencies among BO properties that trigger a reload of the affected properties on the user interface.
• BDEF alternative key: A BDEF alternative key defines a user-defined BDEF key. There are pure keys and secondary keys and they are used, for example, in RAP key functions.
• TypeMapping: A RAP type mapping is required if the field names from database tables differ from field names of the CDS data model.
• group: Implementation grouping makes it possible to divide the implementation-relevant parts of a business object's business logic into multiple groups for behavior implementation, each with its own implementation class.