Send RFC to SAP XI – Asynchronous

[Former Member]

This blog deals with triggering an RFC from SAP R/3 asynchronously. The configurations required at SAP R/3 for triggering RFC’s are explained by Michal and Shabarish, but there is no blog on sending RFC asynchronously. This blog provides a complete walk through from triggering RFC from SAP R/3 Asynchronously.

My requirement is to execute the RFC in SAP R/3 and send the output to SAP XI which needs to download to the database. I do not require any response from the database. I am using RFC_READ_TABLE function module in SAP R/3. This function module expects the Table name as Input parameter.

By default, if there is any input parameter to be passed to the sender RFC, it treats it as a synchronous call. The work around to achieve this requirement is to create a dummy RFC which would not have any import parameters and just the export parameters or table parameters as shown below:



Then on create an executable report in SE38. The first step in the program would be to execute the RFC_READ_TABLE function module in SE38 using a variant. Pass on the output of RFC_READ_TABLE to the ZRFC_READ_TABLE (dummy) function module. Sample code is shown below.

*&---------------------------------------------------------------------**& Report  ZRFC_READ_TABLE_EOFM                                        **&                                                                     **&---------------------------------------------------------------------**&                                                                     **&                                                                     **&---------------------------------------------------------------------*REPORT  zrfc_read_table_eofm.data: i_options like RFC_DB_OPT occurs 0,      i_fields  like RFC_DB_FLD occurs 0,      i_data    like TAB512 occurs 0,      i_table_name like dd02L occurs 0 with header line.SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.PARAMETERS: tab_name like DD02L-TABNAME.SELECTION-SCREEN: END OF BLOCK b1.CALL FUNCTION 'RFC_READ_TABLE'  EXPORTING    query_table                = tab_name*     DELIMITER                  = ' '*     NO_DATA                    = ' '*     ROWSKIPS                   = 0*     ROWCOUNT                   = 0  tables    OPTIONS                    = i_options    fields                     = i_fields    data                       = i_data   EXCEPTIONS     TABLE_NOT_AVAILABLE        = 1     TABLE_WITHOUT_DATA         = 2     OPTION_NOT_VALID           = 3     FIELD_NOT_VALID            = 4     NOT_AUTHORIZED             = 5     DATA_BUFFER_EXCEEDED       = 6     OTHERS                     = 7          .*IF sy-subrc <> 0.**   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO**           WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.*ENDIF.I_TABLE_NAME-TABNAME = tab_name.append I_table_name.CALL FUNCTION 'ZRFC_READ_TABLE_EOFM' IN BACKGROUND TASK DESTINATION'NWDCLNT100'  TABLES    i_data                      = i_data    i_options                   = i_options    i_fields                    = i_fields    i_table_name                = i_table_name EXCEPTIONS   COMMUNICATION_FAILURE       = 1   SYSTEM_FAILURE              = 2   OTHERS                      = 3          .IF sy-subrc <> 0.* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.ENDIF.commit work.

This ZRFC_READ_TABLE_EOFM function should be called with DESTINATION as the TCP/IP RFC destination created for registering the program ID in SM59 transaction.

DO NOT forget to execute ‘COMMIT WORK’ after executing the RFC !!!!!!!!