SAP integration with universal destination environments

Yes, Xtract Universal is certified by SAP. It is based on our SAP certified product ERPConnect.

For detailed requirements, please have a look at our HelpCenter.

Xtract Universal is licensed on a per-server basis. This means that one license will not apply to multiple servers. For example, if a customer would like to install this tool on both a production and non-production environment, they need to license it on each of these environments. Every additional destination add-on will need to have its own license.

Yes, we provide SAP integration consulting services: Both single-day workshops and complete interface re-vamps. If you are interested in participating, please contact us at info@theobald-software.com.

Productive or non-productive, every server on which you are going to install our software has to be licensed. We generally recommend maintaining at least two independent servers. This allows you to install updates and new features, then apply them to the larger collection of servers.

Many different factors can affect how well your systems function: From processing mistakes and the implementation of new features, to differences in license versions/updates. This could have serious consequences, especially in a productive environment. Therefore, we strongly recommend the implementation of a non-productive server (in addition to your productive server) in order not to endanger the stability of the productive environment.

With our Table CDC component (Change Date Capture), you can track data and changes in your SAP system in a timely manner and transfer them to a third-party system. This allows you to implement enterprise-wide data integration in near real-time.

For more information on the functionality of the Table CDC component and how to use it in Xtract Universal, please refer to our Online Help.

Reliable, high-performance extraction of SAP tables (transparent tables, cluster tables, and views) is easier than ever before thanks to the Table component.

This component comes with our custom ABAP package for table extraction but also supports standard SAP function modules. What´s more, joining SAP tables prior to extraction via Open SQL statement is also possible. This replaces the need for manually creating views or SAP queries on the SAP side.

This component is our champion when it comes to mapping data or changes in your SAP system in near real time and as easily as possible. Data from different data sources is integrated to consolidate all changes in one central system. Unlike a full data load, where all records in a table are transferred from the source to the target database, Table CDC captures only the changes to the data since the last load. This reduces the amount of data that needs to be transferred, resulting in faster and more efficient transfers. This ensures that you always have access to the latest and most up-to-date data, saving resources and time.

By incrementally capturing data changes, CDC also enables faster replication of data between different databases or systems. When only the changed data needs to be transferred, rather than the entire table, data changes can be updated in other systems in near real-time.

These components are the crème de la crème when it comes to extracting data from SAP. With the help of the DeltaQ component, users can extract what are known as SAP DataSources. The main benefit of DataSources is the integrated mechanism for incremental data extraction — a function also employed by SAP BW.

DeltaQ and ODP enable the use of DataSources and thus eliminate the need for an SAP BW. The ODP component is Theobald Software’s response to the new SAP ODP extraction types. This component can also be used to extract SAP DataSources, as well as CDS views, BW/4HANA objects, and other data sources.

With the BAPI component, it is possible to call BAPIs and RFC function modules. At the same time, the component can be used as both the data source and—depending on the Xtract product—the target (data write-back). Users can extract or populate the BAPI’s import/export and table parameters.

This component makes it possible to use ABAP reports as a data source. This guarantees the extraction and thus continued use of existing, customer-specific ABAP reports or of standard reports provided by SAP. Users can simply adopt existing reports and their respective business logic instead of wasting time to recreate them outside of SAP.

The Query component lets users extract SAP ERP queries right from the SAP system. There is no need to tediously recreate existing queries and their respective business logic outside of SAP, because you can simply continue using them instead.

The Hierarchy component makes it possible to extract hierarchies from an SAP BW system. At the same time, this component gives users the option to extract the data in its original parent/child format. The hierarchies can also be broken up, however, and the individual hierarchy levels extracted as column headers in a flat table.

Through Open Hub Services (OHS), SAP provides an extraction method for a range of BW source objects. OHS is a particularly interesting choice when it comes to exporting mass data from SAP BW and provides an integrated delta mechanism when using SAP DTPs. Theobald Software supports the OHS component for BW/4 HANA as well.

The BW Cube component implements SAP’s OLAP BAPI interface (MDX) as well as the native BICS interface. It is therefore possible to extract traditional BW objects, such as BW or BEx queries, cubes, and MultiProvider. At the same time, the component supports both the new HANA-based BW objects and the objects of an S/4HANA embedded BW. The BW Cube component supports BEx variables and dimension filtering, thus enabling the extraction of large amounts of data with a packetizing and slicing function.