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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN Variants to Define a RAP Own Authorization Context
New variants are available for defining a RAP own authorization context:
define own authorization context by privileged mode;
define own authorization context by privileged mode and { ... }
ABAP_MODIFICATION_NN BDEF Extensions for RAP BOs
BDEF extensions for RAP BOs can be defined using the statement extension.
ABAP_MODIFICATION_NN BDEF Extensions for RAP Projection BOs
BDEF projection extensions for RAP projection business objects can be defined using the statement extension for projection.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN 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.
