1. QlikView for use with SAP Netweaver Version 5.8 New Features

2. Agenda Extractor Connector – additional extraction method
Query Connector
Report Connector
The presentation covers additions to the SAP Connector for use with SAP Netweaver including enhancements to the Report/Query/Extractor connectors

3. SAP Extractor Connector
SAP Connector Ver. 5.80
Focus area of 5.80
The main area of development is 5.8 is the development of an additional method for the extractor connector to utilise tRFC

4. SAP Extractor Connector
Purpose:
Version 5.8 of the SAP connector introduces an additional method for the Extractor connector primarily to extend the use of this type of connectivity. The vision is to load data faster and in parallel without any restriction of the number of characters in the data source.
Advantages:
No restiction on the number of characters in the data source
Load of several data sources on the same logical system during the same timeframe now possible
The data package will be queued in SAP and wait for free processes
Method:
By using the tRfc method which is a standard method in SAP all of the above is possible and this is normally used when loading ERP data into BW.

5. Transactional RFC (tRFC) method
Transactional RFC(tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system does not need to be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls
are executed in the order in which they are called
are executed in the same program context in the target system
run as a single transaction: they are either committed or rolled back as a unit.
In the SAP ERP system, there are pre-defined data sources available to use for transferring data to SAP BI systems.

6. SAP Extractor Connector – SAP Setup
One method per datasource
Same activation procedure as with IDoc

7. SAP Extractor Connector – Parallel Extractions
New Service installed MUST be started to use the Extractor connector
Parallel tRFC process
QVS
QVB
SrvService
An example of a SAP Clustered environment – Note transports only loaded onto the Master SAP system
Publisher has 2 SAP extractor (tRFC) tasks to execute simultaneously
New SAP Service introduced to marshall multiple requests bi-directional
Must be installed and started on one machine to use the extractor connector from 5.80 onwards
QlikView documents updated and available to multiple clients as required
SAP Clustered environment

8. SAP Extractor Connector – Additional Service
To cater for the option to execute parallel loads an additional component has been introduced which can be run as an exe or a service
To Install the service run SrvService_Console.bat and select input option 2 and start the service
The port option is set to 8680 by default, but can be changed using input option 4.
Note: It’s only possible to have one service running to avoid mismatch

9. SAP Extractor Connector – Host Connection
New Network Server Host and Port is the location of the preinstalled service/exe file with a default port of 8680

10. SAP Extractor Connector – tRFC methods in script
Alternate parameter now available in the generated script indicating the extraction type is tRFC

11. SAP Query Connector
Now possible to execute queries with variants and enter selection parameters
Multiple field filters possible
Include and exclude with <,>,<>,=,<=,>= and between supported
We can now handle long field names up to 70 characters (max 28 before)
Each job started is now logged in the database table /QTQVC/STATUS.

12. SAP Report Connector
Now possible to execute reports with custom variants
Multiple field filters possible
Include and exclude with <,>,<>,=,<=,>= and between supported

13. SAP Extractor Connector - Q&A
Do I need to install and start the new service or exe file to work with the extractor connector with 5.80?
Yes and must only be actively running on ONE machine
Does the parallel load feature work with both Idoc and tRFC extraction methods?
No only tRFC
Can I use this new extractor functionality in 5.80 with BASIS version 6.10 and 6.20?
No only supported with 6.40 and above for 6.10 and 6.20 use the 5.7 version of the connector, only the following connectors are supported on BASIS 6.10 and 6.20 with the 5.80 release:
SQL Connector
Query connector
Report Connector
(OLAP/DSO connector)

14. SAP Extractor Connector - Q&A cont.
Can I activate an extractor with both the Idoc and tRFC methods?
No only one method of activation is allowed per SAP instance
In the SAP Extractor login screen what are the Network Server Host and Port fields for?
The Server Host is for the IP address/server name of where the new service is registered/active and the default port is 8680