ABAP - Keyword Documentation →  ABAP - ABAP Release News →  News for ABAP Release 7.5x →  News for ABAP Release 7.58 →  ABAP RESTful Application Programming Model in ABAP Release 7.58 → 
Mail Feedback

RAP BDL in ABAP Release 7.58


1. Interface BDEF, New Field Characteristics

2. Interface BDEF, use event

3. Managed and Unmanaged RAP BO, New Field Characteristic

4. Static Default Factory Actions

5. RAP Derived Events

6. RAP Side Effects

7. Draft Action Activate Optimized

8. Authorization Control on Action Level

9. with managed instance filter

10. Abstract BDEF Extensions

11. Abstract BDEF, mandatory:execute for Associations

12. Redefined Parameters, Projection or Interface BDEF

13. Draft Action AdditionalSave

14. BOPF-Based RAP Business Objects



Modification 1  

Interface BDEF, New Field Characteristics

In RAP interface behavior definitions, the following RAP field characteristics are now available:





Modification 2  

Interface BDEF, use event

In RAP interface behavior definitions, RAP business events can be reused using the syntax use event.



Modification 3  

Managed and Unmanaged RAP BO, New Field Characteristic

A new RAP field characteristic is available for managed and unmanaged RAP BOs: notrigger[:warn]. Fields with this attribute must not be used in a trigger condition of a RAP validation or a RAP determination.



Modification 4  

Static Default Factory Actions

The syntax addition default is available for static factory actions in managed, unmanaged, and projection BDEFs. Exactly one static factory action per RAP BO entity can be defined as default static factory action. The addition default is evaluated by consuming frameworks, such as OData.



Modification 5  

RAP Derived Events

RAP derived events allow the reuse of existing RAP business events with a custom payload. RAP derived events are available in managed and unmanaged RAP BOs and in base BDEF extensions. They are defined using the syntax managed event.



Modification 6  

RAP Side Effects

RAP side effects define interdependencies among RAP BO properties that trigger a reload of the affected properties on the user interface. Side effects are translated into annotations in the OData metadata of a RAP service. The syntax for defining RAP side effects is side effects.



Modification 7  

Draft Action Activate Optimized

The optional addition optimized is now available for the draft action Activate. SAP recommends always using this addition, since it speeds up the activation of draft instances.



Modification 8  

Authorization Control on Action Level

Two new RAP BO operation additions are available for actions and determine actions:

Both of these additions are specified on the action level and they replace the authorization control that is specified in the authorization master entity.

In managed, unmanaged, and projection BDEFs, these additions are optional. In base BDEF extensions, authorization control on the action level is mandatory.



Modification 9  

with managed instance filter

The optional addition with managed instance filter is available for projection BDEFs and interface BDEFs. If specified, the WHERE condition of the underlying CDS transactional query or CDS transactional interface is evaluated when the BDEF is accessed with ABAP EML or OData requests from Web clients.



Modification 10  

Abstract BDEF Extensions

The new statement extension for abstract of the RAP BDL makes it possible to add abstract BDEF extensions to abstract behavior definitions. Abstract BDEFs are mainly used as parameters for RAP actions, RAP functions, and RAP business events. An abstract BDEF extension allows you to extend these parameters.



Modification 11  

Abstract BDEF, mandatory:execute for Associations

The optional addition mandatory:execute is now available for associations in abstract BDEFs. It declares the association in question as mandatory, that is, whenever the abstract BDEF is used as an input parameter for a RAP action or a RAP function, the %control flag must be set for this association.



Modification 12  

Redefined Parameters, Projection or Interface BDEF

The input or output parameter of a RAP action, RAP function, or a RAP business event that is reused in a projection BDEF or an interface BDEF can optionally be replaced with a dedicated projection-specific structure using the syntax additions deep parameter or deep result.



Modification 13  

Draft Action AdditionalSave

A new draft action is available, draft action AdditionalSave. This draft action allows users to define a custom saving strategy for draft instances. It is intended in particular for draft actions with a user-defined implementation, defined using the addition with additional implementation.



Modification 14  

BOPF-Based RAP Business Objects

A migration tool has been released to migrate CDS-based BOPF business objects to BOPF-based RAP business objects. For details on BOPF-based RAP business objects, see the topic RAP - BOPF-Based RAP Business Objects.