Get Example source ABAP code based on a different SAP table
• EXTENSIBLE ABAP_BDL_PROJ_EXT
ABAP_RAP - Extensibility Enabling for Projection BDEFs
ABAP_SYNTAX
projection> strict$[(version)$]>; extensible>; define behavior for ProjectedEntity > extensible> $[...$] { $[...$] $[mapping for PartnerType corresponding extensible>$] $[...$] } ...>
ABAP_PREREQUISITE To allow BDEF projection extensions > to a RAP projection behavior definition >, BDEF strict mode> must be switched on using the keyword strict $[(version)$]>>. ABAP_PREREQ_END
What does it do? The keyword extensible> can be specified at different places to allow for extensions:
extensible> in the RAP behavior definition header> Prerequisite for extensibility. If it is not specified, then extensions are not allowed. If specified, at least one RAP BO entity must be declared as extensible in the entity behavior characteristics >. Allows the following components to be added to a RAP projection behavior definition> via a BDEF projection extension: BEGIN_SECTION VERSION 5 OUT
RAP foreign entity>
Adding a new RAP authorization context for disable> and extending an existing full authorization context> from the extended entity. END_SECTION VERSION 5 OUT
Defining behavior for an extension node on the projection layer by means of a RAP projection extension entity >.
extensible> in the entity behavior characteristics> Mandatory for each individual RAP BO entity> that allows extensions. Allows the following behavior extensions to be added via a BDEF projection extension for the RAP BO entity in question:
RAP field characteristics> can be added to extension fields. BEGIN_SECTION VERSION 5 OUT
RAP actions> including authorization control>, feature control>, and precheck>.
RAP functions> END_SECTION VERSION 5 OUT
Reuse of actions, functions, and associations from the base RAP BO of type managed> or unmanaged>. BEGIN_SECTION VERSION 5 OUT
RAP type mapping> END_SECTION VERSION 5 OUT
extensible> in the entity behavior body>: mapping for PartnerType corresponding extensible>>: a RAP type mapping> defined in the extended RAP business object can be extended with extension fields. extensible> can only be used in combination with corresponding>, so that components with the same name are automatically mapped to each other. ABAP_NOTE It is not required that the underlying projected BDEF> is declared as extensible>. A BDEF projection can be extensible independently of the projected RAP BO. BEGIN_SECTION VERSION 5 OUT
ABAP_EXAMPLE_VX The RAP projection behavior definition for DEMO_RAP_PROJ_EXTEND > enables BDEF extensions: BDEF DEMO_RAP_PROJ_EXTEND ABAP_EXAMPLE_END
ABAP_EXAMPLES_ABEXA
BDEF Projection Extension, Node Extension>
BDEF Projection Extension, Field Extension> ABAP_EXAMPLE_END END_SECTION VERSION 5 OUT