Types of Destinations
Each destination has a connection-type field (Connection type), which tells the kind of system connection:
Type 2 entries specify R/2 systems. No further specification is required, i.e. when you create a type 2 entry, you only need to give the host name; all communications information is already stored in the sideinfo table in the SAP Gateway host. You can, however, specify logon information if desired.
Example entry name: K50
Type 3 entries specify R/3 systems. When you create a type 3 entry, you must give the host name and communications service. You can also specify logon information if desired. From R/3 Release 3.0 onwards, you can also specify the load-balancing option if desired.
From R/3 Release 3.0 onwards, it is possible to specify an application server from the R/3 message server. The application server is then determined according to the load-balancing process. This applies both for RFCs between R/3 Systems and external calls to R/3 Systems.
Example entry name: K11
Type I entries specify R/3 systems connected to the same data base as the current system. These entries are pre-defined and cannot be modified. The entry names are the same as those used in the SAP Message Server (transaction SM51)
Example entry name: hs0010_K11_24
Instead of specifying a system connection, type L (logical) entries refer to a physical destination. Type L destinations can also refer to other type L entries. A type L entry uses the information in the "referred-to" entry, and adds further information of its own. Typically, the "referred-to" entry gives the host information, and the type-L entry gives logon data. You can also set a user name, an explicit password, a logon language or an explicit client.
A type L entry can refer to other type L entries.
Example entry name: K11_SD or K11_01
Type X entries specify systems where device drivers in ABAP have been specially installed. When you create a type X entry, you must give the name of the ABAP device driver.
Type T destinations are connections to external programs that use the RFC API to receive RFCs. The activation type can be either Start or Registration.
If it is Start, you must specify the host name and the pathname of the program to be started.
Activation Type Start
The communication method depends on how you select the program location:
In this case, the program is started either by the default gateway for the system or by the explicitly specified gateway (gwrd) via remote shell.
Ensure that the computer with the gateway process can access the specified computer by entering
In order to be able to start a program on another computer using remote shell, the target system must fulfil certain conditions.
To check this, logon to the computer containing the gateway process with the appropriate user ID and enter the command
On choosing Application server and specifying your program, you can start the program from the SAP application server.
First, ensure that the program can be accessed from the SAP application server and that the SAP application server has the authorization to start the program.
To check this, logon with the user ID of the SAP application server (e.g. c11adm). If possible, change to the working directory of the SAP application server (/usr/sap/.../D.../work) and try to start the RFC server program manually from there. (As in the above case, if you call an RFC server program without parameters, the RfcAccept call always returns an error code (RFC_HANDLE_NULL) and the program terminates at once.)
On choosing Front-end workstation and specifying your program, you can start the program from the SAPGUI.
Ensure that you can access the program with SAPGUI.
Ensure that SAPGUI has the authorization to start the program.
To check this, simply call the RFC server program in your environment.
The function call can also be transactional (CALL FUNCTION... IN BACKGROUND TASK DESTINATION...).
Activation Type Registration
If the activation type is Registration, you have to identify a registered RFC program. With an SAP gateway, an RFC server program can be registered under this ID and then wait for RFC calls from different SAP Systems.
Example entry name: SERVER_EXEC
Type M entries are asynchronous RFC connections to R/3 Systems via CMC (protocol X.400).
Type S corresponds to type 2, except that the destination is SNA or APPC.