The SAP system logs on to the R/2 System to send or retrieve IDocs. The necessary logon data is maintained in the SAP system under an RFC destination. The target system (R/2) and the technical communication attributes are maintained in the table TXCOM.
Maintaining the RFC Destination
To create an RFC destination, choose R/2 Connections and choose Create.
(SM59). Position the cursor onName the RFC destination (for example, K50-Test) and the connection type 2 (connection to the R/2 system). Enter a description of the RFC destination. This data only has to be entered once before you can save the destination. The data is not relevant to the CPI-C connection. The following logon data, however, is important:
Client in the R/2 system
User and password in the R/2 system
Save your entries.
This transaction is called "Maintain RFC Destinations", but only the logon data (client, user name, password and logon language) is entered for port type CPI-C, not the target system itself. For this reason, the connection test for this transaction does not have to be successful. The actual name of the target system is read as a "symbolic destination" from table TXCOM.
If you want the system to make a connection log when sending IDocs, then you must select the field Trace.
Maintaining Entries in table TXCOM
Choose
(SM54). Choose .Maintain the R/2 System name (for example, K50) as the Destination. Enter the following parameters, in addition to the name:
Gateway host and gateway service
Protocol C ( = partner can be reached via CPI-C)
You can determine the gateway host and service via the gateway monitor or the report RSPARAM.
Save your entries.
The "logical unit" ( LU column) and the transaction program ( TP column) are not read from TXCOM, but from the sideinfo file on the SNA-compatible gateway server.
The SAP system recognizes the R/2 System (TXCOM entry) and vice versa (logon data). Continue with