Show TOC

Sending IDocs from External Systems to SAPLocate this document in the navigation structure

Use
Process

The following graphic highlights the program structure logic.

The calling, external program uses the following functions of the RFC Software Development Kit (RFC SDK):

  • RfcOpen

    An RFC connection to the server system is built with this call. You can define the loogon to the SAP system including the server name of the SAP target machine, SAP logon, user, password, and so on in the C program or in the saprfc.ini file.

After the connection is built to the server system, both of the following functions for the tRFC must be called in the client program:

  • RfcCreateTransID

    This call determines the transaction ID (TID) that was created in the server system.

  • RfcIndirectCall

    The RFC data together with the TID is transferred to the server system with this call.

    In case of errors, the client program repeats this call.

    For this, the RfcCreateTransID call must use the old TID. Otherwise it is not guaranteed that the RFC function is only executed one time in the SAP system.

    The transaction is ended after this call is executed successfully. The calling program can then update its own TID administration (for example, delete the TID entry).

For more information, see the documentation Writing RFC Programs in ABAP or in the RFC SDK documentation.

The use data is to be formatted in IDoc form and placed in an internal table of the structure EDI_DD40 (EDI_DD before 4.0). A control record needs to be built for each IDoc and placed in an internal table of the structure EDI_DD40 (EDI_DD before 4.0). The form of the data transfer is also described in the documentation.