The following section shows how to create an SAP connection using the Xtract for Alteryx UI.
An SAP connection is required to use any Xtract for Alteryx component.

Note: Creating SAP connections using the Xtract for Alteryx UI is deprecated.
The recommended method for creating SAP connections involves the use of Alteryx’ Data Connection Manager and requires an Alteryx Designer version >= 2022.3. For more information, see Online Help: SAP-Connection.

Creating an SAP Connection #

  1. Drag&drop an Xtract for Alteryx component from the Alteryx Designer tool box onto the canvas (1). The configuration window of the component opens.
  2. Click [New] (2) to create a new connection. The window “SAP Connection Details” opens.
  3. Fill out the connection details to establish an SAP connection.
    The connection details consist of four subsections: System, Client and Language, Authentication and Miscallaneous.
    Connection details
  4. Click [Test Connection] to test the SAP connection. A confirmation window opens.
    Connection test
  5. Click [OK] to save the SAP connection.

The SAP connection is now available for selection in the configuration window (2).
To edit the SAP connection, select the SAP connection from the dropdown list (2) and click [Edit].

Tip: Values to fill out the connection details can be found in the SAP Logon Pad in the Properties or acquired from SAP Basis team.

Note: The connection details of an SAP connection are stored in a JSON file in the following directory:
C:\Users\<UserName>\AppData\Roaming\Theobald Software\Xtract for Alteryx\Connections\<SAPSourceName>.json

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)
    • Sys. No.:: a two-digit number between 00 and 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)

For more information, see SAP Help: Load Balancing.

Access 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.
Example: If the application server is “hamlet” and the router string is /H/, set the host property to /H/

For more information, see SAP Help: SAP-Router.

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:

  • SNC (1): encrypted connection between Xtract for Alteryx and SAP with username and password. For more information, see SAP Help: Secure Network Communications (SNC).
  • Plain (2): SAP username and password (system or dialogue user)
  • SAP Log On Ticket (3): uses SAP Logon-Tickets in place of user credentials. This connection is not encrypted.

Connection details

SNC (1)

  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 that runs Xtract for Alteryx.
  2. When using SNC, make sure to enter the complete path of the library in the field SNC library e.g., C:\SNC\gx64krb5.dll.
  3. Enter the SAP Partner Name configured for the SAP application server e.g., p:SAPserviceERP/do_not_care@THEOBALD.LOCAL.

For more information on SNC, see the knowledge base article Enabling Secure Network Communication (SNC) via X.509 certificate.

Plain (2)

Enter your SAP username and password.

SAP Log On Ticket (3)

Enter the URL of an Application Server Java (AS Java) that is configured to issue logon tickets in the field Ticket issuer.
For more information, see SAP Documentation: Configuring the AS Java to Issue Logon Tickets.

Miscellaneous #

Select an RFC library. The following RFC libraries are supported:

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

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. For more information on SAP libraries, see SAP Help: RFC Libraries.

SAP does not support the librfc32.dll anymore.

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

Trace Directory (Debug Logging)
You can log debug information and save it locally. In the field Trace directory enter a local path to a folder, where you want to save the debug information. For more information, see the knowledge base article How to activate tracing for Xtract Products.
Clear the Trace Directory field when it is not needed.

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.