To create a connection to your system, follow these steps:

  1. Navigate to Settings inline-svg-1 > Data Ingestion > Connections.
  2. In the top-right corner, click New connection, find your system, and click Connect.

General configuration

In the general connection configuration step:

  1. Name your connection for easier identification in Dawiso. Use a unique and descriptive name like the combination of the server name and your local environment naming (e.g., server1_prod).
  2. Provide a description (purpose of the connection).
  3. Select a Connection type.
    • Shared: Source is accessible from the public internet and you can share your credentials with Dawiso.
    • Private: Source is not accessible from the public internet and you cannot share your credentials with Dawiso. For more information, see the Create a private connection article.
  4. Click Next.

Server configuration

In the host configuration step, provide the following information. Your SAP Basis team will recognize all of it: it is the same set used for any RFC connection, and it appears on every SAP GUI logon entry.

  1. Application Server Host: host name or IP address of the SAP application server, e.g. bwprod01.example.com.
  2. System Number: the two-digit SAP system number, e.g. 01.
  3. Client: the SAP client (mandant) holding the BW metadata to catalogue, e.g. 800.
  4. Language: the logon language, e.g. EN. It is also Dawiso’s first choice where an object’s texts exist in several languages — where they do not, Dawiso falls back to English, then German, then whatever the system holds, so objects maintained only in a local language still get their names.
Warning

There is no port setting. The RFC gateway port is derived from the system number — 33 followed by the two digits. System number 01 means port 3301, 00 means 3300. If you were given a port instead of a system number, take the last two digits.

Check the system number carefully: it is the single most common cause of a failed first connection. A host that is reachable but answers on a different system number fails with RFC_COMMUNICATION_FAILURE rather than a clear “wrong system number” message.

Authentication

Provide the technical SAP user created in Prepare for SAP BW integration:

  1. User: the technical user name. Use a System or Communications Data user rather than a personal account. A personal account consumes a named-user license, and its password expiry silently stops the scan.
  2. Password: the user’s password. Stored encrypted.

The user needs display-only authorization: S_RFC to call RFC_PING and RFC_READ_TABLE, and S_TABU_NAM to read the BW metadata tables. No write access and no S_DEVELOP are required.

Warning

Load-balanced logon through the SAP message server (a logon group rather than a named application server) is not currently supported. See Prepare for SAP BW integration.

Optional and additional settings

Configure Optional and Additional Settings for your connection. These settings are fully optional:

  • Optional settings: Specify options supported by the provider in JSON format.
  • Additional Settings: Recommended to leave empty unless our Dawiso support team suggests otherwise. Here, you can add a JSON formatted list of additional settings for troubleshooting or advanced connection configuration.

When adding optional settings, make sure the value is in a valid JSON.

Test and save connection

If your connection is shared, click on Test connection and wait for a few seconds.

  • If successful, there will be a green checkmark next to the button.
  • In case of failure, there will be a red error icon. Hover over it for a detailed error message. For more information, see the troubleshooting section. You are still able to save your connection.
Tip

If your connection is private and you used dummy credentials, the connection test will fail.

Finally, Save the connection and proceed to the next step: using the connection to create a data source. During this process, you will specify what metadata to ingest.

The connection test performs an RFC_PING followed by a trial read of the RSDAREA table, so both network and authorization problems surface immediately.

MessageWhat to check
SAP NW RFC SDK not found at …, Unable to load DLL 'sapnwrfc', or a missing MSVCP140.dllThe SAP NetWeaver RFC SDK libraries are missing from the runtime’s providers/sap-bw/ folder, or the Microsoft Visual C++ Redistributable is not installed
RFC_COMMUNICATION_FAILUREWrong host or system number, or the gateway port is blocked by a firewall
RFC_LOGON_FAILUREWrong user, password or client
An error immediately after logon, while reading RSDAREAThe user is missing table display authorization