From R/3 to R/2 (SAP Library - SAP Communication: CPI-C Programming (BC-CST-GW))

From R/3 to R/2

Purpose

An ABAP program in an R/3 System uses an RFC or CPI-C call to start an ABAP program in an R/2 System under DCAM or UTM on a BS2000 host, and exchanges data with this program.

Prerequisites

Using the RFC interface:

The SAP Gateway must run under DCAM in BS2000.

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

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

Using the CPI-C interface

The SAP Gateway must run under DCAM in BS2000.

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

If you are using the CPI-C calls from ABAP, 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 side info table TXCOM must be configured in the calling R/3 System. For this, use transaction code SM54.

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

BC SAP Communication: Configuration

If there is a side info file SAPGW.DATA.SIDEINFO on the BS2000 host, an application can only be reached if the side info file contains an entry for this application.

For details on configuration, please refer to the documentation BC - SAP Communication: Configuration under the topic Connection Setup to the R/2 System

Process flow

Using the RFC interface:

Once the above requirements have been met, select the target system with the Transaction SM59.

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

Using the CPI-C interface

For details on configuration, please refer to the documentation BC - SAP Communikation: Configuration under the topic Connection Setup to the R/2 System