Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  ABAP RESTful Programming Model →  Behavior Definitions 

ABAP BDL - Example

Other versions: 7.31 | 7.40 | 7.54


In the following example, the data from the ABAP flight data reference scenario (or flight data scenario for short) is used. It represents a legacy business logic that can be used to create and edit flight bookings.

The underlying business object for managing flight trips can be given an alias, in this instance, Travel. The structure of the business object consists of a tree with the entities Travel, Booking, Agency, Customer, Carrier, Connection, Currency, and Status. The entities are joined by compositions and associations. Each entity of the tree structure is modeled as a CDS view:

  • The entity Travel is the top node in the business object structure and is used to manage general travel data. It is represented by the CDS view /DMO/I_Travel.
  • The entity Booking is a child entity of Travel and is represented by the CDS view /DMO/I_Booking. It is used to manage flight booking data, for example, the passenger, connection, price, and flight date.
  • The CDS views that represent entities other than those in this example are described in Other entity examples.

The following example shows the behavior definition for the root entity Travel. In the example, the implementation type is set to unmanaged because the existing legacy business logic needs to be integrated into the new application for managing flight trips.

implementation unmanaged;
define behavior for /DMO/I_Travel alias travel
late numbering
lock master
etag LastChangedAt
  field (read only) Travel_ID;
  field (mandatory) Agency_ID, Customer_ID, Begin_Date, End_Date;
  action set_status_booked result [1] $self;
  association _Booking { create; }

The transactional behavior of the business object travel is defined by the standard operations create, update, and delete as well as the action set_status_booked. These operations are implemented in the association behavior pool.

The end user can use the action set_status_booked to set the status of a trip to booked. The action set_status_booked is bound to an instance of the type travel, which in this case is also returned by the action. This means the cardinality equals [1] and $self is set as the type of the output parameter.

The association _Booking specifies that new instances of the child entity Booking can be created for a specific instance of the entity Travel only.


Root entities example

Child entity example

Other entity examples