RMSA104_PROTOCOL_ENTRY_ADD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name RMSA104_PROTOCOL_ENTRY_ADD into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
RMSA104
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'RMSA104_PROTOCOL_ENTRY_ADD' "
EXPORTING
* i_msgid = RMSAP_GC_MSGID_PP " symsgid
* i_msgty = RMSAP_GSC_MSG_TYPE-E " symsgty
* i_msgno = RMSAP_GSC_MSG_PP-007 " symsgno
* i_msgv1 = " any
* i_msgv2 = " any
* i_msgv3 = " any
* i_msgv4 = " any
* i_fieldname = RMSAP_GC_FNAM_VALUE01 " lvc_fname
i_row_id = " int4
is_outtab = " ehsbs_api_vai_alvout
io_data_changed = " cl_alv_changed_data_protocol
. " RMSA104_PROTOCOL_ENTRY_ADD
The ABAP code below is a full code listing to execute function module RMSA104_PROTOCOL_ENTRY_ADD including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
DATA(ld_i_msgid) = 'some text here'.
DATA(ld_i_msgty) = 'some text here'.
DATA(ld_i_msgno) = 'Check type of data required'.
DATA(ld_i_msgv1) = 'some text here'.
DATA(ld_i_msgv2) = 'some text here'.
DATA(ld_i_msgv3) = 'some text here'.
DATA(ld_i_msgv4) = 'some text here'.
DATA(ld_i_fieldname) = 'some text here'.
DATA(ld_i_row_id) = 'some text here'.
DATA(ld_is_outtab) = 'some text here'.
DATA(ld_io_data_changed) = 'some text here'. . CALL FUNCTION 'RMSA104_PROTOCOL_ENTRY_ADD' EXPORTING * i_msgid = ld_i_msgid * i_msgty = ld_i_msgty * i_msgno = ld_i_msgno * i_msgv1 = ld_i_msgv1 * i_msgv2 = ld_i_msgv2 * i_msgv3 = ld_i_msgv3 * i_msgv4 = ld_i_msgv4 * i_fieldname = ld_i_fieldname i_row_id = ld_i_row_id is_outtab = ld_is_outtab io_data_changed = ld_io_data_changed . " RMSA104_PROTOCOL_ENTRY_ADD
IF SY-SUBRC EQ 0. "All OK ENDIF.
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_i_msgid | TYPE SYMSGID , |
| ld_i_msgty | TYPE SYMSGTY , |
| ld_i_msgno | TYPE SYMSGNO , |
| ld_i_msgv1 | TYPE ANY , |
| ld_i_msgv2 | TYPE ANY , |
| ld_i_msgv3 | TYPE ANY , |
| ld_i_msgv4 | TYPE ANY , |
| ld_i_fieldname | TYPE LVC_FNAME , |
| ld_i_row_id | TYPE INT4 , |
| ld_is_outtab | TYPE EHSBS_API_VAI_ALVOUT , |
| ld_io_data_changed | TYPE CL_ALV_CHANGED_DATA_PROTOCOL . |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name RMSA104_PROTOCOL_ENTRY_ADD or its description.