Data Interfaces

Communication Between Two R/3 Systems
© SAP AG
hs5001, sapgw00 hs5101, sapgw01
System T01
Table TXCOM (T01)
TCP/IP
Dest LU TP Prot Gateway host Gateway service
BC415A hs5101 sapgw01 I
BC415B hs5101 sapgw01 I hs5101 sapgw01
System T02
Communication between two R/3 Systems is always based on the transport protocol TCP/IP.
For R/3 - R/3 communication, you need to maintain the R/3 tables TXCOM (for CPI-C) and RFCDES
(for RFC).
The destination Dest can be any name you choose.
LU (logical unit - related to IBM's SNA) is the "host name" of the R/3 partner system.
TP (transaction program name) is the sapgwXX of the partner system. Since a gateway service is assigned
to every application server, this name is unique.
For Prot (protocol), you enter an “I” for R/3 - R/3 communication.
The Gateway host entry is optional and specifies the host name of an alternative gateway. By default, the
system uses the gateway of the application server from which the communication is set up.
The Gateway service entry only makes sense if there is also an entry for Gateway host. It specifies the
service sapgwXX of the alternative gateway.
For an R/3 - R/3 RFC connection, you must make an entry in the table RFCDES. To maintain this table,
you use Transaction SM59. The connection type that you specify in the transaction is 3.