Side info tables contain both general and specific parameters.
As a rule, side info tables contain the following general parameters:
· Symbolic destination (DEST)
Side information for a specific partner program is indicated by a symbolic name for the target system. The symbolic name is followed by a series of connection parameters. These always include the following parameter values.
· Name of the logical unit (LU) of the partner
This parameter specifies the name of the LU, where the partner program is located. The local LU must know this LU when setting up a connection.
· Name of the transaction program (TP)
This parameter specifies the name of the remote program.
For more information refer to General Parameters.
Side info tables can contain parameters which are specific to a particular constellation and system platform. Some examples:
Protocol type (Parameter PROTOCOL in sideinfo, Prot in TXCOM) is an example of a parameter which is assigned a specific value according to constellation.
The following values are possible:
Protocol type |
Meaning |
C |
The partner program is an ABAP program in R/2. |
I |
The partner program is an NetWeaver ABAP program that can be accessed via TCP/IP. |
E |
The partner program is a program written in C, 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 SAP 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 (via SAP_CMREGTP, see SAP Communication Programming. |
A series of parameters are pre-defined as profile parameters with default values (see Configuring the SAP Gateway). If you do not want to work with these default values, you can assign alternative values to the corresponding parameters in the side info table.