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 | RFCDEST |
| Short Description | Logical Destination (Specified in Function Call) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCDEST | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | RFCDES |
Further Characteristics
| Search Help: Name | F4_RFCDESTYPEALL | |
| Search Help: Parameters | RFCDEST | |
| Parameter ID | RFC | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 5 | Dest. |
| Medium | 11 | Destination |
| Long | 15 | RFC Destination |
| Heading | 15 | RFC Destination |
Documentation
Definition
Standard name of an RFC destination.
Use
If the receiver is an SAP system, the name of the instance in the SAP system is displayed (for example, C11, CENTRAL_C11).
If the receiver is an external program, the program name is normally displayed here.
If the field in SM51 is empty, it is an RFC server.
You may not use the following standard names for the destination in transaction SM59:
'<hostname>_<systemname>_<system number>',
'<hostname>_<systemname>_<system number>_TRUSTED',
'<hostname>_<systemname>[group name]',
'<hostname>_<systemname>[]',
'<hostname>_<systemname>_TRUSTED[group name]',
'<hostname>_<systemname>_TRUSTED[]',
NONE[groupname] und NONE[].
These destinations are addressed directly by the system (internal connections are automatically assigned these names).
Supplementary Documentation - RFCDEST 0001
Use
This RFC destination identifies the trusted system. You may not change the destination.
Procedure
Examples
Dependencies
Supplementary Documentation - RFCDEST 0002
Use
RFC destination pointing to an SSF server program.
Procedure
Examples
SAPSSFATGUI SAPSSFATDEST
Dependencies
Supplementary Documentation - RFCDEST 0003
Use
Enter an RFC destination of a different system, if the transactions of the role are to be started in this other system.
To transfer menu entries from another system via an RFC connection, enter a target system and choose From the SAP Menu. In the dialog box you can specify if you want to transfer the menu in a local system or via a remote system. If you choose a remote system, the SAP menu of the remote system is offered to you.
If you want to navigate in the SAP GUI via the SAP Easy Access menu, only RFC destinations should be used that have been created according to the trusted system concept. This ensures that the target system works with the same user.
Alternatively, a variable can also be specified in field Target System, that links to an RFC destination. Variables are assigned to RFC destinations in transaction SM30_SSM_RFC.
To distribute the role, choose Distribute. If the text Distribution Incomplete appears, you should perform the distribution again. The authorization data of the role is not distributed. Therefore the authorization data of the roles has to be updated in the target system.
If the field remains empty, the transactions are started in the same system in which the user is logged on.
Dependencies
Example
Supplementary Documentation - RFCDEST 1
Use
This RFC destination identifies the trusted system. You may not change it.
Procedure
Examples
Dependencies
Supplementary Documentation - RFCDEST 3333
Use
The RFC destination contains the connection data to the telephony server.
You can enter an existing RFC destination or select RFC destination to branch to the transaction to create RFC destinations.
Dependencies
Example
Supplementary Documentation - RFCDEST 9000
Use
In the Alert Monitor, the RFC destination identifies the connection to the remote monitoring segments.
The monitoring architecture assigns the name automatically for R/3 servers in the local R/3 System and host and database segments.
In remote systems and servers, the name is specified using the Remote Monitoring function in Transaction RZ21.
In either case, you can change the RFC destination name here. If you do, you must ensure that the destination has been entered as as remote destination in the RFC maintenance transaction (SM59).
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
