Data Interfaces

R/3 R/2 Communication (IBM)
© SAP AG
Connection setup from R/3
hs5001 hs5002
UNIX, UNIX, NT NT (T01) (T01)
SAP SAP gateway
gateway
Host Host (K50)
(K50)
R/3 R/3
ABAP/4
ABAP/4
SNA SNA subsystem
subsystem
R/2 R/2
ABAP/4
ABAP/4
TCP/IP (remote)
shared memory (local)
Table RFCDES (T01) Gateway options
RFC destination K50 Gateway host: hs5002
Connection type 2 Gateway service: sapgw00
Dest LU TP Prot Gateway host Gateway service
K50 C hs5002 sapgw00
LU6.2
Table TXCOM (T01) Side info SAPgateway
DEST = K50
LU = K50T00
TP = X1SA
For communication from R/3 to R/2, an SNA gateway must be active (i.e. an SAP gateway plus the
relevant SNA subsystem). Ideally, this should be installed as a standalone gateway.
For the SNA-LU6.2 connection, the specific SNA product (SNA subsystem) of the hardware
manufacturer must be installed and configured on the gateway machine.
You can find out which products are supported on which platforms, and in which version, in the overview
SAP Supported Network Products.
In the case of a CPI-C communication between R/3 and R/2 where the R/3 System is the initiator of the
communication, you need to make an entry in der R/3 table TXCOM and an entry in the gateway table
sideinfo.
Table TXCOM:
- The destination Dest can be any name you choose
- LU and TP are dummy entries and can be left blank
- Prot (protocol) must be C
In the case of an RFC communication between R/3 and R/2 where the R/3 System is the initiator of the
communication, you need to make an entry in the R/3 table RFCDES and an entry in the gateway table
sideinfo.