Ansicht
Dokumentation
ABENBDL_EXTENSION_FOR_PROJECTION - BDL EXTENSION FOR PROJECTION
General Material Data Vendor Master (General Section)This documentation is copyright by SAP AG.
- extension for projection
extension for projection $[implementation in class ClassName unique$];
$[with privileged mode disabling base context $[and ContextName$]$];
$[foreign entity$]
$[define behavior for$]
$[extend behavior for$]
$[extend own authorization context$]
$[define authorization context$]
...
Effect
Extends an existing CDS projection behavior definition using a BDEF projection extension in the CDS BDL. A CDS projection behavior definition can have one or multiple BDEF projection extensions. The number of extensions is not limited. A BDEF projection extension itself cannot be further extended.
A BDEF projection extension can have the following components:
- implementation in class ClassName unique: in a BDEF projection extension, an ABAP behavior pool is possible:
- Functionality that is reused from the original BO does not require its own implementation. The implementation from the original BO is reused.
- If the BDEF projection extension defines new actions or functions, an ABAP behavior pool is required.
- The rules for extension ABPs apply, see topic implementation in class unique, extension.
- with privileged mode disabling base context $[and ContextName$]:
- A BDEF projection extension can enable BDEF privileged mode. As a prerequisite, the original BO of type managed or unmanaged must enable privileged mode. The behavior of the extended BDEF of type projection is irrelevant, it may define privileged mode, but this is optional.
- The syntax addition disabling base context is mandatory, and ContextName is optional. The same rules apply as for projection behavior definitions, see topic with privileged mode, Alternative 2.
- foreign entity:
- Defines a RAP BO entity which is not part of the CDS composition tree of the current RAP BO as part of the response structures.
- A foreign entity can be defined before, after, or between the other components.
- Only entities that belong to the same software component can be added as RAP foreign entity to a BDEF projection extension.
- define behavior for: Defines a RAP projection extension entity using the statement define behavior for.
- extend behavior for: A RAP entity projection extension extends the behavior of an existing entity of a projection BDEF.
- extend own authorization context: if the projected BDEF of implementation type projection defines a full authorization context, this context can be extended. If the projected BDEF does not define a full authorization context, it must not be added newly via an extension.
- define authorization context: a new
authorization
context can be defined in a BDEF projection extension. For details, see topic CDS
BDL - define authorization context.
: No ABAP behavior pool must be specified. The statement implementation in class ClassName unique is forbidden.
Example
The BDEF projection extension DEMO_RAP_PROJ_EXT_BEH_1 extends the CDS projection behavior definition DEMO_RAP_PROJ_EXT_BEH.
- It extends the behavior of the root node.
- It behavior-enables an extension node using the syntax define behavior for, reusing operations from the projected BDEF and specifying field attributes.
The executable example Projection Entity Extension explains the example above in detail.
Vendor Master (General Section) Fill RESBD Structure from EBP Component Structure
This documentation is copyright by SAP AG.
Length: 8338 Date: 20240511 Time: 090928 sap01-206 ( 74 ms )
