SAP BDL EXTENSION



Get Example source ABAP code based on a different SAP table
  



ABAP_RAP - BDEF Extension
A BDEF extension is a transportable extension of a RAP behavior definition . BDEF extensions can be added to BDEF implementation types managed, unmanaged, and projection.
A BDEF extension can make additions to the original BDEF, but it cannot modify, overwrite, or delete elements from it. The following extensions are possible: field extensibility, behavior extensibility, node extensibility. A RAP BO extension itself cannot be further extended.
Section Extensibility Enablement: As a prerequisite for BDEF extensions, the behavior definition must be explicitly enabled for RAP extensibility.
Section Base BDEF Extension: All available extension features for RAP BOs of type managed and unmanaged are described.
Section BDEF Projection Extension : All available extension features for BDEF projections are described .
The following image shows the role of BDEF extensions within the ABAP RESTful Application Programming Model.
IMAGE BDEF_projection_extension.jpg 641 271
A note on the terminology: the following topics use the terms base RAP BO and base BDEF to refer to RAP behavior definitions of type managed and unmanaged. A base BDEF extension is a BDEF extension that extends a RAP behavior definition of type managed or unmanaged.
original is used as synonym for extended or to refer to BDEF components that belong to the extended RAP BO. For example, original field and original operation refers to fields and operations from the extended RAP BO. The term original can refer to BDEFs of any type or layer. It focuses on the contrast between extended object and extension.

ABAP_FURTHER_INFO
Development guide for the ABAP RESTful Application Programming Model, section Extend.
C0 Contract Rules for RAP Behavior Definitions
DDIC - Extensions
ABAP CDS - CDS Entity Extension
CDS Service Definition Extensions ( EXTEND SERVICE).



Latest notes:

BDEF extensions themselves and each single extension element should use a separate namespace to avoid naming conflicts with extended elements. BDEF extensions created in non-SAP and non-partner development systems should use the customer namespace prefix Z or ZZ.
NON_V5_HINTS
BDEF extensions are connected to Switch Framework whenever they are defined in a package that is assigned a switch.
ABAP_HINT_END

ABAP_CAUT
BDEF extensions for unmanaged RAP BOs are currently still under development. They are not fully supported yet. The following features are currently not supported:
with additional save
Determinations and validations
Node extensibility