RAP - BDL for Behavior Definitions

RAP behavior definitions are created using the behavior definition language RAP BDL in BDL source code.

The general syntax rules for the RAP BDL are described in the topic RAP BDL - General Syntax Rules.

A list of all available BDL language elements can be found in topic RAP BDL - Feature Tables.

RAP 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. In a managed RAP BO, a ready-to-run business object can work without ABAP behavior pool.
As soon as non-standard operations, validations, determinations, or other implementation-relevant syntax elements are added, an ABAP behavior pool is necessary.
Recommended for development scenarios in which all essential parts are developed from scratch, without a large amount of existing code (so-called greenfield development) with standard implementation.
See also: managed RAP business object
unmanaged
The transactional buffer and the standard BO operations must be implemented in an ABAP behavior pool.
Recommended for development scenarios in which business logic already exists and is intended to be reused (so-called brownfield development).
See also: unmanaged RAP business object
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: RAP interface behavior definition.
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 means to define service-specific behavior for a BO projection.
See also: RAP projection behavior definition
abstract
A RAP 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: RAP abstract behavior definition

Managed and unmanaged RAP BOs share a common set of keywords. These keywords are listed in section RAP BDL - managed and unmanaged behavior definitions.

RAP projection behavior definitions reuse elements of the underlying base BDEF. Section RAP BDL - RAP projection behavior definitions explains which elements, such as characteristics and operations, can be reused under which conditions and which characteristics and operations can be newly added to RAP projection behavior definitions.

RAP abstract behavior definitions offer only a limited range of behavior definition elements, such as associations and type mapping. It is not possible to define any transactional behavior in an abstract behavior definition. Section RAP BDL - RAP abstract behavior definitions explains which elements are available in abstract BDEFs.

RAP BOs can be extended using BDEF extensions. The rules for BDEF extensions are described in the topic RAP - BDEF Extension.

ABAP Keyword Documentation

RAP - BDL for Behavior Definitions

Continue