Xtract QV—連接SAP和QlikView的完美工具

下面這幅圖顯示了XtractQV的結(jié)構(gòu)。XtractQV由兩部分構(gòu)成：服務(wù)器和設(shè)計(jì)器。服務(wù)器部分負(fù)責(zé)正真的數(shù)據(jù)提取。QlikView和服務(wù)器交流，服務(wù)器再和SAP交流，從而將QlikView和SAP連接起來(lái)。由于服務(wù)器沒(méi)有圖形用戶界面，所以只能通過(guò)設(shè)計(jì)器來(lái)控制和配置數(shù)據(jù)提取的過(guò)程。

Xtract QV –可連接 SAP BW/BI 和QlikView

下面您將看到SAP BW/BI的幾種提取數(shù)據(jù)方法。有了Xtract QV，您就可以在SAP BW/BI應(yīng)用程序中，將QlikView視為 DATA Mart。特別是在SAP BW中， Xtract QV的這種優(yōu)點(diǎn)更加明顯。

BW Cubes / BW Queries

Xtract QV BW Cube是一個(gè)連接SAP BW / BI中MDX引擎的配件。有了它，在QlikView中加載BEX查詢將會(huì)十分簡(jiǎn)單。要傳遞的數(shù)據(jù)大小，關(guān)鍵數(shù)據(jù)和特征參數(shù)都可以顯示在查詢結(jié)果中。這樣，復(fù)雜的多維數(shù)據(jù)結(jié)構(gòu)將被轉(zhuǎn)換為可控制的相關(guān)數(shù)據(jù)。

• 支持BW（商務(wù)信息倉(cāng)庫(kù)）變量（甚至是復(fù)雜的選擇準(zhǔn)則）。

• 動(dòng)態(tài)的變量限制。

• 輸出值可以被調(diào)節(jié)為有格式化或非格式化（比如對(duì)于縮放比例）。

• 可對(duì)大數(shù)據(jù)打包分組。

下圖顯示了一個(gè)數(shù)據(jù)源編輯器（多維數(shù)據(jù)集）。

Open Hub Services

相對(duì)于傳統(tǒng)BW提取數(shù)據(jù)（通過(guò)OLAP API）來(lái)說(shuō)，Open Hub Services（OHS）是一種進(jìn)步。有了OHS，BW數(shù)據(jù)提取過(guò)程可以不斷優(yōu)化，而不是簡(jiǎn)單地傳遞下去。

Xtract QV OHS支持所有的OHS過(guò)程：

• 通過(guò)打包分組和異步背景處理的方法來(lái)處理極大數(shù)據(jù)量。

• Delta提取。

• 不僅支持多維數(shù)據(jù)集，還支持InfoObjects, ODSObjects和文本文件。

• 通過(guò)InfoSpokes (BW 3.5) 或者數(shù)據(jù)傳遞過(guò)程(BI 7.0)來(lái)決定提取過(guò)程。

下圖是設(shè)計(jì)過(guò)程中的編輯器?？芍С侄喾N方法（比如觸發(fā)型的提取數(shù)據(jù)）。圖片的底面是SAP的Open Hub Monitor。

SAP BI體系

Open Hub Services不支持從BW結(jié)構(gòu)中提取數(shù)據(jù)，在這種情況下，Xtract QV Hierarchy孕育而生。有了Xtract QV Hierarchy，就可以從各種結(jié)構(gòu)的BW中提取數(shù)據(jù)。下面的截圖顯示了在設(shè)計(jì)時(shí)，SAP 和Xtract QV的層次結(jié)構(gòu)。如果有需要，也可以讀入體系文本。

Xtract QV DeltaQ—Delta 管理和商業(yè)信息

在連接SAP和QlikView的BI組件中，Xtract QV DeltaQ組件是一個(gè)高端產(chǎn)品。有了它，SAP R/3中的Extractor API的地址得以確定，而且也可以保證數(shù)據(jù)安全（數(shù)據(jù)是BW系統(tǒng)從產(chǎn)品系統(tǒng)中獲得）。

• 實(shí)時(shí)交易，保證數(shù)據(jù)傳輸?shù)陌踩?/p>

• 支持主要數(shù)據(jù)和交易數(shù)據(jù)，包括共同的數(shù)據(jù)提取器。

