Show TOC

Background documentationPossible Parameters Locate this document in the navigation structure

 

Type R

Registers an RFC server program at an SAP gateway and lets it wait for RFC calls by an R/2 or an SAP system.

The following parameters can be used:

DEST = <destination in RfcAccept>

TYPE = <R: Register at SAP gateway>

PROGID = <program-ID, optional; default: destination >

GWHOST = <host name of the SAP gateway>

GWSERV = <service name of the SAP gateway>

RFC_TRACE = <0/1: OFF/ON, optional; default:0(OFF)>

In an SAP system the program-ID and this SAP gateway must be specified in the Destination entry defined with transaction sm59: use connection type T and register mode.

To work with R/2 Systems, the entry in the sideinfo file for the gwhost program must have R instead of E as PROTOCOL parameter.

The host service names of the SAP gateway must be specified in the hosts and services files (<service name> = sapgw<SAP system number>).

Type B

Connects to an SAP system using load balancing. The application server will be determined at runtime.

The following parameters can be used:

DEST = <destination in RfcOpen>

TYPE = <B: use Load Balancing feature>

R3NAME = <name of SAP system, optional; default: destination>

MSHOST = <host name of the message server>

GROUP = <group name of the application servers, optional; default: PUBLIC>

RFC_TRACE = <0/1: OFF/ON, optional; default:0(OFF)>

ABAP_DEBUG = <0/1: OFF/ON, optional; default:0(OFF)>

USE_SAPGUI = <0/1: OFF/ON, optional; default:0(OFF)>

The host name and the service name of the message server must be defined in the 'hosts' and 'service' files (<service name> = sapms<SAP system name>).

Type A

Connects to a specific SAP application server.

The following parameters can be used:

DEST = <destination in RfcOpen>

TYPE = <A: RFC server is a specific SAP application server>

ASHOST = <host name of a specific SAP application server>

SYSNR = <SAP system number>

GWHOST = <optional; default: gateway on application server>

GWSERV = <optional; default: gateway on application server>

RFC_TRACE = <0/1: OFF/ON, optional; default:0(OFF)>

ABAP_DEBUG = <0/1: OFF/ON, optional; default:0(OFF)>

USE_SAPGUI = <0/1: OFF/ON, optional; default:0(OFF)>

The host name and the service name of the specific application server must be defined in the hosts and services files (<service name> = sapdp<SAP system number>).

The host name and the service name of the SAP gateway must be defined in the hosts and services files. If GWHOST and GWSERV are not specified, the service name of the SAP gateway must be defined in the services file (<service name> = sapgw<SAP system number>).

Type 2

Connects to an R/2 System.

The following parameters can be used:

DEST = <destination in RfcOpen and in the 'sideinfo' file for the SAP gateway>

TYPE = <2: RFC server is an R/2 System>

GWHOST = <host name of the SAP gateway>

GWSERV = <service name of the SAP gateway>

RFC_TRACE = <0/1: OFF/ON, optional; default:0(OFF)>

The host name and the service name of the SAP gateway must be defined in the hosts and services files. (<service name> = sapgw<SAP system number>).

Type E

Connect to another external program as RFC server program.

DEST = <destination in RfcOpen>

TYPE = <E: RFC server is an external server>

GWHOST = <host name of the SAP gateway>

GWSERV = <service name of the SAP gateway>

TPHOST = <host name of the RFC server program>

TPNAME = <name of the RFC server program>

RFC_TRACE = <0/1: OFF/ON, optional; default:0(OFF)>

The host name and the service name of the SAP gateway must be defined in the hosts and services files (<service name> = sapgw<SAP system number>).

See "Configurations" in Establishing an RFC Connection from an SAP System for details about how to start an RFC server program by an SAP gateway.