RS_MSG_TEXT SAP Function module

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

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

Pattern for FM RS_MSG_TEXT - RS MSG TEXT

CALL FUNCTION 'RS_MSG_TEXT' "
  EXPORTING
*   text_type = 'S'             " c
    msgid =                     " sy-msgid      Message ID
    msgno =                     " sy-msgno      Message Number
*   msgv1 = SPACE               " sy-msgv1
*   msgv2 = SPACE               " sy-msgv2
*   msgv3 = SPACE               " sy-msgv3
*   msgv4 = SPACE               " sy-msgv4
*   dialog = ABAP_TRUE          " abap_bool
  TABLES
    msgtext =                   " abapsource
  EXCEPTIONS
    MESSAGE_NOT_EXISTS = 1      "
    .  "  RS_MSG_TEXT

ABAP code example for Function Module RS_MSG_TEXT

The ABAP code below is a full code listing to execute function module RS_MSG_TEXT 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_msgtext  
 
 TYPE STANDARD TABLE OF ABAPSOURCE,"TABLES PARAM
wa_msgtext
 
 LIKE LINE OF it_msgtext
.


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

DATA(ld_msgid) = 'some text here'.

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

DATA(ld_msgv1) = 'some text here'.

DATA(ld_msgv2) = 'some text here'.

DATA(ld_msgv3) = 'some text here'.

DATA(ld_msgv4) = 'some text here'.

DATA(ld_dialog) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_msgtext to it_msgtext.
.

CALL FUNCTION 'RS_MSG_TEXT'
  EXPORTING
*   text_type =                  ld_text_type
    msgid =                      ld_msgid
    msgno =                      ld_msgno
*   msgv1 =                      ld_msgv1
*   msgv2 =                      ld_msgv2
*   msgv3 =                      ld_msgv3
*   msgv4 =                      ld_msgv4
*   dialog =                     ld_dialog
  TABLES
    msgtext =                    it_msgtext
  EXCEPTIONS
    MESSAGE_NOT_EXISTS =         1
    .  "  RS_MSG_TEXT

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_text_type
 
 TYPE C ,
it_msgtext
 
 TYPE STANDARD TABLE OF ABAPSOURCE ,
wa_msgtext
 
 LIKE LINE OF it_msgtext,
ld_msgid
 
 TYPE SY-MSGID ,
ld_msgno
 
 TYPE SY-MSGNO ,
ld_msgv1
 
 TYPE SY-MSGV1 ,
ld_msgv2
 
 TYPE SY-MSGV2 ,
ld_msgv3
 
 TYPE SY-MSGV3 ,
ld_msgv4
 
 TYPE SY-MSGV4 ,
ld_dialog
 
 TYPE ABAP_BOOL .


ld_text_type = 'some text here'. 

"populate fields of struture and append to itab
append wa_msgtext to it_msgtext.
ld_msgid = 'some text here'.
ld_msgno = 'Check type of data required'.
ld_msgv1 = 'some text here'.
ld_msgv2 = 'some text here'.
ld_msgv3 = 'some text here'.
ld_msgv4 = 'some text here'.
ld_dialog = 'some text here'.