Get Example source ABAP code based on a different SAP table
• FIELD ABAP_BDL_PROJ_EXT • READONLY ABAP_BDL_PROJ_EXT , FIELD • USE ABAP_BDL_PROJ_EXT • USE ASSOCIATION ABAP_BDL_PROJ_EXT , USE • READONLY UPDATE ABAP_BDL_PROJ_EXT , FIELD • SUPPRESS ABAP_BDL_PROJ_EXT , FIELD • CREATE ABAP_BDL_PROJ_EXT , USE ASSOCIATION • WITH DRAFT ABAP_BDL_PROJ_EXT , USE ASSOCIATION • USE ACTION ABAP_BDL_PROJ_EXT , USE • USE FUNCTION ABAP_BDL_PROJ_EXT , USE • STATIC ABAP_BDL_PROJ_EXT • FACTORY ABAP_BDL_PROJ_EXT • ACTION ABAP_BDL_PROJ_EXT • FUNCTION ABAP_BDL_PROJ_EXT • EXTEND MAPPING FOR ABAP_BDL_PROJ_EXT • MAPPING FOR ABAP_BDL_PROJ_EXT • CORRESPONDING ABAP_BDL_PROJ_EXT • CONTROL ABAP_BDL_PROJ_EXT • EXCEPT ABAP_BDL_PROJ_EXT • PARAMETER ABAP_BDL_PROJ_EXT , MAPPING FOR
ABAP_RAP - extension_body, Projection Extension
ABAP_SYNTAX ... $[field characteristics$]; $[use$]; BEGIN_SECTION VERSION 5 OUT $[actions and functions$]; $[mapping for$]; END_SECTION VERSION 5 OUT $[extend mapping for$];
What does it do? Defines the behavior extension body to extend an existing RAP BO entity in a RAP projection behavior definition. Components:
field characteristics:
Adds field attributes to extension fields in a BDEF projection extension.
Field attributes can be added only for extension fields. Extension fields are fields which are added via RAP data model extension.
The following field attributes are available in BDEF projection extensions for extension fields: readonly, suppress, readonly:update .
These field attributes work as described in topic Field Characteristics, Projection BDEF.
ABAP_NOTE The field characteristics mandatory, modify, and features:instance are not available in BDEF projection extensions.
use:
The keyword use allows the reuse of RAP BO operations.
The following operations can be reused: RAP actions, RAP functions, and associations.
ABAP_LIMITATION The operation augmentation is not available in BDEF projection extensions. As a consequence, the following is not supported: use association _child {create(augment);}.
Only extension operations that were created in the same software component can be reused. Operations from the original base BDEF of type managed or unmanaged must not be reused.
Actions, functions, and associations from the projection layer cannot be reused.
Reuse works as described in topic RAP BDL - use. BEGIN_SECTION VERSION 5 OUT
Actions and functions:
New RAP actions and RAP functions can be defined and implemented in a BDEF projection extension.
The syntax is exactly the same as for actions and functions in projection BDEFs, see topic TITLE with one difference: The optional addition default to define a factory action as default factory action is not available in BDEF projection extensions.
An implementation in an extension ABP is required. The rules for extension ABPs apply, see topic TITLE .
mapping for:
RAP type mapping can be added. This type mapping can only contain extension fields. It must not contain any fields from the original BDEF. The syntax is exactly the same as for RAP BOs, see topic TITLE . END_SECTION VERSION 5 OUT
extend mapping for:
An existing RAP type mapping can be extended with extension fields using the syntax extend mapping for as described in topic RAP BDL - extend mapping.
ABAP_EXAMPLES_ABEXA
BDEF Projection Extension, Node Extension
BDEF Projection Extension, Field Extension ABAP_EXAMPLE_END
