The R/3 System logs on to the R/2 System to send or retrieve IDocs. The necessary logon data is maintained in the R/3 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
In the initial node of the IDoc interface go to the same place via IDoc ® RFC destination.
·
Client in the R/2 System·
User and password in the R/2 SystemSave 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.
Maintaining entries in table TXCOM
·
Gateway host and gateway service·
Log C ( = partner can be reached via CPI-C)You can determine the gateway host and service via the
gateway monitor or the report RSPARAM.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.
Result
The R/3 System recognizes the R/2 System (TXCOM entry) and vice versa (logon data). Continue with
Configuring the CPI-C Port: Port Definition