A system is the satellite system in your SAP landscape including the connections to it
Systems may be added via the Quick Setup Menu in Step "System" or via the "Master data, System, New" menu item:
Quick setup and Master data menu item: System
In this example, a double stack type system will be configured. This brings up the following screen:
Again, all fields marked with a "*" are mandatory and must be filled before the data can be saved. After the data has been supplied, press the "Save" button in order to continue with the next screen.
After saving the System header data, a wizard containing the following steps will be started:
Wizard for creating the System connections
In this first screen the connection data to the Central Instance (FQDN or Fully Qualified hostname) now known as Primary Application Server) must be supplied. This includes the Central Instance hostname (, instance number, number of the Productive client, the SAP user name and password. If the system allows it, you may set the "Trusted system" flag and additionally SNC settings for encryption can be set by setting the "SNC active" flag and filling the "SNC partner" field.
You may also select an existing RFC destination in order to copy its: hostname, instance number and client to this screen.
When the Next button is pressed, the wizard will contact the System and determine what available clients exist.
RFC connections to Clients
The client data of the satellite system is retrieved and now the relevant SAP users in and their passwords may be supplied for the other clients. Although this is not mandatory, ERP-SEC recommends to supply this data in order to get a better Scan result. When done, press the "Next" button.
ABAP Database connection
In this screen, the ABAP database connection data must be supplied. The database hostname provided must be fully qualified (including domain name). Supply the database user and password created earlier. If the database port has a default port number, then you may skip this field
For the JAVA connection, you may supply the JAVA user created earlier. The default JAVA port will be taken if the port number is left empty.
Optionally you may supply a UserID and password for the JAVA database schema.
JAVA database connection
The connections to SAP Control consists of 2 steps, first the connection to the primary application server must be set up. Supply the fully qualified hostname or IP-adress of the server on which the SAP Instance is located.
Primary SAP control connection
Then the wizard will check whether connections to other instances must be set up. When these are located on the same host as the primary application server, the same user as in the previous step can be used.
SAP Control connections to other instances
After pressing Next, an overview of all the connections that will be created, is given.
System connection creation
After confirmation by pressing the Save button, the system connections will be created. This may take approx. 1 to 2 minutes, depending on the amount of connections required.
At the end of all the steps, you will see an overview of the System header data and the different connections that were generated.
You may re-check the connections by pressing on the “Check all connections” button:
Checking the System connections
In order to add a layer of security to the used SAP RFC Abap connection, it is advised to use the S_ICF object to specify any authorization value that is set in SM59 for the created RFC's. See the SAP documentation for more information.