Warning: file_get_contents(/customers/9/5/e/s4hd.com/httpd.www/global/php/adxcode.txt): Failed to open stream: No such file or directory in /customers/9/5/e/s4hd.com/httpd.www/global/php/helpers.php on line 89
Get Example source ABAP code based on a different SAP table
Warning: Undefined variable $prev in /customers/9/5/e/s4hd.com/httpd.www/sap/help/index.php on line 55
• ACTION ABAP_BDL_BODY • STATIC ABAP_BDL_BODY • DEFAULT ABAP_BDL_BODY • EXTERNAL ABAP_BDL_BODY , action • LOCK NONE ABAP_BDL_BODY
What does it do? RAP actions are non-standard RAP BO operations that modify the state of an entity instance. The custom logic must be implemented in the RAP handler method FOR MODIFY. The following kinds of actions are available:
non-factory actions
Non-factory actions implement custom logic that changes existing entity instances.
Instance-bound non-factory actions can be declared as repeatable. A repeatable action can be executed multiple times on the same RAP BO entity instance in the same ABAP EML or OData request.
factory actions
Factory actions can be used to create RAP BO entity instances.
A default factory action is a special kind of factory action.
save actions
RAP save actions can be non-factory actions or factory actions. RAP save actions are characterized by the syntax addition save, which has the effect that the action in question can only be executed during the RAP save sequence. Any attempt to execute a RAP save action during the RAP interaction phase results in a short dump .
ABAP_FURTHER_INFO Development guide for the ABAP RESTful Application Programming Model, section about Actions.
