Ansicht
Dokumentation

ABENBDL_BO_INTERFACE_HEADER - BDL BO INTERFACE HEADER

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

- CDS Behavior Definition Header, Interface BDEF

implementation type;
$[extensible;$]
$[use draft;$]
$[with privileged mode;$]
$[foreign entity EntityName;$]
${ entity behavior definition $}
...

Effect

The CDS behavior definition header of an interface BDEF can project certain elements from its base BO. Defining new elements is not possible. All possible elements are listed below. The implementation type is mandatory and all other attributes are optional.

• implementation type: an interface BDEF must start with the keyword interface and it must be based on a CDS transactional interface.

• extensible: if specified, BDEF extensions are allowed. As a prerequisite, the projected BDEF must define at least one entity as extensible.

• use draft: the draft concept can be reused from the base BO.

• For details on the draft concept, see topic CDS BDL - with draft.

• For details on the reuse, see topic CDS BDL - use.

• with privileged mode: BDEF privileged mode can be used. As a prerequisite, it must be specified in the projected BO. For details, see topic CDS BDL - with privileged mode.

• 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 one or more entity behavior definition(s) that start with define behavior for.

An ABAP behavior pool must not be specified. The syntax implementation in class is not supported. An interface BDEF is a BDEF type without runtime handler.

Example

The following example shows an interface BDEF. The projected BO is DEMO_RAP_UNMANAGED_DRAFT_ROOT. The interface BDEF reuses draft handling and standard operations from the underlying BO. It also defines a foreign entity and excludes two fields from the BDEF derived types.

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4428 Date: 20240511 Time: 161011     sap01-206 ( 46 ms )