• 不需安裝在SAP中。

• 即使在沒(méi)有獲得特殊應(yīng)用程序的背景（比如目錄表的結(jié)構(gòu)）情況下，都可以即時(shí)得到所有商業(yè)信息。

下面的截圖顯示了2LIS_12_VCITM數(shù)據(jù)源編輯器。它提供傳遞功能?？墒褂萌N提取模式：“Full”是完全提取模式（不用delta）。“Delta Init”是delta初始化。“Delta”通過(guò)R/3 delta隊(duì)列，對(duì)delta進(jìn)行升級(jí)（交易R(shí)SA7）。

Xtract QV可連接QlikView和SAP R/3、SAP ERP

下面，將為您介紹從SAP R/3和SAP ERP中提取數(shù)據(jù)的幾種方式。

Xtract QV目錄

通過(guò)Xtract QV的目錄組件，你可以從SAP的目錄和瀏覽圖中提取數(shù)據(jù)。您也可以運(yùn)行WHERE語(yǔ)句來(lái)滿足用戶對(duì)數(shù)據(jù)提取的特殊要求。當(dāng)然，它也支持動(dòng)態(tài)結(jié)構(gòu)化（有特殊變量的）查詢語(yǔ)言。

• 可對(duì)大數(shù)據(jù)進(jìn)行分組打包處理。

• 異步處理數(shù)據(jù)包。

• 支持動(dòng)態(tài)WHERE語(yǔ)句變量。

• SAP的數(shù)據(jù)字典中支持安全類型和超數(shù)據(jù)。

• 對(duì)產(chǎn)品系統(tǒng)沒(méi)有明顯的影響。

在下面的截圖里，前景圖是目錄對(duì)話框，背景是在儲(chǔ)存庫(kù)中創(chuàng)建的其他提取數(shù)據(jù)工作室。

SAP查詢

由于目錄表無(wú)需任何認(rèn)證就可加入到SAP終端，SAP查詢?cè)跀?shù)據(jù)提供者中十分受歡迎。有了Xtract QV Query，您可以在QlikView中直接使用SAP查詢。有了圖形用戶界面和超數(shù)據(jù)支持，可以馬上處理查詢結(jié)果。 可以為您量身定做SAP查詢，您也可以在選擇屏幕上放置您的選擇。這些，都可以通過(guò)設(shè)置變量表來(lái)實(shí)現(xiàn)。

下面這張截圖顯示了SAP的查詢對(duì)話框和Xtract QV設(shè)計(jì)者的Query Form。

BAPI和功能模塊

有了Xtract QV BAPI組件，您可以從BAPI和RFC功能模塊中獲得數(shù)據(jù)，并直接使用QlikView的輸出。 標(biāo)量輸入和輸出參數(shù)都可在變量表中讀取，或者存儲(chǔ)在變量表中。通過(guò)一個(gè)連接管道，您可以連接一個(gè)或者多個(gè)輸出表。

下面的截圖顯示了SD_RFC_CUSTOMER_GET模塊，他通過(guò)一種特殊的查詢格式，顯示一系列用戶。這種查詢格式并不是固定的，它因QlikView腳本上的變量而改變。

ABAP Reports

有了Xtract QV Report組件，您可以將QlikView腳本中的ABAP報(bào)告和ABAP程序作為數(shù)據(jù)源。這個(gè)技術(shù)經(jīng)常用在FI/CO報(bào)表領(lǐng)域中。經(jīng)過(guò)這么多年的積累，這些報(bào)表早已堆積如山，不可能輕易地被取代或者調(diào)整。Xtract QV Report組件可以保護(hù)您的投資，因?yàn)椴挥萌〈F(xiàn)有的資源，只需循環(huán)使用。

下面這張截圖是這個(gè)組件的預(yù)覽版圖。輸入值（可選）顯示的是所有可用的變量。有了圖形工具的幫助，輸出的報(bào)告被分成多列，然后再生成查詢輸出。

• 可以改變參數(shù)（甚至改變每一個(gè)參數(shù)）。

• 可以生成基于ALV框架的復(fù)雜報(bào)表。

• 通過(guò)異步技術(shù)，可以支持很長(zhǎng)的運(yùn)行報(bào)表（不考慮RFC的時(shí)間限）。

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)