Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-TWB-TST-P-GPA (Application Component) Global Performance Analysis (Transaction ST30)⤷
S_PERF_TRA (Package) New Performance Trace / Statistics with DB Connection
Basic Data
| Data Element | DESTIN_Z |
| Short Description | Destination of the Central System |
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 | ||
| Search Help: Parameters | ||
| 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 | 10 | CenSysDest |
| Medium | 19 | Central Sys. Dest. |
| Long | 28 | Central System Destination |
| Heading | 28 | Central System Destination |
Documentation
Definition
Destination of the central monitoring system in a system landscape.
Use
You can enter a destination here, at which, for example, non-SAP R/3 system components (such as J2EE components) are registered. Only using this destination (usually the central system that is used for monitoring the system landscape), can the statistical data for these system components be collected. If no specification is made, the current system is used as the central monitoring system.
The destination entered here is only taken into account if "With Distributed Statistical Data" was also selected.
Supplementary Documentation - DESTIN_Z 0001
Use
The trusted system is identifed using this RFC destination. The destination may not now be changed.
Procedure
Examples
Dependencies
Supplementary Documentation - DESTIN_Z 0002
Use
RFC destiantion that points to an SSF server program.
Procedure
Examples
SAPSSFATGUI SAPSSFATDEST
Dependencies
Supplementary Documentation - DESTIN_Z 0003
Use
Enter an RFC destination of another system, if the transactions of the role are to be started in the other system.
To transfer menu entries from another system using an RFC connection, enter a target system and choose From the SAP Menu. A dialog box appears, in which you can specify whether you want to transfer the menu locally or using a remote system. If you choose to do so in the remote system, the SAP menu of the remote system is provided for you.
If you want to navigate using the SAP Easy Access menu in SAP GUI, you should only use RFC destinations that have been created in accordance with the trusted system concept. In this way, you can ensure that you can work with the same user in the target system.
Alternatively, you can also specify a variable in the Target System field, that points to an RFC destination. Variabes are assigned to RFC destinations in transaction SM30_SSM_RFC.
To distribute the role, choose Distribution. If the text Distribution incomplete appears, perform the distribution again. The authorization data of the role is not distributed. You therefore need to complete the authorization data of the distributed roles in the target system.
If you leave the field empty, the transactions are started in the same system, in which the user is logged on.
Dependencies
Example
Supplementary Documentation - DESTIN_Z 9000
Use
In the Alert Monitor, the RFC destination is the connection to the remote monitoring segments.
For SAP R/3 servers of the local SAP R/3 system and for host and database segments, the monitoring architecture automatically assigns the name.
For remote systems and servers, you specify the name using the Remote Monitoring function in transaction RZ21.
If necessary, you can change the name of the RFC destination here in both cases. In this case, you need to ensure that the destination is also entered in the RFC maintenance transaction (SM59).
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
