SAP RAP_MESSAGE_SAVER Function Module for RESTful ABAP Programming Model: Message Save
RAP_MESSAGE_SAVER is a standard rap message saver SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RESTful ABAP Programming Model: Message Save processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for rap message saver FM, simply by entering the name RAP_MESSAGE_SAVER into the relevant SAP transaction such as SE37 or SE38.
Function Group: RAP_SERVICES_MESSAGES
Program Name: SAPLRAP_SERVICES_MESSAGES
Main Program: SAPLRAP_SERVICES_MESSAGES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function RAP_MESSAGE_SAVER pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'RAP_MESSAGE_SAVER'"RESTful ABAP Programming Model: Message Save.
EXPORTING
IT_INSERT_MESSAGES = "
IT_DELETE_MESSAGES = "
IT_DISCARDED_MESSAGES = "
IMPORTING Parameters details for RAP_MESSAGE_SAVER
IT_INSERT_MESSAGES -
Data type: RAP_MESSAGES_TABOptional: No
Call by Reference: No ( called with pass by value option)
IT_DELETE_MESSAGES -
Data type: RAP_MESSAGES_DELETE_TABOptional: No
Call by Reference: No ( called with pass by value option)
IT_DISCARDED_MESSAGES -
Data type: RAP_MESSAGES_DISCARD_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RAP_MESSAGE_SAVER Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_it_insert_messages | TYPE RAP_MESSAGES_TAB, " | |||
| lv_it_delete_messages | TYPE RAP_MESSAGES_DELETE_TAB, " | |||
| lv_it_discarded_messages | TYPE RAP_MESSAGES_DISCARD_TAB. " |
|   CALL FUNCTION 'RAP_MESSAGE_SAVER' "RESTful ABAP Programming Model: Message Save |
| EXPORTING | ||
| IT_INSERT_MESSAGES | = lv_it_insert_messages | |
| IT_DELETE_MESSAGES | = lv_it_delete_messages | |
| IT_DISCARDED_MESSAGES | = lv_it_discarded_messages | |
| . " RAP_MESSAGE_SAVER | ||
ABAP code using 7.40 inline data declarations to call FM RAP_MESSAGE_SAVER
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects