RPY_MESSAGE_READ SAP Function module

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

Associated Function Group: SIFP
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RPY_MESSAGE_READ - RPY MESSAGE READ

CALL FUNCTION 'RPY_MESSAGE_READ' "
  EXPORTING
*   language = SY-LANGU         " sy-langu
    message_id =                " rglif-message_id  Message Class
    message_nr =                " t100-msgnr
*   with_docu = ' '             " rglif-with_docu
  IMPORTING
    message_text =              " t100
  TABLES
    docu_tab =                  " rpy_objtab
    docu_tech =                 " tline
  EXCEPTIONS
    CANCELLED = 1               "
    NOT_FOUND = 2               "
    PERMISSION_ERROR = 3        "
    .  "  RPY_MESSAGE_READ

ABAP code example for Function Module RPY_MESSAGE_READ

The ABAP code below is a full code listing to execute function module RPY_MESSAGE_READ 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_message_text  
 
 TYPE T100
,
it_docu_tab  
 
 TYPE STANDARD TABLE OF RPY_OBJTAB,"TABLES PARAM
wa_docu_tab
 
 LIKE LINE OF it_docu_tab
,
it_docu_tech  
 
 TYPE STANDARD TABLE OF TLINE,"TABLES PARAM
wa_docu_tech
 
 LIKE LINE OF it_docu_tech
.


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


DATA(ld_message_id) = some text here
 

SELECT single MSGNR 
  FROM T100 
  INTO @DATA(ld_message_nr).



DATA(ld_with_docu) = some text here
 

"populate fields of struture and append to itab
append wa_docu_tab to it_docu_tab.
 

"populate fields of struture and append to itab
append wa_docu_tech to it_docu_tech.
.

CALL FUNCTION 'RPY_MESSAGE_READ'
  EXPORTING
*   language =                   ld_language
    message_id =                 ld_message_id
    message_nr =                 ld_message_nr
*   with_docu =                  ld_with_docu
  IMPORTING
    message_text =               ld_message_text
  TABLES
    docu_tab =                   it_docu_tab
    docu_tech =                  it_docu_tech
  EXCEPTIONS
    CANCELLED =                  1
    NOT_FOUND =                  2
    PERMISSION_ERROR =           3
    .  "  RPY_MESSAGE_READ

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_message_text
 
 TYPE T100 ,
ld_language
 
 TYPE SY-LANGU ,
it_docu_tab
 
 TYPE STANDARD TABLE OF RPY_OBJTAB ,
wa_docu_tab
 
 LIKE LINE OF it_docu_tab,
ld_message_id
 
 TYPE RGLIF-MESSAGE_ID ,
it_docu_tech
 
 TYPE STANDARD TABLE OF TLINE ,
wa_docu_tech
 
 LIKE LINE OF it_docu_tech,
ld_message_nr
 
 TYPE T100-MSGNR ,
ld_with_docu
 
 TYPE RGLIF-WITH_DOCU .


ld_language = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_docu_tab to it_docu_tab.

ld_message_id = some text here 

"populate fields of struture and append to itab
append wa_docu_tech to it_docu_tech.

SELECT single MSGNR 
  FROM T100 
  INTO ld_message_nr.


ld_with_docu = some text here