Hierarchy
SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management⤷
FIN-SEM-BPS-BP (Application Component) Business Planning⤷
UPB (Package) SEM-BPS: Planning Applications
Basic Data
| Data Element | UPB_Y_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 | H_RFCDEST | |
| 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
The standard name of an RFC destination.
Use
If the receiver is an SAP System, then the name of the system is displayed here (for example, C11, CENTRAL_C11 ).
For external programs the program name is issued here.
The following standard names cannot be used in transaction SM59 for the destination:
'<hostname>_<systemname>_<systemnummer>',
'<hostname>_<systemname>_<systemnummer>_TRUSTED',
'<hostname>_<systemname>[groupname]',
'<hostname>_<systemname>[]',
'<hostname>_<systemname>_TRUSTED[groupname]',
'<hostname>_<systemname>_TRUSTED[]',
NONE[groupname] und NONE[].
These destinations are directly addressed by the system (for example, the internal connections automatically receive these destination names).
Supplementary Documentation - UPB_Y_RFCDEST0001
Use
The trusted system is identified through this RFC destination. The destination can no longer be changed.
Procedure
Examples
Dependencies
Supplementary Documentation - UPB_Y_RFCDEST0002
Use
RFC destination that refers to an SSF server program.
Procedure
Examples
SAPSSFATGUI SAPSSFATDEST
Dependencies
Supplementary Documentation - UPB_Y_RFCDEST0003
Use
Enter an RFC destination of another system, when the transactions of the roles should be started in the other system.
To copy menu options from another system using an RFC connection, enter a target system and choose From the SAP Menu. In a dialog box you can enter, whether you want to copy the menu locally or using a remote system. If you choose in the remote system wählen, you are offered the SAP menu of the target system.
If you want to navigate in the SAP GUI using the SAP Easy Access Menu, then only the RFC destinations should be used which were created in accordance with the trusted system concept. In this way it can be that the same users work in the target system.
Alternatively, a variable can also be entered in the field target system which refers to an RFC destination. Variables are assigned to the RFC destinations in the transaction SM30_SSM_RFC.
To distribute the role, choose Distribute. When the text Distribution incomplete appears, then you should distribute again . The authorization data of the role is not distributed. Therefore, the authorization data of the distributed roles must be completed in the target system.
If the field remains empty, then the transactions are started in the same system, in which the user is logged on.
Dependencies
Example
Supplementary Documentation - UPB_Y_RFCDEST9000
Use
In the alert monitor, the RFC destination describes the connection to the removed monitoring segments.
The monitoring architecture automatically assigns the names for R/3 servers of the local R/3 System as well as with host and database segments.
With remote systems and servers, the name is entered in the transaction RZ21 using the Remote monitoring function.
If required in both cases, the name of the RFC destination can be changed. In this case, you must ensure that the destination is also entered in the RFC maintenance transaction (SM59).
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20041006 |
| SAP Release Created in | 3.1B |
