Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-RRR-SAA (Application Component) System Administration Assistant⤷
SSAA (Package) System Administration Assistant
Basic Data
| Data Element | SAAREMOTE |
| Short Description | Remote access allowed |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SAAREMOTE | |
| 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 | Remote |
| Medium | 15 | Remote |
| Long | 20 | Remote allowed |
| Heading | 10 | Remote |
Documentation
Definition
Setting this flag enables a remote access from the System Administration Assistant.
In place of multiple-system landscapes, we refer here to a 2-system landscape consisting of a development system and a production system. When a development and production system is mentioned in the following description, this can be any system from the underlying system landscape.
The System Administration Assistant contains tasks for the administrator, the project manager and project members, which are to be performed in the development system as tasks that affect the production system. To be able to administrate from one system without being logged on to another system in parallel, you can enable a remote access for the other system by setting this flag.
You must set the flag in the source system.
If the flag is set in the production system, you can remotely access the development system.
If you choose an action that must be performed in the development system, the transaction is executed remotely in the target system.
If the flag is switched off, remote access is expressly disabled.
We recommend allowing remote access from the production system to the development or quality system. In system landscapes with at least 3 systems, you need to declare one system as the master system. All status information is gathered centrally there.
To enable remote access, you must define the RFC connection RRR@<SID> using Transaction SM59, for example, setting the RFC destination RRR@DEV. The connection type is RFC connections. Enter the target host and a short description. For the logon data, enter the target client, for example, client 200. For the user, choose Current user. Save the settings for the connection and test the remote login. The logon to system DEV occurs in this case with the user currently logged on. If the user is defined in the target system, the logon can continue.
The System Administration Assistant always uses the RFC connection RRR@SID, where SID is the system ID of the remote system.
You can also generate the RFC connection using the System Administration Assistant. The first time you call a remote transaction, the system asks you to set the RFC connection. You can also set up or modify the RFC connection by choosing from the menu Utilities -> Check RFC Connection.
This RFC connection requires that the logon screen for the remote system is sent each time you call the System Administration Assistant. If you want to suppress this function, you must define a trust relationship between the current system and the target system (see Online Help for transaction SM59: RFC Programming in ABAP -> Trusted System: Maintaining Trust Relationships Between SAP Systems ).
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
