Xtract QV - SAP and QlikView seamless Integration 

The following image shows the Xtract QV architecture. Xtract QV essentially consists of two components: a server component and a designer. The server component is responsible for the actual extraction. QlikView Communicates with the Server component, and these in turn with SAP. Since the server component has no GUI, you use the Xtract QV designer for the design and configuration of the extractions.

Xtract QV - Access to SAP BW/BI from QlikView

Auf den folgenden Seite finden Sie einen Überblick über Extraktionsmöglichkeiten aus SAP BW bzw. SAP BI. Diese Architektur ermöglicht es Ihnen, QlikView als einen Data Mart für SAP BW / BI zu nutzen, um so elegant vor allem Performance- und Architektur-Schwierigkeiten des BWs auszugleichen.

BW Cubes / BW Queries

Xtract QV BW Cube is a component to access the MDX engine of SAP BW / BI. It is so easily possible to load BEX queries in QlikView. The dimensions, key figures and attributes to be transferred can simply be dragged and dropped into the query output. This turns complex, cubic data structures into relational data that are easy to handle.

• Support of BW variables (even complex selection criteria)
• Dynamic restrictions 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.

Open Hub Services

Compared to traditional BW extraction via the OLAP API, the Open Hub Services (OHS) were developed by SAP so that the extraction of BW data could be made available for further electronic 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.

SAP BI Hierarchies

Open Hub Services do not support extraction from BW hierarchies. Due to this, the Xtract QV Hierarchy component was developed. It makes it possible to extract all hierarchy types from the BW.
The screenshots below show the hierarchy in SAP and the Xtract QV component at the design time. If necessary, hierarchy texts can also be read in.

Xtract QV DeltaQ - Delta-Management und Business Content

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 R/3 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 modi 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 R/3 delta queue (transaction RSA7).

Xtract QV - Access to SAP R/3 and SAP ERP from QlikView

On the following page you will find an overview of the extraction types from SAP R/3 and SAP ERP.

Xtract QV Table

Using Xtract QV's table component you can extract data from SAP tables and view. 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 extraction can be processed in packets to handle large amounts of data
• Asynchronous processing of data packets
• Variables for dynamic WHERE statements
• Type safety and meta data support by 100% from SAP’s data dictionary
• No significant effect on the production system

The screenshort 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.

SAP Queries

SAP queries are so popular as data suppliers because tables can be joined on the SAP end without any developer authorization. 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.
As with every SAP query, variants can also be applied 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.

BAPIs and Function Modules

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 variables. You can link one or many outbound tables with a pipeline to access them.
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.

ABAP Reports

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 a lot of cases, a comprehensive pool of such reports has accumulated over the years and simply cannot be replaced or reengineered
With the Xtract QV Report component you can protect your investments because existing logic doesn’t have to be reengineered—it can simply be reused.
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 then 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)