SAP integration with universal destination environments

Xtract Universal is based on our SAP certified product ERPConnect.

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

Xtract Universal is licensed per server. It is independent if our software will be installed on a productive or a non-productive server environment. In both cases a full license is required. Every destination Add-On needs to be licensed additonally.

Every license comes with six months of maintenance. Apart from technical support via phone or email, this also includes updates for all versions that are released within this period. After the six-month maintenance period is over, an additional year of maintenance can be purchased for 20% of the license fee. There is no right for updates after expiration of maintenance.

Yes. We provide the consulting you want and need. From a single-day workshop up to a complete interface solution. Please contact us at info@theobald-software.com.

Every server on which you are going to install our software has to be licensed. It does not matter whether this server environment is used productive or non-productive. From our experience, we generally recommend an architecture of at least two independent servers. The reason for this is concerning the installation of updates and new features relating to other solutions in the overall architecture. There are many different factors like the version of each individual solution which could affect the functionality. This could have serious consequences, especially in a productive environment. Therefore, we strongly recommend the implementation of a second non-productive server in order not to endanger the stability of the productive environment, especially in terms of installing updates and new features. We would also like to point out that there are no questions about the functionality of Theobald Software’s own solutions, but rather the whole architecture with all the influencing factors has to be taken into account.

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.

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.