What does it do? 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. 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: RAP BDL - projection behavior definitions.
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
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.
Latest notes: 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. NON_V5_HINTS ABAP_HINT_END
ABAP_EXAMPLE_VX5 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 RAP behavior definition header. ABAP_NOTE This example does not fully meet the requirements of the RAP BO contract. It is intentionally kept short and simple and serves demonstration purposes only. See more information on the RAP BO contract in the Development guide for the ABAP RESTful Application Programming Model. BDEF DEMO_SALES_CDS_BUPA_2 ABAP_EXAMPLE_END
