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

RAP BDL in ABAP Release 7.57


1. RAP Late Numbering for Managed and for Draft-Enabled RAP BOs

2. Instance-Bound Factory Actions for Managed RAP BOs

3. BDEF Privileged Mode for RAP Projection BOs

4. CDS Interface Behavior Definitions

5. Managed RAP BO, New Field Characteristic

6. Unmanaged RAP BO, New Field Characteristic

7. Managed RAP BO, with full data

8. Variants to Define a RAP Own Authorization Context

9. BDEF Extensions for RAP BOs

10. BDEF Extensions for RAP Projection BOs

11. New Version of BDEF Strict Mode

12. Draft Query Views for Draft-Enabled RAP BOs

13. Abstract BDEF, New Field Characteristic

14. result selective for Deep Result Types

15. RAP Business Events

16. RAP Save Actions with Phase Specification

17. Repeatable RAP Actions and Functions



Modification 1  

RAP Late Numbering for Managed and for Draft-Enabled RAP BOs

RAP late numbering is now also available for managed RAP BOs, managed draft-enabled RAP BOs, and for unmanaged draft-enabled RAP BOs.



Modification 2  

Instance-Bound Factory Actions for Managed RAP BOs

Instance-bound factory actions are now also available for managed RAP BOs.



Modification 3  

BDEF Privileged Mode for RAP Projection BOs

A new syntax variant of with privileged mode is now available for RAP projection BOs.



Modification 4  

CDS Interface Behavior Definitions

A new implementation type is available: the RAP interface behavior definition. Such interface BDEFs are based on CDS transactional interfaces and define the behavior of a RAP BO interface. The overall purpose of a RAP BO interface is to project a business object for stable consumption.



Modification 5  

Managed RAP BO, New Field Characteristic

In managed RAP business objects, a new field characteristic is available: field(suppress). It removes the field in question from the BDEF derived types and from all RAP APIs.



Modification 6  

Unmanaged RAP BO, New Field Characteristic

In unmanaged RAP business objects, a new field characteristic is available: field(suppress). It removes the field in question from the BDEF derived types and from all RAP APIs.



Modification 7  

Managed RAP BO, with full data

In managed RAP business objects, the optional addition with full data can be used in combination with one of the RAP saving options to ensure that full instance data is handed over to the save_modified method of the RAP saver class in the ABAP behavior pool.



Modification 8  

Variants to Define a RAP Own Authorization Context

New variants are available for defining a RAP own authorization context:





Modification 9  

BDEF Extensions for RAP BOs

BDEF extensions for RAP BOs can be defined using the statement extension.



Modification 10  

BDEF Extensions for RAP Projection BOs

BDEF projection extensions for RAP projection business objects can be defined using the statement extension for projection.



Modification 11  

New Version of BDEF Strict Mode

A new version of BDEF strict mode is available: Strict mode version 2, specified using strict(2). It applies even more syntax checks than the first version.



Modification 12  

Draft Query Views for Draft-Enabled RAP BOs

The new syntax addition query is available to define a draft query view for a draft-enabled RAP BO. This addition is optional. Only in the context of RAP extensibility is it a mandatory prerequisite for the C0 release of the CDS behavior definition in question.



Modification 13  

Abstract BDEF, New Field Characteristic

In RAP abstract behavior definitions, a new RAP field characteristic is available: mandatory:execute. It declares the field in question as mandatory. Whenever the hierarchical type is used as input parameter for a RAP action or a RAP function, a value must be supplied.



Modification 14  

result selective for Deep Result Types

The addition result selective is now also possible for deep result types. It can be specified for an output parameter of a RAP action or RAP function to return only parts of the result structure.



Modification 15  

RAP Business Events

Using RAP business events, the ABAP RESTful Application Programming Model now offers native support for event-driven architecture. RAP business events are defined with the language element event. A flat or deep output parameter can optionally be specified.



Modification 16  

RAP Save Actions with Phase Specification

RAP save actions can now specify one or both of the RAP saver methods finalize or adjustnumbers in brackets to indicate the RAP saver method during which the action can be executed.



Modification 17  

Repeatable RAP Actions and Functions

RAP actions and RAP functions can be defined as repeatable. This syntax addition explicitly allows multiple executions of the same action or function on the same RAP BO entity instance within the same ABAP EML or OData request. The BDEF derived type of a repeatable action or function has an extra %cid component, in contrast to the BDEF derived type of non-repeatable actions or function.