SAP BDL CHARACTER



Get Example source ABAP code based on a different SAP table
  



ABAP_RAP - Entity Behavior Characteristics

ABAP_SYNTAX
... $[persistent table$] TableName
$[draft table DraftTableName$]
$[saving options$]
${$[etag$]
$[locking$]
$[authorization$]$}
$| syntax_short_form
$[early numbering$]
$[late numbering$] ...

What does it do?
This topic gives an overview of all available entity behavior characteristics . Some are mandatory and others are optional. For managed, unmanaged, and draft-enabled scenarios, different characteristics are available and there is also a difference in which ones are required and which ones can be left out. In some cases, the order is important. For example, total etag must always be specified directly after lock master. These details are described in the respective topics.
persistent table Specifies the database table TableName for storing the CDS entity's data changes that result from transactional behavior. Only available for managed RAP BO.
draft table Specifies the database table DraftTableName as draft table for storing draft instances of data changes. This addition is only available for draft-enabled scenarios using the addition with draft.
saving options The default save sequence can either be enhanced or switched off and overwritten with a user-defined saving strategy. Can be defined in the BDEF header and then applies to all entities of the business object. It is also possible to define saving options as an entity behavior characteristic. If specified, an implementation in the ABAP behavior pool is required. Only available for managed implementation scenarios.
etag Optimistic concurrency control .
locking Pessimistic concurrency control .
authorization Defines which RAP BO consumers under which circumstances are allowed to read or change data of a business object.
short_syntax_form: The three statements lock dependent by _assoc , authorization dependent by _assoc , and etag dependent by _assoc can be summarized into one statement: (lock, authorization, etag) dependent by _assoc. For details, see topic TITLE .
early numbering Early value assignment for the primary key fields. Only available for managed implementation scenarios.
late numbering Late value assignment for the primary key fields. Only available for unmanaged implementation scenarios.



Latest notes:

Each characteristic can occur no more than once in a RAP behavior definition.
NON_V5_HINTS
ABAP_HINT_END