Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-RFC (Application Component) RFC⤷
SRCX (Package) Development Class for Remote Communication: RFC and RMC
Basic Data
| Data Element | RFCTYPE_D |
| Short Description | Type of Entry in RFCDES |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCTYPE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Type |
| Medium | 15 | Connection Type |
| Long | 20 | Connection Type |
| Heading | 55 | Connection Type |
Documentation
Definition
Type of RFC connection.
By entering the type of RFC connection, you specify the communication method (TCP or SNA) and the logon type in the target system.
The possible connection types and their options are as follows:
Type L (logical) destinations normally refer to a physical destination. You can also set a user name, an explicit password, a logon language or an explicit client. Type L destinations can also refer to another type L destination.
Type 3 destinations refer to another ABAP system. You must specify the host name and the SAP system number of the target system.
Type 2 destinations refer to an R/2 System. No further specifications are required. Instead, you store the information required to establish the connection in the 'Sideinfo' file for SAP gateway.
Type I destinations are generated internally and thus cannot be changed. They describe ABAP systems that use the same database as the calling program. The names used are the same as in the SAP message server or in Transaction SM51.
Type T destinations are connections to external programs that use the RFC API to receive 'Remote Function Calls'. You must specify the host name and the pathname of the program to be started. The communication method depends on how you select the program location:
- 'Explicit' selection
In this case, the program is started either by the standard gateway program 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 '/etc/ping <host name>'.
In order to be able to start a program on another computer using 'remote shell', the target system must fulfil certain conditions. The user ID of the gateway process must exist and a file called .rhosts must also be present in the user's home diretory. The file .rhosts must contain the name of the calling computer. To check this, logon to the computer containing the gateway process with the appropriate user ID and enter the command 'remsh <host name> <program name>'. The <host name> and <program name> must be the same as in SM59. (If you call an RFC server program without any parameters, the RfcAccept call always returns an error code (RFC_HANDLE_NULL) and the program terminates at once.) - 'Server'
By entering the 'server', you 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, go into the 'work' 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.) - 'User'
By entering the 'user', the program is started by 'SAPGUI', i.e. under the user's ID and environment.
Ensure that you can access the program with 'SAPGUI'/'SAPTEMU'.
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 asynchronous (CALL FUNCTION ... IN BACKGROUND TASK DESTINATION ...).
Type X destinations are special destinations with their own I/O driver routines written in ABAP. You must specify the driver program.
Type M destinations are asynchronous RFC connections to ABAP systems via CMC (protocol X.400).
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in |
