...
The fields required to add the new system successfully, are:
| System name | Descriptive name of the system, it will be shown in the landscape tree. |
|---|---|
| System ID | ID of system, the same system cannot be added to the landscape twice. |
| RFC destination | The name for the RFC destination for the added system that needs to be defined on central system. OutBoard for Housekeeping cockpit communicates with the systems via remote function calls. No matter if the cockpit populates settings, pushes task execution, communication always directs from cockpit to systems. So there's no need to configure fully bi-directional RFC connection in the system – RFC client is enough. In the RFC connection the logon user defined must be the type SYSTEM or DIALOG (see transaction su01, tab "Logon data"). SYSTEM type brings limitation in executing standard SAP tasks executed as transactions. |
| Secondary RFC | Optional parameter. If Primary RFC is not of a DIALOG type and the task requires it, the system checks for a Secondary RFC connection (of DIALOG type) and executes the task there. This is true for all standard transactional tasks (task type of STD_TRAN) as the system automatically executes the task on the Secondary RFC, if it is not in initial state. |
| System type | Depends on the purpose of the system; acceptable types are BW, ERP and CRM. |
| Warning |
|---|
If central system is running in, for example, German language, RFC language is not set and satellite system doesn't have German language support installed, now, if the RFC connection tries to use German language connection to satellite, the connection fails and it looks like the system is not responding. The solution is to force the language existing on satellite in RFC connection settings. |
...