Xtract QV - In-Memory BI with QlikView / Qlik Sense and SAP Data
"The decision to use Xtract QV was an instant hit, which you probably cannot expect too often in the IT world."
Christian Mühlthaler, IT Manager, Kardinal Schwarzenberg´sches Krankenhaus BetriebsgesmbH
On this page you will find an overview of the extraction types for SAP ERP. Please note that the access of Business Content extractors is described on the page DeltaQ.
Xtract QV Table
Using the Xtract QV Table component you can extract data from SAP tables and views. It is also possible to process WHERE statements to restrict the data to the user's needs. Of course, dynamic SQL statements involving variables are also supported.
- Data processing in packets to handle large amounts of data
- Asynchronous processing of data packets
- Variables for dynamic WHERE statements
- Type safety and full meta data support directly from SAP’s data dictionary
- No significant effect on the production system
The screenshot below shows the table dialog in the foreground. In the background you see the designer workbench with other extractions, which are created in the repository.
Xtract QV Query
SAP queries are popular data suppliers because tables can be joined on the SAP side without developer access. With Xtract QV Query, you can make your SAP queries directly available in QlikView. With a graphical user interface and full metadata support, the result is available for further processing within seconds.
- Table joins without SAP developer access
- Dynamic adjustment of the selection and variant through variables
- Type reliability thanks to meta data support
As with every SAP query, variants can also be used here. Alternatively or in addition, it is also possible to fill the selection screen with your own selection values. The variant and all selection parameters can be dynamically entered via variables. The screenshot shows the query dialog in SAP and the Xtract QV Designer’s Query Form.
Xtract QV BAPI
With the Xtract QV BAPI component you can access data from BAPIs and RFC function modules and directly use the output in QlikView. Scalar import and export parameters are read or stored from static values or variables. One or more tables can be transformed into a data stream. The screenshot shows the function module SD_RFC_CUSTOMER_GET that returns a list of customers by a specified search pattern. The search pattern is not set directly but dynamically via a variable in the QlikView script.
Xtract QV Report
The Xtract QV Report component allows you to use existing ABAP reports or ABAP programs as data sources within the QlikView script. This technique is often used in the area of FI/CO reporting. In many cases, a comprehensive pool of such reports has been accumulated over the years and simply cannot be replaced or reengineered. This ensures the highest level of investment protection when migrating to QlikView: Existing reports and their business process logic do not require any complex reverse engineering, and can continue to be used with Xtract QV Report.
The screenshot below shows the component in the layout preview. The input values (select options) are filled with values (variables if necessary). With the help of a graphical tool, the report output is split up into columns that generate the query output for further processing.
- Use of variants is possible (even dynamic per variable)
- Even complex reports based on an ALV grid can be generated
- Extremely long running reports are supported by asynchronous techniques (no RFC timeout)
- Automatic column detection possible
The Xtract QV DeltaQ component forms the top class of the BI components for SAP access by QlikView. With its help, the Extractor API in SAP ERP can be addressed and in such, the functionality with which BW systems also secure their data supply from the production system can be used.
- Real transaction-secure delta transfer of data
- Support of all master and transaction data including own generic extractors
- No installation in SAP required
- All business contents are available immediately even though no application-specific knowledge (e.g. about the tables’ structure) is required
The following screenshot shows the editor for the data source 2LIS_12_VCITM. It provides the delivery items. Three extraction modes are available: "Full" for a complete extraction (without delta); "Delta Init" for a delta initialization; "Delta" for the real delta update that is done via the ERP delta queue (transaction RSA7).
Xtract QV BW Cubes
Xtract QV BW Cube is a component to access the MDX engine of SAP BW, with which BEx queries can be extracted into QlikView. The dimensions, key figures and attributes to be transferred can simply be dragged and dropped into the query output. This turns complex, multidimensional data structures into relational data that is easy to manage.
- Support of BW variables (even complex selection criteria)
- Dynamic filtering through variables
- Value output can be adjusted as formatted or non-formatted (e.g. for scaling factors)
- Packaging function for large amounts of data
The image below shows the data source editor for a demo cube.
Xtract QV OHS
Compared to traditional BW extraction via the OLAP API, the Open Hub Services (OHS) were developed by SAP to make the extraction of BW data available for further processing instead of just pure reporting.
The Xtract QV OHS component supports all of the possibilities inherent to OHS extraction:
- Extremely large data volumes through packaging and asynchronous background processes
- Delta extracts
- Not just cubes, but also InfoObjects, ODS objects, texts etc.
- Extraction definition with the help of InfoSpokes (BW 3.5) or data transfer processes (BI 7.0)
The following screenshot shows the editor at design time. Different modes are supported (e.g. triggering of a process chain for extraction). In the background you see the Open Hub Monitor in SAP.
Xtract QV Hierarchy
Open Hub Services do not support extraction from BW hierarchies. Due to this limitation, the Xtract QV Hierarchy component was developed. It makes it possible to extract all hierarchy types from the BW system.
Additional optional features can be activated to perform other functions, for example, extracting description texts or removing leading zeroes from the data. Xtract QV Hierarchy supports parent/child and natural representation.
The screenshots below show the hierarchy in SAP and the Xtract QV component at the design time.
- Based on SAP-certified technology*
- Minimal to zero modification in your SAP system
- Very fast installation and configuration
- Fast, simple & user-friendly; programming knowledge not necessary
- Cross-module and module independent
- Business logic is available
- Robust, standardized process for incremental loads (Delta logic)
- Central security concept
- Central process monitoring for complete control of SAP access
- Cost savings through optimal integration, no friction losses
*Our SAP certified product ERPConnect provides the kernel for all our products and is responsible for the connection to each SAP system.
If you can't find an answer here, please contact us at email@example.com.
Is Xtract QV certified by SAP?
Xtract QV is based on our SAP certified product ERPConnect.
Which SAP and QlikView releases are supported?
SAP supported releases by extract type:
|Table||As of release 4.0B|
|Query||As of release 4.0B|
|BAPI||As of release 4.0B|
|BW Cube||As of BW 3.1|
|Hierarchy||As of BW 3.1|
|OHS||As of BW 3.5|
|DeltaQ||As of release 4.6A|
All versions from QlikView 8 and Qlik Sense 1 are supported.
What about license fees?
Xtract QV is licensed per server.
What about maintenance?
All licenses include six months of maintenance. After this period the maintenance can be extended for 20% of the list price per year. The maintenance service covers phone and email support, as well as all updates throughout the maintenance period.
Do you offer consulting services for SAP integration?
Yes. We provide the consulting services that suit your needs, from an introductory workshop up to a complete interface solution. Please contact us at firstname.lastname@example.org for further information.