Side Information In R/3: TXCOM
Definition
There is a side info table called TXCOM in the database of each R/3 System. It contains the following column headings:
Dest
Destination
Symbolic name of the target system
(up to 8 characters)
LU
Logical unit
(up to 8 characters)
TP
Transaction program
(up to 8 characters)
Prot
Protocol type (1 character)
The following protocol types are possible:
C: |
The partner program is an ABAP program in R/2. |
I: |
The partner program is an ABAP program in R/3, which can be accessed via TCP/IP. |
E: |
The partner program is a C program, which can be accessed via TCP/IP and started by means of fork/exec, remote shell or rexec. |
F: |
The partner program is a C program, which can be accessed via TCP/IP and started externally (for example, by the R/3 Frontend or an R/3 Server). |
R: |
The partner program is a C program, which can be accessed via TCP/IP and has registered at the SAP-Gateway. |
Gateway host
Host computer of the SAP Gateway
(up to 20 characters)
If the computer name is longer, you must define a symbolic computer name in the THOST table.
Gateway service
SAP Gateway service
(up to 20 characters)
Use
The table txcom must be configured according to the target system:
Target System: R/3
Two ABAP programs on two R/3 servers (BIN and B20), located on the same computer, communicate with one another.
The connection parameters must be defined in the TXCOM side info table. If the target system is an R/3 System Release 2.1 or higher, you can also specify sapgw<nr> under TP.
The following table has examples of values.
DEST LU TP Prot Gateway-Host Gateway-Service
---------------------------------------------------------------
bin hs0001 sapdp53 I is0001 sapgw00
b20 hs0001 sapdp21 I is0001 sapgw00
DEST21 hw0002 sapgw53 I - -
Target System: R/2 (MVS/VSE Host)
An ABAP program of an R/3 System communicates with an ABAP program of an R/2 System on a MVS/VSE host.
Example:
DEST LU TP Prot Gateway-Host Gateway-Service
-----------------------------------------------------------
S50 S50 X1SA C is0001 sapgw00
K50 K50 X1SA C is0002 sapgw01
The LU parameter value in TXCOM is of no relevance to R/3 to R/2 communication.
Example:
DEST=50
LU=K50T00
TP=X1SA
For more details, refer to the topic
Side Information on OS/2, Windows NT, UNIX and AS/400 Platforms: . SideinfoTarget System: R/2 (BS2000 Host)
An ABAP program of an R/3 System communicates with an ABAP program of an R/2 System on a BS2000 host with the SAP Gateway under DCAM.
Example:
DEST LU TP Prot Gateway-Host Gateway-Service
-------------------------------------------------------------
BS2S50 BS2S50 X1SA C sb0002 sapgw02
BS2K50 BS2K50 X1SA C sb0002 sapgw02
For more details, refer to the topic
Maintaining the Side Info File in BS2000 in the section "BS2000 Host Systems".
Target System: Non-SAP System
An ABAP program of an R/3 system communicates with a program written in C of an external system.
The protocol type for this type of communication must be
E , as the partner program is located outside the SAP system and can be accessed via TCP/IP.In the following side info example, the SAP Gateway and the target system are on different computers. The SAP Gateway starts the program written in C using Remote Shell.
For this the following requirements must be met:
/* C Program: rcvcpic */
DEST LU TP Prot Gateway host gateway service
---------------------------------------------------------------
rcvcpic iw10004 rcvcpic E is0001 sapgw00