What does it do? The RAP 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 TITLE .
For details on the reuse, see topic RAP 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 TITLE .
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.
ABAP_RESTRICTIONS
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.
BDEF strict mode cannot be defined explicitly. Strict checks are automatically applied. ABAP_RESTR_END
ABAP_EXAMPLE_VX5 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 a field from the BDEF derived types. BDEF DEMO_RAP_INTERFACE_DRAFT ABAP_EXAMPLE_END
