Skip to main content

SAP Systems

Note

You can create as many SAP System Connections as you want. However, to use a SAP System Connection in a Task you need to register it. It depends on your license how many SAP System Connections you can register and how many slots each Connection can use.

Depending on what settings you choose for a few options, other sections may change. To avoid confusion, we'll describe every setting here on their own, without the description on what other sections change.

Overview​

In the overview you can see all SAP System Connections that currently exist. You can search for a specific Connection, adjust the column selection or create a new SAP System Connection with the button + System.


Creation​

First, enter a name for the new SAP System connection. Afterwards, go through every section to insert the details. Every section will be described below.

Communication Type​

You can choose between RFC Function Call and HTTP Request.

For the RFC Function Call, you'll need to install the RFC function module on your SAP System. Please find all information about it in this article.

To use the HTTP Request you need an Endpoint URL.

SAP Solution​

You can choose between a connection to an ECC System and a S/4HANA System.

Connection​

Server Type

  • Application Server: SID, Application Server, Instance Number, optionally SAProuter
  • Load Balancing: SID, Message Server, Group, optionally SAProuter

Payload Format

  • Web Service: Endpoint URL
  • Process Integration: Endpoint URL

Authentication​

Username and Password

  • Client
  • Language
  • Username
  • Password

SNC with SSO

  • Client
  • Language
  • Partner Name: you find the partner name in the transaction SU01 for the corresponding user - select the SNC tab and you find the value of the partner name in the field SNC name
  • My Name (optional)
  • Quality of Protection: Authentication, Integrity, Privacy, Maximum Available
  • SNC Mechanism: Kerberos, NTLM, Individual (SNC Library Path necessary)
    • to find this information go to SAP Logon > right-click on the Connection > Properties > Network tab > here you find this information

SNC without SSO

  • Client
  • Language
  • Partner Name: you find the partner name in the transaction SU01 for the corresponding user - select the SNC tab and you find the value of the partner name in the field SNC name
  • My Name (optional)
  • Quality of Protection: Authentication, Integrity, Privacy, Maximum Available
  • SNC Mechanism: Kerberos, NTLM, Individual (SNC Library Path necessary)
    • to find this information go to SAP Logon > right-click on the Connection > Properties > Network tab > here you find this information

RFC Configuration​

RFC Configuration Type

  • Certified: SAP certified function module
  • Legacy (Extended): newer version of the function module based on Z_RFC_READ_TABLE with support for up to 8,000 characters per data record
  • Legacy (Small): smaller version of the legacy function module based on Z_RFC_READ_TABLE with a limit of 2000 characters per data record

RFC Function

  • /DABEXP/RFC_SAPCONNECTOR: default, latest function module
  • Z_RFC_READ_TABLE: old version of the function module
  • Custom: enter the name of the function module if it has been renamed

Settings​

Available Data Masking - only the selected options are available to the User when creating a Task

  • None
  • Anonymize
  • Pseudonymize
Important

Limit dependency batch size and increasing the number of System Slots can lead to performance problems in your SAP System.

Maximum parallel extractions - the maximum number of concurrent Connections to this SAP System

Batch Size (Rows per request) - can be adjusted in stacks of 15.000 rows > Higher values might improve extraction performance but also increase resource consumption.

Dynamic batch Size - attempts to dynamically determine a optional batch size for table extractions based on the column selection. Might improve extraction performance. The value is calcualted based on the configured batch size.

Limit dependency batch Size - enable this option if your SAP System is using MaxDB and you have trouble extracting dependency tables.

Test download table (optional) - When testing the connection to the SAP system, dab Nexus attempts to access the table T000 by default, falling back to T001 if T000 doesn't work. If neither table is accessible due to restrictive permissions, you can set a different table to use for testing here.

Permissions​

Note

If you don't select any Teams or Users, all Users of dab Nexus can use this SAP System Connection. If you select one or more Teams or Users, only these can use the SAP System Connection.

Test Connection​

If the connection test fails, you'll get possible solutions. You can also see more details about the possible issue.


Registration​

Note

When a SAP System is registered in dab Nexus, it occupies one licence slot. When you delete a registered SAP System Connection, this slot is still occupied. But you can create the exact same SAP System Connection again and it will use the license slot, that was already assigned.

The number of SAP systems that can be registered can be found in Settings > Licence & Support in the SAP Configuration section. This shows how many SAP systems are already registered and the maximum number that can be registered.

To use a SAP System Connection in a Task, you have to register it.

To register a SAP System Connection go to Settings > SAP Systems > click on the three dots on the right side of the SAP System Connection you want to register and click on Register.


Edit​

You can adjust an existing SAP System Connection in certain ways.

But some settings can't be changed afterwards:

  • Communication Type
  • Connection

Deletion​

Important

The deletion of a SAP System Connection can affect active (scheduled) Tasks and may cause them to fail. This deletion cannot be undone.