RSAP_TRFC_SEND SAP Function module

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

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

Pattern for FM RSAP_TRFC_SEND - RSAP TRFC SEND

CALL FUNCTION 'RSAP_TRFC_SEND' "
  EXPORTING
    i_rcvprn =                  " rosrequest-rcvprn
    i_s_header =                " rssdheader
*   i_flag_commit_work =        " rsaapi_if-initflag
*   i_trfc_option =             " rsaapi_if-initflag
  IMPORTING
    e_s_callback_info =         " rsaptrfccb
  TABLES
    i_t_data =                  " rodatatrsp
  EXCEPTIONS
    TRFC_ERROR = 1              "
    .  "  RSAP_TRFC_SEND

ABAP code example for Function Module RSAP_TRFC_SEND

The ABAP code below is a full code listing to execute function module RSAP_TRFC_SEND 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_e_s_callback_info  
 
 TYPE RSAPTRFCCB
,
it_i_t_data  
 
 TYPE STANDARD TABLE OF RODATATRSP,"TABLES PARAM
wa_i_t_data
 
 LIKE LINE OF it_i_t_data
.



DATA(ld_i_rcvprn) = some text here

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


DATA(ld_i_flag_commit_work) = some text here


DATA(ld_i_trfc_option) = some text here
 

"populate fields of struture and append to itab
append wa_i_t_data to it_i_t_data.
.

CALL FUNCTION 'RSAP_TRFC_SEND'
  EXPORTING
    i_rcvprn =                   ld_i_rcvprn
    i_s_header =                 ld_i_s_header
*   i_flag_commit_work =         ld_i_flag_commit_work
*   i_trfc_option =              ld_i_trfc_option
  IMPORTING
    e_s_callback_info =          ld_e_s_callback_info
  TABLES
    i_t_data =                   it_i_t_data
  EXCEPTIONS
    TRFC_ERROR =                 1
    .  "  RSAP_TRFC_SEND

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_e_s_callback_info
 
 TYPE RSAPTRFCCB ,
ld_i_rcvprn
 
 TYPE ROSREQUEST-RCVPRN ,
it_i_t_data
 
 TYPE STANDARD TABLE OF RODATATRSP ,
wa_i_t_data
 
 LIKE LINE OF it_i_t_data,
ld_i_s_header
 
 TYPE RSSDHEADER ,
ld_i_flag_commit_work
 
 TYPE RSAAPI_IF-INITFLAG ,
ld_i_trfc_option
 
 TYPE RSAAPI_IF-INITFLAG .



ld_i_rcvprn = some text here 

"populate fields of struture and append to itab
append wa_i_t_data to it_i_t_data.
ld_i_s_header = 'Check type of data required'.

ld_i_flag_commit_work = some text here

ld_i_trfc_option = some text here