Creating an SAP connection #

Warning! Missing Authorization To establish a connection to SAP the access to general authority objects (RFC) must be available. Make sure to gain access to the general authority objects. For more information, see the knowledge base article on SAP User Rights.

  1. In the main window of the Designer, navigate to the menu bar and select Server > Manage Sources. BC-Create-Connection-1 The window “Manage Sources” opens.

  2. Click [Add]. The window “SAP Source Details” opens.
  3. Enter a name of your added connection.

Connection Details #

The tab General contains the connection details and is divided into four subsections:

Fill out the connection details to establish an SAP connection.

Tip: Values to fill out the fields can be found in the SAP logon pad in the Properties or acquired from SAP Basis team.

Click [Test Connection] (1) to test the successful connection. The confirmation window opens.
The SAP connection is set up successfully. XU-Create-Connection-3

System #

There are two possibilities to connect to an SAP source system:

  • Use a Single Application Server
    • Host: host name or IP address of the application server (Property Host)
    • Instance No: a two-digit number between 00 und 99 (Property SystemNumber)
  • Use a Load Balancing Server (message server)
    • Message Server: name or IP address of the message server (Property MessageServer)
    • Group: property LogonGroup, usually PUBLIC
    • SID: three-digit System ID (Property SID e.g., MSS) See also SAP online help: Load Balancing.

Accessing via SAP router

If you access the SAP source system (Application server or Message server) via an SAP router, set the router string before the host name.
If the application server is “hamlet” and the router string is /H/, set the host property to /H/

See also SAP online help: SAP-Router.

Tip: Values to fill out the forms can be found in the SAP logon pad in the Properties or acquired from SAP Basis team.

Client and Language #

  • Client - a three-digit number of the SAP client between 000 and 999, e.g., 800.
  • Language - the logon language for the SAP system, e.g., EN for English or DE for German.

Authentication #

The following authentication methods are supported:

  • Plain (1) - SAP username and password (system or dialogue user)
  • SNC (Secure Network Communication) (2) with username and password
  • SNC with SSO (Single Sign On) (3)

XU-Authentication You can additionally use SAP Log On Ticket for authentication (available only for several connectors, e.g., ERPConnect, ERPConnect Services, Xtract Universal and BOARD Connector).

Require SAP credentials to be explicitly supplied for execution (4)
Option available only when using Plain or SNC authentication method. SAP credentials entered in the User and Password fields are not applied. Instead, SAP credentials need to be provided via basic authentication when executing an extraction. Caching the result of extractions is inactive.

Xtract Universal only: See Power BI Connector or Alteryx destinations for possible examples.

Note: The option “Require SAP credentials to be explicitly supplied for execution” requires extractions to be called via HTTPS - unrestricted.


  1. Check the SAP parameter snc/gssapi_lib to determine, which library is used for encryption in your SAP system. Your SAP basis has to import and configure the same library on the application server and on the machine with installed Xtract Universal or BOARD Connector.
  2. In the SNC library field, fill in the complete path to the library location e.g., C:\Program Files\SAP\FrontEnd\SecureLogin\lib\sapcrypto.dll.
  3. Fill in the SAP Partner Name configured for the SAP application server e.g., p:SAPserviceERP/do_not_care@THEOBALD.LOCAL.

For additional details see the knowledge base article Enabling Secure Network Communication (SNC) via X.509 certificate.

When working with Kerberos library, follow the steps described in SSO with Kerberos SNC.

Miscellaneous #

Select a library and optionally define a trace directory for debug logging.

RFC libraries

The RFC API (Remote Function Call) allows to establish an RFC connection to an SAP system from an external system that communicates as Client or Server with the SAP system.
There are two options for using RFC libraries:

  • Use classic RFC library (librfc32.dll)
  • Use NetWeaver RFC libraries (sapnwrfc.dll)

See additional information on SAP libraries on the SAP Help Site - RFC Libraries.

SAP has stopped supporting librfc32.dll.

Note: When using the NetWeaver RFC library with DeltaQ or OHS extractions, the RFC destination in SM59 must be set to Unicode.

Trace Directory

You can log debug information and save it locally. Fill the Trace directory field with a local path to a folder, where you want to save the debug information.

Warning!: Increase of used hard drive memory
A big amount of information is collected when debug logging is activated. This can decrease the capacity of your hard drives dramatically. Activate the debug logging only when necessary e.g., upon request of the support team.

To Check the New SAP Connection #

  1. In the main window of the Designer, navigate to the menu bar and select the menu item Server > Manage Sources.
    The window “Manage Sources” opens.
  2. Check if created SAP connection is listed. XU-Create-Connection-4