Ansicht
Dokumentation

ABENBDL_EXTENSION_SYNTAX - BDL EXTENSION SYNTAX

TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

- extension

extension $[using interface InterfaceBdef$]$[;$]
  $[extension_header$]
  $[foreign entity$]
  $[entity_behavior_extension$]
  $[extension_entity_behavior$]
  $[extend own authorization context$]
  $[define authorization context$]
...

Effect

Extends an existing CDS behavior definition of type managed or unmanaged using a BDEF extension in the CDS BDL. An existing CDS behavior definition can have one or multiple BDEF extensions. The number of extensions is not limited. A BDEF extension itself cannot be further extended.

Naming: BDEF extensions themselves and each single extension element should use a separate namespace to avoid naming conflicts with the original BDEF and its elements. BDEF extensions created in non-SAP and non-partner development systems should use the customer namespace prefix Z or ZZ.

A BDEF extension can have the following components:

• using interface: It is strongly recommended and in certain scenarios even mandatory to extend a RAP BO via an interface layer. For details, see topic CDS BDL using interface, Extension.

• extension_header: Mandatory component of a BDEF extension. Similar to the CDS behavior definition header but offers fewer options.

The semicolon after the keyword extension is either mandatory or not allowed, depending on the components of the extension_header. See examples.

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

• entity_behavior_extension: behavior extension of an existing RAP BO entity.

• extension_entity_behavior: defines the behavior for an extension node.

• extend own authorization context: if the extended BO defines a full authorization context, this context can be extended. If the extended BO does not define a full authorization context, it must not be added via an extension.

• define authorization context: a new authorization context can be defined in a BDEF extension. The syntax is similar to the syntax for RAP BOs with the following difference: The addition for disable is not supported. For details, see topic CDS BDL - define authorization context.

Example

The following source code shows BDEF extension DEMO_RAP_EXTENSION_1. It extends BDEF DEMO_RAP_EXTENSIBLE_ROOT. The extension contains the following components:

• BDEF extension header

• Entity behavior extension

• Authorization context

• Extension entity behavior

ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6824 Date: 20240511 Time: 090453     sap01-206 ( 68 ms )