SAP RMSA461_WRITE Function Module for NOTRANSL: Puffer: In Puffer schreiben
RMSA461_WRITE is a standard rmsa461 write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Puffer: In Puffer schreiben 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 rmsa461 write FM, simply by entering the name RMSA461_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMSA461
Program Name: SAPLRMSA461
Main Program: SAPLRMSA461
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RMSA461_WRITE 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 'RMSA461_WRITE'"NOTRANSL: Puffer: In Puffer schreiben.
IMPORTING
E_FLG_CHACOLL = "Change Number Collision
TABLES
* XT_TAB_IOT_WRI = "
* XT_TAB_IOT_DEL = "
EXPORTING Parameters details for RMSA461_WRITE
E_FLG_CHACOLL - Change Number Collision
Data type: RCGRHBUF-VALFLGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RMSA461_WRITE
XT_TAB_IOT_WRI -
Data type: RMSAS_QMHDR_IOTOptional: Yes
Call by Reference: Yes
XT_TAB_IOT_DEL -
Data type: RMSAS_QMHDR_IOTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RMSA461_WRITE 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_e_flg_chacoll | TYPE RCGRHBUF-VALFLG, " | |||
| lt_xt_tab_iot_wri | TYPE STANDARD TABLE OF RMSAS_QMHDR_IOT, " | |||
| lt_xt_tab_iot_del | TYPE STANDARD TABLE OF RMSAS_QMHDR_IOT. " |
|   CALL FUNCTION 'RMSA461_WRITE' "NOTRANSL: Puffer: In Puffer schreiben |
| IMPORTING | ||
| E_FLG_CHACOLL | = lv_e_flg_chacoll | |
| TABLES | ||
| XT_TAB_IOT_WRI | = lt_xt_tab_iot_wri | |
| XT_TAB_IOT_DEL | = lt_xt_tab_iot_del | |
| . " RMSA461_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM RMSA461_WRITE
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.| "SELECT single VALFLG FROM RCGRHBUF INTO @DATA(ld_e_flg_chacoll). | ||||
Search for further information about these or an SAP related objects