Side Information in R/2 on BS2000 Host: XCOM
Definition
On the BS2000 host, the XCOM table is used to assign logical partner names to their LU and TP names. This makes you independent of generation parameters when programming (for example in the ABAP program). You can therefore transfer the program, without changes, from a test system into a productive system. The XCOM table has the following structure:
XCOM
table parameters:
Name |
Type |
Length |
Description |
SDEST |
CHAR |
20 |
Symbolic destination (Key field) |
LU |
CHAR |
8 |
Name of the logical unit |
TP |
CHAR |
8 |
Name of the transaction program |
CTYPE |
CHAR |
1 |
Communication type |
Integration
Parameters for UTM-UTM Connections
In UTM implementations, the LU name corresponds to the LPAP name, with which the UTM partner application is addressed. The TP name corresponds to the LTAC name, with which the remote UTM partial program is addressed.
The UTM partial program is started by the partner application after the ABAP program has relocated the first RECEIVE call.
The LPAP name is therefore registered in the LU field, and the local TAC of the remote application (LTAC) is registered in the TP field.
Under UTM, the third parameter of Table XCOM (CTYPE) is also used. It has the following values depending on the communication types:
A
Asynchronous message transfer
The queue driver transfers DOUT queue messages as asynchronous UTM messages. As of UTM Version 3.3, synchronous communication is supported.
D
Direct message transfer
Messages are sent via the APQ interface as UTM-D messages directly without buffering in the DOUT file.
Prerequisites:
The partner is a UTM application. If the interface is used in an update task, no separate update task is allowed.
H
Gateway-to-host communication
Communication takes place via a GWHOST task. This parameter value is required if you use component 83, as a UTM-D communication is initiated by default.
K
SAP leaves the transaction open and ends the transaction step with PEND KP (standard: PEND RE)(from 5.0 G)
Parameters for GWHOST Connections
If communication to an R/3 System or a non-SAP program takes place via the gwhost program, the XCOM parameters have the following meaning:
SDEST
Symbolic destination used in the ABAP program
LU
Non-relevant
TP
Destination with which the Job SAPGWHO (program gwhost) determines further directions in the side information file (SAPGW.DATA.SIDEINFO)
An example of table XCOM settings for the gwhost program can be found under
Connection Setup by the R/2 System.