SAP RSTI_COMMUNICATION_HANDLER Function Module for









RSTI_COMMUNICATION_HANDLER is a standard rsti communication handler SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 rsti communication handler FM, simply by entering the name RSTI_COMMUNICATION_HANDLER into the relevant SAP transaction such as SE37 or SE38.

Function Group: RSTI
Program Name: SAPLRSTI
Main Program: SAPLRSTI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RSTI_COMMUNICATION_HANDLER 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 'RSTI_COMMUNICATION_HANDLER'"
EXPORTING
* E_FCODE = "
* E_REXEC = 'X' "
* E_SEL_SCREEN = "
E_FCCLS = "Function code class
* E_REC = "Payee information
* E_RDARK = ' ' "

IMPORTING
I_REC = "Selected Recipient
I_EXIT = "

EXCEPTIONS
APPL_STACK_NOT_INITIALIZED = 1 NO_LINES = 2 NO_LINE_PICKED = 3 TOOL_NOT_EXIST = 4 NOT_FOUND = 5
.



IMPORTING Parameters details for RSTI_COMMUNICATION_HANDLER

E_FCODE -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_REXEC -

Data type: C
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_SEL_SCREEN -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_FCCLS - Function code class

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

E_REC - Payee information

Data type: RSTIREC
Optional: Yes
Call by Reference: No ( called with pass by value option)

E_RDARK -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RSTI_COMMUNICATION_HANDLER

I_REC - Selected Recipient

Data type: RSTIREC
Optional: No
Call by Reference: No ( called with pass by value option)

I_EXIT -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

APPL_STACK_NOT_INITIALIZED -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_LINES -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NO_LINE_PICKED - No report was selected

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TOOL_NOT_EXIST -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_FOUND - Function module does not exist

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RSTI_COMMUNICATION_HANDLER 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_i_rec  TYPE RSTIREC, "   
lv_e_fcode  TYPE C, "   
lv_appl_stack_not_initialized  TYPE C, "   
lv_i_exit  TYPE C, "   
lv_e_rexec  TYPE C, "   'X'
lv_no_lines  TYPE C, "   
lv_e_sel_screen  TYPE C, "   
lv_no_line_picked  TYPE C, "   
lv_e_fccls  TYPE C, "   
lv_tool_not_exist  TYPE C, "   
lv_e_rec  TYPE RSTIREC, "   
lv_not_found  TYPE RSTIREC, "   
lv_e_rdark  TYPE C. "   ' '

  CALL FUNCTION 'RSTI_COMMUNICATION_HANDLER'  "
    EXPORTING
         E_FCODE = lv_e_fcode
         E_REXEC = lv_e_rexec
         E_SEL_SCREEN = lv_e_sel_screen
         E_FCCLS = lv_e_fccls
         E_REC = lv_e_rec
         E_RDARK = lv_e_rdark
    IMPORTING
         I_REC = lv_i_rec
         I_EXIT = lv_i_exit
    EXCEPTIONS
        APPL_STACK_NOT_INITIALIZED = 1
        NO_LINES = 2
        NO_LINE_PICKED = 3
        TOOL_NOT_EXIST = 4
        NOT_FOUND = 5
. " RSTI_COMMUNICATION_HANDLER




ABAP code using 7.40 inline data declarations to call FM RSTI_COMMUNICATION_HANDLER

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.

 
 
 
 
DATA(ld_e_rexec) = 'X'.
 
 
 
 
 
 
 
 
DATA(ld_e_rdark) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!