Ansicht
Dokumentation
ABENBDL_BDEF_HEADER - BDL BDEF HEADER
Addresses (Business Address Services) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
- CDS Behavior Definition Header
implementation_type$[saving options$]
${$[
implementation in class ClassName unique$]$};
$[strict;$]
$[extensible;$]
$[with draft;$]
$[with privileged mode disabling ContextName:$]
$[foreign entity EntityName;$]
${
entity behavior definition $|
define $[own$] authorization context$}
...
Effect
Defines a CDS behavior definition in the CDS BDL. A CDS behavior definition consists of a CDS behavior definition header and one or more entity behavior definitions.
The header can define the following attributes for the entire business object. The implementation type is mandatory, all other attributes are optional.
- implementation type: four different implementation types exist: managed, unmanaged, abstract, projection.
- The default save sequence can either be enhanced or switched off and overwritten with a self-defined saving strategy.
- Can be defined either 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 / entity behavior characteristics.
- If specified, an implementation in the ABAP behavior pool is required.
- Only available for managed implementation scenarios.
- implementation in class ClassName unique: specifies one or more classes which allow the behavior implementation of a business object. In a managed scenario, this is optional and required only if unmanaged components are added to the managed implementation.
- strict: switches on BDEF strict mode. Handled by the RAP framework.
- extensible: if specified, BDEF extensions are allowed. Handled by the RAP framework. Currently, only available for managed implementation scenarios.
- with draft: enables the draft concept for a business object. This allows users to save their changes as draft and resume editing at a later point in time. Handled by the RAP framework.
- with privileged mode disabling ContextName: Enables BDEF privileged mode. The effect is that the authorization context ContextName is automatically disabled when a RAP BO consumer accesses the business object in question with a privileged EML call.
- foreign entity: Defines an entity which is not part of the BO structure as component for the response structures, thus enabling message mapping for other BOs.
The behavior definition header is followed by
- either an entity behavior definition that starts with define behavior for
- or by the definition of an authorization
context that starts with define $[own$] authorization context.
Example
The following example shows a managed BDEF based on the CDS root view entity
DEMO_SALES_CDS_BUPA_2. The BDEF header consists
only of the implementation type, in this case, managed.
General Data in Customer Master General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 7331 Date: 20240427 Time: 051144 sap01-206 ( 69 ms )
