Necessary Components #

  • ADFv2
  • Azure-SSIS Integration Runtime (IR)

Setting up the Environment #

Setting up the necessary environment is documented in the Microsoft documentation below:

Once the environment is running, develop a simple SSIS package (NOT containing any Xtract IS components) and deploy and run the package on the Azure-SSIS IR.

If running the SSIS package is successful, proceed to setting up Xtract IS for Azure on the Azure-SSIS IR.

Note: By default Azure automatically updates the Microsoft integration runtime. To avoid possible compatibility issues with Xtract IS for Azure, disable automatic updates.

Supported SQL Server Integration Services (SSIS) Versions #

  • SQL Server Integration Services (SSIS) 2014 SP3 (until 2024-07-09)
  • SQL Server Integration Services (SSIS) 2016 SP2 (until 2026-07-14)
  • SQL Server Integration Services (SSIS) 2017 (until 2027-10-12)
  • SQL Server Integration Services (SSIS) 2019 (until 2030-01-08)
  • SQL Server Integration Services (SSIS) 2022

For development: SQL Server Data Tools are required to create SSIS packages. Use the related SSDT for the SQL Server Integration Services (SSIS) version you are using.
Check the Microsoft Help for details.

The version of the SQL Server Database used in SSIS to read or write data can differ from the version of the SQL Server Integration Services (SSIS) version, it means one can use e.g., SSIS version 2019 to write data to SQL Server Database version 2014.

Supported SAP Systems and Releases #

The following SAP Systems are supported:

  • All SAP ABAP based systems that provide RFC connectivity are supported. All communication with SAP is performed via the RFC protocol.
  • SAP ABAP Systems on any database (including HANA) are supported. The database used by the SAP system is irrelevant, because the integration occurs at SAP application server level.
  • SAP Systems running on Big Endian and Little Endian hardware are supported.
  • SAP industry solutions like IS-U, IS-R, etc. are supported.
  • SAP Releases 4.6C and newer are supported.
  • All operating systems are supported.

Examples: SAP S/4HANA, mySAP, SAP Application Server ABAP, Message Server, Router, Standalone Gateway, SAP Business Suite 7 (CRM, SRM, SCM etc.), SAP Business All in One, CAR, APO, PI, SAP BW 3.1 and later, SAP BW/BI 7.x, SAP ERP / ECC 5.0 / ECC 6.0 (including all EhPs), SAP R/3 Version 4.6C and later, SAP BW/4HANA and more.

Disclaimer: While SAP versions that are no longer supported by SAP still work with Theobald Software products, they are excluded from the Theobald Software support service.

Not supported SAP Systems #

The following SAP Systems are not supported:

  • SAP systems that don’t run on ABAP systems
  • SAP systems that don’t provide RFC connectivity.

Examples: SAP S/4HANA Cloud Public Edition, Business By Design, Business One, Business Objects, Sybase, Ariba, Success Factors, Concur

HANA Database #

You can use Operational Data Provisioning (ODP) to connect the SAP HANA database of an SAP ABAP source system. Communication is done via RFC. With the ODP context for SAP HANA (HANA) the following HANA View types are available for extracting:

  • Analysis Views
  • Calculation Views
  • Associated Attribute Views

Direct access to a HANA database without an SAP ABAP source system running on the corresponding HANA database is not supported.

Installation and Configuration on SAP #

Component SAP Release Requirements on the SAP system
Table Rel. > 4.6C Installation of a custom function module /THEO/READ_TABLE is recommended.
BAPI & Function Module Rel. > 4.6C No requirements. Note: Only remote-enabled functions are supported.
Query Rel. > 4.6C No requirements.
Report Rel. > 4.6C Installation of a custom function module Z_XTRACT_IS_REMOTE_REPORT is necessary.
BW Cube & InfoProvider Rel. > BW 3.1 No requirements.
BW Query Rel. > BW 3.1 No requirements. Note: “Allow External Access to this Query” option is active.
Hierarchy Rel. > BW 3.1 No requirements.
ODP SAP_BASIS >= 730, BW >= 7,3X No requirements.
DeltaQ Rel. > 4.6C Customizing required, see Customizing for DeltaQ.
OHS Rel. > BW 3.5 Customizing required, see Customizing for OHS in BW.
Table CDC SAP ECC 5.0 or above Installation of a custom function modules is necessary, see Table CDC Requirements.

For Information about the installation of the custom function modules and the SAP customizing, check the section SAP customizing.

SAP Authentication #

  • SAP user authentication (user name and password)
  • SAP authentication with Single Sign On (SSO) and kerberos
  • SAP Logon Ticket (via SAP Ticket Issuer) is also in some products available.
  • SAP system or dialog user with appropriate authority objects.

Ports #

Following ports have to be opened depending on the SAP system, where nn is the instance number of the SAP system (e.g. 00 or 99).

  • SAP Application Server: Port 33nn
  • SAP Message Server (Load Balancing): Port 36nn
  • Secure Network Communications (SNC): Port 48nn
  • SAP Router: Port 3299

SAP Licenses #

Additional SAP licenses might be required for extracting data from SAP. Contact SAP to verify these requirements.

Operating Systems #

  • Windows 11
  • Windows Server 2022 (until 2031-10-14)
  • Windows 10 (until 2025-10-14)
  • Windows Server 2019 (until 2029-01-09)
  • Windows Server 2016 (until 2027-01-12)

Other applications and frameworks #

.NET Framework 4.7.2 or higher. Download .NET Framework from the Microsoft website.

Hardware #


  • Minimum 4 GB.
    Depending on data volume, more memory may be required.

Disk space

  • 50 MB total for installation

32/64-Bit Environment

  • 32-Bit and 64-Bit operating systems