Ansicht
Dokumentation

ABENBDL_STRUCTURE - BDL STRUCTURE

General Material Data   CPI1466 during Backup  
This documentation is copyright by SAP AG.

- Structure

* Work in progress *

A behavior definition consists of a header part and a sequence of entity behavior definitions. An entity behavior definition consists of a section containing properties of the entity plus operations enclosed in curly brackets {}.

The following depicts the syntax structure of a behavior definition that itself defines the transactional behavior of CDS_Entity_name.

/* Header part of the behavior definition */
implementation unmanaged $| managed $| abstract
       $[in class class_name unique$];

/* Entity behavior definition */
define behavior for CDS_Entity_name $[alias AliasName$]

/* Entity properties */
$[implementation in class ClassName unique$]
$[late numbering $[in place$]$]
$[etag field $| AncestorEntity~Field ( LocalField = MasterField )$]
$[lock master $| dependent ( LocalField = MasterField )$]

/* Curly bracket */
{

/* Access restrictions */
field (read only | mandatory) field$[, field, ...$];

/* Standard Operations*/
$[internal$] create;
$[internal$] update;
$[internal$] delete;

/* Actions */
$[internal$] $[static$] action ActionName
       $[external LongName$]
       $[parameter InputParameterEntity|$self$]
       $[result cardinality OutputParameterEntity|$self$];

/* Association */
$[internal$] association AssociationName
       $[abbreviation AbbreviationName$] {$[$[internal;$]create;$]};

/* Curly bracket */
}

Rules

• Not every entity property ( late numbering, etag, or lock) from the composition tree is a mandatory property.

• A property can occur a maximum of once in a behavior definition.

• If an entity does not occur in the behavior definition, the entity does not have a transactional character (it is read-only).

ROGBILLS - Synchronize billing plans   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3696 Date: 20240419 Time: 052743     sap01-206 ( 32 ms )