Ansicht
Dokumentation

ABENBDL_IMPL_TYPE - BDL IMPL TYPE

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

- Implementation Type

${ $[implementation$] managed
                 $| unmanaged
                 $| abstract
                 $| projection $}
                 $| interface ...

Effect

CDS BDL offers the following statements for different implementation types:

• managed

The transactional buffer and the standard BO operations are handled by the managed RAP BO provider.

Recommended for development scenarios in which all essential parts are developed from scratch, without a large amount of existing code (also known as "greenfield" development) with standard implementation.

See also: managed RAP business object

• unmanaged

The transactional buffer and the standard BO operations must be implemented in the ABAP behavior pool.

Recommended for development scenarios in which business logic already exists and is intended to be reused (also known as "brownfield" development).

See also: unmanaged RAP business object

• projection

A RAP projection behavior definition is based on a managed or unmanaged RAP BO and represents a direct projection of its base behavior definition. It exposes a subset of the base behavior definition's operations and characteristics. In a business application, a projection BDEF provides the means to define service-specific behavior for a BO projection.

See also: CDS BDL - projection behavior definitions.

• abstract

A CDS abstract behavior definition mainly serves as typing mechanism for deep action or function parameters. Only a limited range of syntax elements is available, such as associations and type mapping. It is not possible to define any transactional behavior in an abstract behavior definition.

See also: CDS abstract behavior definition

• interface

Defines the behavior of a RAP BO interface, which serves as interface for stable consumption and is typically released as released API.

See also: CDS Interface Behavior Definition.

Note

The syntax implementation ${managed$|unmanaged$|projection$|abstract$} is obsolete and should not be used. The short syntax form that specifies only the implementation type, without the keyword implementation, should be used instead. If BDEF strict mode is enabled, this syntax must not be used and produces a syntax error.

Example

The following example shows a managed BDEF based on the CDS root view entity DEMO_SALES_CDS_BUPA_2. The implementation type managed is specified in the CDS behavior definition header.

Addresses (Business Address Services)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 5893 Date: 20240424 Time: 054240     sap01-206 ( 69 ms )