ABAP - Keyword Documentation → ABAP RAP Business Objects → RAP - Behavior Definitions → RAP - BDL for Behavior Definitions → 

    RAP - BDEF Extension

    A BDEF extension is a transportable extension of a RAP behavior definition. BDEF extensions can be added to the BDEF implementation types managed, unmanaged, projection, and abstract. A BDEF extension itself can be extended. This is referred to as extension layering.

    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.

    • Section Extensibility Enablement: As a prerequisite for BDEF extensions, the behavior definition or BDEF extension to be extended 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.
    • Section Abstract BDEF Extension: All available extension features for abstract BDEFs are described.

    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.

    Each BDEF extension automatically inherits the release contract of the original RAP BO. Therefore, BDEF extensions must also meet the specifications of the release contract and need to be kept stable.

    Hints

    • 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.

    Further Information

    Continue