Communication Between R/2 Systems (SAP Library - SAP Communication: CPI-C Programming (BC-CST-GW))

Communication Between R/2 Systems

Purpose

Between R/2 Systems, program-to-program communication is possible with the following restrictions:

Restrictions for MVS/VSE hosts

Communication is only possible on MSE/VSE hosts when CICS is used as the data communications system. Local communication in R/2 is not possible because CICS does not support a local conversation via SNA-LU6.2.

Restrictions for BS2000 hosts

Communication between R/2 Systems on BS2000 is possible if both systems are operated under UTM.

Prerequisites

With this constellation, you must note the following guidelines:

When using the RFC interface (from 5.0D):

The side info tables XCOM and RFCD must be configured.

The destination of the function call must match the corresponding entry in XCOM and RFCD.

The called function must be an ABAP function module, which has the "remote" ID in the function library.

Using the CPI-C interface

The calling ABAP program must build the data for the logon to the target system, convert it to EBCDIC and receive the response (possibly a denial) from the target system.
The table XCOM must be configured in the calling R/2 System.

For details on the configuration of XCOM, refer to the relevant topic in the following documentation:

BC SAP Communication: Configuration

The target ABAP program must contain the form routine specified in the connect data.

Process flow

For more details on the RFC interface, refer to the documentation Remote Communications.

For details on CPI-C calls, refer to the topic CPI-C-Implementation in ABAP.