Ansicht
Dokumentation

ABENBDL_DEFINE_BEH_EXTEND - BDL DEFINE BEH EXTEND

CPI1466 during Backup   General Data in Customer Master  
This documentation is copyright by SAP AG.

- Extension Entity Behavior Definition

... define behavior for ExtNode ...

As a prerequisite, the extended CDS behavior definition must explicitly allow BDEF extensions as described in topic CDS BDL - Extensibility Enabling for RAP BOs.

Effect

Defines the behavior for an extension node in a BDEF extension using the statement define behavior for. As a prerequisite, the node must be added to the RAP data model via RAP data model extensions. The BDEF extension can add behavior for this extension node.

The behavior for the extension node is defined in the same way as for RAP BOs, see section Entity Behavior Definition, with the following differences:

• No explicit pointing to a RAP authorization master entity.

Use authorization dependent instead of authorization dependent by _Assoc.

• No explicit pointing to a RAP lock master entity.

Use lock dependent instead of lock dependent by _Assoc.

• No explicit pointing to a RAP ETag master entity.

Use etag dependent instead of etag dependent by _Assoc.

As a best practice, SAP recommends to define an ETag master field for each individual entity. As a consequence, the syntax etag dependent should not be used at all.

• Declare ancestor associations, so that the path to the authorization master, lock master, and ETag master entities can be derived.

If an ABAP behavior pool is specified, the rules for extension ABPs apply. See topic CDS BDL - implementation in class unique, Extension.

Note

A short syntax form is available: ( lock, authorization, etag ) dependent. Each of the three components lock, authorization, and etag is optional but at least one of them must be specified within the brackets.

Example

The BDEF extension DEMO_RAP_EXTENSION_1 extends the CDS behavior definition DEMO_RAP_EXTENSIBLE_ROOT. It behavior-enables an extension node using the syntax define behavior for. It defines behavior and multiple ancestor associations. Lock, authorization, and ETag master are not specified explicitly, but derived implicitly.

The executable example Node extension explains the example above in detail.

Fill RESBD Structure from EBP Component Structure   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 4870 Date: 20240511 Time: 130817     sap01-206 ( 56 ms )