RSSM_RSMONMESS_WRITE SAP Function module - Change RSMONMESS

RSSM_RSMONMESS_WRITE 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 RSSM_RSMONMESS_WRITE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: RSSM_LOAD
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM RSSM_RSMONMESS_WRITE - RSSM RSMONMESS WRITE

CALL FUNCTION 'RSSM_RSMONMESS_WRITE' "Change RSMONMESS
  EXPORTING
    i_method =                  " rs_bool       Boolean
*   i_all =                     " rs_bool       Boolean
*   i_t_fields =                " rssm1_t_field
*   i_with_dbcommit =           " rs_bool       Boolean
*   i_second_connection = SPACE  " dbcon_name   Character Field Length = 10
  TABLES
    i_t_rsmonmess =             " rsmonmess     Monitor: Selections for executed request
  EXCEPTIONS
    ARCHIVED = 1                "
    .  "  RSSM_RSMONMESS_WRITE

ABAP code example for Function Module RSSM_RSMONMESS_WRITE

The ABAP code below is a full code listing to execute function module RSSM_RSMONMESS_WRITE 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:
it_i_t_rsmonmess  
 
 TYPE STANDARD TABLE OF RSMONMESS,"TABLES PARAM
wa_i_t_rsmonmess
 
 LIKE LINE OF it_i_t_rsmonmess
.


DATA(ld_i_method) = 'Check type of data required'.

DATA(ld_i_all) = 'Check type of data required'.

DATA(ld_i_t_fields) = 'Check type of data required'.

DATA(ld_i_with_dbcommit) = 'Check type of data required'.

DATA(ld_i_second_connection) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_i_t_rsmonmess to it_i_t_rsmonmess.
.

CALL FUNCTION 'RSSM_RSMONMESS_WRITE'
  EXPORTING
    i_method =                   ld_i_method
*   i_all =                      ld_i_all
*   i_t_fields =                 ld_i_t_fields
*   i_with_dbcommit =            ld_i_with_dbcommit
*   i_second_connection =        ld_i_second_connection
  TABLES
    i_t_rsmonmess =              it_i_t_rsmonmess
  EXCEPTIONS
    ARCHIVED =                   1
    .  "  RSSM_RSMONMESS_WRITE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

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_method
 
 TYPE RS_BOOL ,
it_i_t_rsmonmess
 
 TYPE STANDARD TABLE OF RSMONMESS ,
wa_i_t_rsmonmess
 
 LIKE LINE OF it_i_t_rsmonmess,
ld_i_all
 
 TYPE RS_BOOL ,
ld_i_t_fields
 
 TYPE RSSM1_T_FIELD ,
ld_i_with_dbcommit
 
 TYPE RS_BOOL ,
ld_i_second_connection
 
 TYPE DBCON_NAME .


ld_i_method = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_i_t_rsmonmess to it_i_t_rsmonmess.
ld_i_all = 'Check type of data required'.
ld_i_t_fields = 'Check type of data required'.
ld_i_with_dbcommit = 'Check type of data required'.
ld_i_second_connection = 'Check type of data required'.