Qlik view connector manual

©2012 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other
QlikTech products and services as well as their respective logos are trademarks or registered trademarks of QlikTech International AB. All other company names, products and services
used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice. This publication is for informational
purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech
products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting
any additional warranty.
QlikView Connector for Use with
SAP NetWeaver
Installation and Usage Guide
QlikView Connector Version: 5.70 IR, May 2012
www.qlikview.com

2
Table of Contents
1 About this Document.............................................................................................................6
2 Introduction ...........................................................................................................................7
3 Authorization Concept...........................................................................................................8
3.1 General...................................................................................................................................... 8
3.1.1 Authorization Concept........................................................................................................... 8
3.1.2 QlikView Predefined Authorization Roles.............................................................................. 9
4 QlikView SAP SQL Connector............................................................................................11
4.1 SAP System.............................................................................................................................. 11
4.1.1 Prerequisites........................................................................................................................ 11
4.1.2 Installing Transports............................................................................................................ 11
4.1.3 User Configuration for SAP BASIS System 6.10, 6.20, 6.40, and 7....................................... 12
4.1.4 Testing SQL Statements – /QTQVC/SQL.............................................................................. 13
4.2 Authorisation........................................................................................................................... 13
4.2.1 Table-based Access Control................................................................................................. 14
4.2.2 Row-based Access Control .................................................................................................. 15
4.3 QlikView SAP SQL Connector Client ........................................................................................ 18
4.3.1 Prerequisites........................................................................................................................ 18
4.3.2 Windows Folders................................................................................................................. 18
4.3.3 Installing SAP SQL Connector Client .................................................................................... 18
4.3.4 Using SAP SQL Connector.................................................................................................... 21
4.3.5 ScriptBuilder........................................................................................................................ 24
4.3.6 SQL SUBSELECT Syntax........................................................................................................ 25
4.3.7 SAP SQL Connector Log ....................................................................................................... 25
5 QlikView SAP OLAP Connector..........................................................................................27
5.1 SAP System.............................................................................................................................. 27
5.1.1 Prerequisites........................................................................................................................ 27
5.1.3 User Configuration .............................................................................................................. 27
5.2 QlikView SAP OLAP Connector Client...................................................................................... 29
5.2.1 Prerequisites........................................................................................................................ 29
5.2.2 Installing SAP OLAP Connector Client.................................................................................. 29
5.2.3 Accessing BEX Queries......................................................................................................... 30
5.2.4 Using SAP OLAP Connector ................................................................................................. 30
5.2.5 Defining Query .................................................................................................................... 32
5.2.6 Optimizing Query ................................................................................................................ 34
5.2.7 Delta Loads.......................................................................................................................... 36
6 QlikView SAP DSO/ODS Connector ..................................................................................37

3
6.1 SAP System.............................................................................................................................. 37
6.1.1 Prerequisites........................................................................................................................ 37
6.2 QlikView SAP DSO/ODS Connector Client ............................................................................... 38
6.2.1 Prerequisites........................................................................................................................ 38
6.2.2 Installing SAP DSO/ODS Connector Client........................................................................... 38
6.2.3 Using SAP DSO/ODS Connector........................................................................................... 38
6.2.4 Defining Query .................................................................................................................... 40
7 QlikView SAP Query Connector .........................................................................................43
7.1 SAP System.............................................................................................................................. 43
7.1.1 Prerequisites........................................................................................................................ 43
7.2 QlikView SAP Query Connector Client..................................................................................... 45
7.2.1 Prerequisites........................................................................................................................ 45
7.2.2 Installing SAP Query Connector Client................................................................................. 45
7.2.3 Using SAP Query Connector ................................................................................................ 45
7.2.4 Defining Query .................................................................................................................... 47
8 QlikView SAP Report Connector ........................................................................................49
8.1 SAP System.............................................................................................................................. 49
8.1.1 Prerequisites........................................................................................................................ 49
8.2 QlikView SAP Report Connector Client.................................................................................... 50
8.2.1 Prerequisites........................................................................................................................ 50
8.2.2 Installing SAP Report Connector Client ............................................................................... 50
8.2.3 Preparing SAP Report.......................................................................................................... 51
8.2.4 Using SAP Report Connector ............................................................................................... 52
8.2.5 Defining Report ................................................................................................................... 54
9 QlikView SAP Extractor Connector.....................................................................................57
9.1 SAP System.............................................................................................................................. 57
9.1.1 Prerequisites........................................................................................................................ 57
9.1.3 User Configuration for SAP BASIS System 6.10, 6.20, 6.40, and 7.00.................................. 58
9.1.4 Setting up SAP Side Extractor.............................................................................................. 58
9.1.5 Setting up QlikView SAP Extractor ...................................................................................... 59
9.1.6 Setting up QlikView Extractor Administration..................................................................... 60
9.1.7 Activating/Generating Data Sources/Extractors................................................................. 61
9.2 QlikView SAP Extractor Connector Client................................................................................ 62

4
9.2.1 Prerequisites........................................................................................................................ 62
9.2.2 Installing SAP Extractor Connector Client............................................................................ 62
9.2.3 Using SAP Extractor Connector ........................................................................................... 62
9.2.4 Delta Loads.......................................................................................................................... 67
9.2.5 Hierarchy Properties............................................................................................................ 67
9.2.6 Overview of Logs and Processes.......................................................................................... 70
9.2.7 Error Handling..................................................................................................................... 71
9.3 QlikView SAP Extractor Connector in BW System ................................................................... 73
9.3.1 Prerequisites BW ................................................................................................................. 73
9.3.3 User Configuration for SAP BASIS System 6.40 and Later – BW.......................................... 74
9.3.4 Setting up SAP BW Side Extractor ....................................................................................... 74
9.4 QlikView SAP Extractor Connector in BW System – Client...................................................... 75
9.4.1 Prerequisites........................................................................................................................ 75
9.4.2 Installing SAP Extractor Connector Client............................................................................ 75
9.4.3 Using SAP Extractor Connector ........................................................................................... 75
9.5 Important Issues...................................................................................................................... 76
9.5.1 Services File ......................................................................................................................... 76
9.5.2 Multiple Loads..................................................................................................................... 76
9.5.3 Idoc Length.......................................................................................................................... 76
9.5.4 Language Dependencies ..................................................................................................... 76
9.5.5 Finding Activated Data Sources........................................................................................... 76
9.5.6 Logistics Data Sources......................................................................................................... 76
9.6 Authorizing SAP Extractor Connector in SAP Systems............................................................. 78
9.6.1 Authorization Profile in SAP ERP ......................................................................................... 78
9.6.2 Authorization Profile in SAP BW System ............................................................................. 81
9.7 Tips and Recommendations .................................................................................................... 84
9.7.1 Delta Mechanism ................................................................................................................ 84
9.7.2 Load Time............................................................................................................................ 84
9.7.3 Sample Extractors ............................................................................................................... 84
9.7.4 Transaction Codes............................................................................................................... 85
10 BAPI Connector ..............................................................................................................86
10.1 SAP System.............................................................................................................................. 86
10.1.1 Prerequisites ................................................................................................................... 86
10.1.2 Installing Transports ....................................................................................................... 86
10.1.3 User Configuration for SAP BASIS System 6.10, 6.20, 6.40, and 7.00 ............................. 86
10.1.4 Function modules in the SAP System .............................................................................. 87
10.2 QlikView .................................................................................................................................. 90
10.2.1 BAPI Function in QlikView............................................................................................... 90
11 BW Process Chain Status and QlikView tasks...............................................................92
11.1 Background.............................................................................................................................. 92

5
11.2 BW Process Chain Overview.................................................................................................... 92
11.3 How to do it............................................................................................................................. 92
11.4 Set-up in SAP BW system ........................................................................................................ 93
11.5 Setup in Qlikview..................................................................................................................... 94
12 Secure Network Communication ....................................................................................97

6
1 About this Document
This document describes the installation and use of the QlikView connector for use with SAP
NetWeaver. The latest version of this document is available through support@qliktech.com.

7
2 Introduction
The QlikView components are installed on two different types of computers; the SAP system
and the QlikView SAP connector client. The procedures for each of these systems are
described in this document.
The connector package consists of seven different connectors:
 SQL connector
 Query connector
 Report connector
 Extractor connector
 BAPI connector
 OLAP connector (can only be used on a SAP BW system).
 DSO/ODS connector (can be used on a SAP BW system).

8
3 Authorization Concept
3.1 General
3.1.1 Authorization Concept
The Connectors are intended to be used as back-end components, not to be used by end-
users. The authorization for end-users should be setup via the normal QlikView procedures, not
described in this document.
Connector-specific SAP Users should be created and these should not be used for other
purposes. This will ensure traceability and better control. The Connector package includes
Roles and Profiles, but these should be seen as suggestions to be used in development
environments. Parts of the development process of the QlikView applications will be to create
the necessary authorization in Production Roles. Changes to the Qlikview supplied Roles in
future versions have to be manually added to the Production Roles.
An authorization is a permission to perform a certain action in the SAP system. The action is
defined by the values of individual fields in an authorization object. When a user logs on to a
client in an SAP system, the user’s authorizations are loaded in the user context. The user
context is located in the user buffer (in the main memory) of the application server.
Several authorizations may be needed to perform an operation in the SAP system. The
resulting contexts can be complex. The SAP authorization concept, based on authorization
objects, has been introduced to provide an understandable and simple procedure. Several
system elements that are to be protected form an authorization object.
The programmer of a function decides whether, where, and how authorizations are to be
checked. The program determines whether the user is authorized to perform an activity by
comparing the specified authorization object field values in the program to the authorization
values in the user master record.
Authorizations can be collected in authorization profiles in order to reduce the maintenance
effort that would be required to enter individual authorizations in the user master record. Access
authorization changes affect all users with the profile in their master record.

9
3.1.2 QlikView Predefined Authorization Roles
One of the SAP transports from QlikView contains some predefined Roles. These Roles are
only a proposal and should be adjusted to fit the specific purpose and needs. Remember, if you
add authorization objects or change values, you should do so in a new custom Role, to avoid
these changes being lost when you import new versions of the Connector transports. The
QlikView supplied Roles and their intended usage are listed below.
3.1.2.1 QTQVCACCESS
To be used by SQL, Report, Query and BAPI Connector Back-end user for doing extraction
jobs from QlikView.
3.1.2.2 QTQVCADMIN
The QTQVCADMIN role has been created in order to make a restricted setup using SAPGUI
for row-based security. With row-based security, the tables and fields that the user is allowed to
access can be controlled within the SQL Connector.
The role should only be given to people normally administering Authorisations in SAP.
3.1.2.3 QTQVCBWACCESS
To be used by OLAP and DSO/ODS Connectors Back-end user for doing extraction jobs from
SAP BI/BW system with QlikView.
3.1.2.4 QTQVCEXTRACTOR
To be used by Extractor Connector Back-end user for doing extraction jobs from QlikView.

10
3.1.2.5 QTQVCEXTRADM
This role can only be used to activate and generate the extractors in an SAP system. The role
is very restricted and can only be used to activate the extractors for later use by the Extractor
Connector.
3.1.2.6 QTQVCEXTRSETUP
This role can only be used to create, delete, and verify the setup of the number logical system
in an SAP system for later use by the Extractor Connector.

11
4 QlikView SAP SQL Connector
4.1 SAP System
4.1.1 Prerequisites
 SAP BASIS system 610 or later (R/3 4.7 or later)
4.1.2 Installing Transports
Two transports must be installed in the SAP system. These are copied to the following folder on
the computer during the installation of the QlikView SAP connector:
C:Program FilesCommon FilesQlikTechCustom
DataQvSAPConnectorTransports
A third transport, used with Roles for the OLAP and/or DSO connectors, is also supplied.
The transports can also be obtained through the QlikTech support (support@qliktech.com).
4.1.2.1 SAP BASIS System 4.6
For these systems, use version 5.30 of the QlikView SAP connector.
4.1.2.2 SAP BASIS System 6.10 and 6.20
For these systems, the following transports must be installed in the SAP system:
 E6DK900335 (data extraction)
 E6DK900329 (user profile)
The transports must be installed in the above order. The first is cross-client, whereas the
second is client-specific and has to be installed on all clients where it is to be used.
4.1.2.3 SAP BASIS System 6.40 and 7
For these systems, the following transports must be installed in the SAP system:
 E6DK900338 (data extraction)
 E6DK900329 (user profile)
The transports must be installed in the above order. The first is cross-client, whereas the
second is client-specific and has to be installed on all clients where it is to be used.

12
4.1.3 User Configuration for SAP BASIS System 6.10, 6.20, 6.40, and 7
After the transports have been installed in the system, proceed as follows:
Create one or more SAP users that will be used for Back-end jobs from QlikView. These users
are not intended for QlikView end-users– only a few SAP users should be created. The reason
to create several users might be that you want to give them different authorization or for
traceability.
1.
a. Go to transaction SU01.
b. Click Create (F8).
c. Give the user a name and a password.
d. On the Logon data tab, assign the user to User Type: Service.
e. On the Roles tab, add the role QTQVCACCESS.
f. Click Save.
2. If the installation is an upgrade from a previous version and the role QTQVCACCESS
has been updated, update all users assigned to the role:
a. Go to transaction PFCG.
b. Enter the role name QTQVCACCESS and click Change Role.
c. On the User tab, enter the name of the user(s) created above.
d. Click User comparison.
e. Click Complete comparison.
f. Click Save.

13
4.1.4 Testing SQL Statements – /QTQVC/SQL
The /QTQVC/SQL transaction allows testing of SQL SELECT statements. After installing the
transports and creating a user, proceed as follows to test that everything has been correctly
installed:
1. Log on with the newly created user and test transaction /n/QTQVC/SQL.
2. Enter the SQL statement.
3. Click Open Stream.
4. Click Fetch Stream to display the result.
4.2 Authorisation
The Role QTQVCACCESS should be used by the newly created SAP/QlikView user, this Role,
delivered in a Transport gives access to all tables in the SAP system. This Role is only
intended to be used in a development environment. In production a copy of this Role should be
used, where you have restricted access to only the tables that need to be downloaded.

14
4.2.1 Table-based Access Control
Proceed as follows to configure the table-based access control:
1. Go to transaction PFCG and enter the role QTQVCACCESS.
2. Click the Change icon, .
3. Select the Authorizations tab.

15
4. Click the Change authorization data icon.
5. Expand the tree until the QlikTech Display>Table name row is available.
6. Click the Pencil icon, , to change the values.
By default, it has the value *, which means all tables are accessible. Single values or
ranges of tables can be entered.
4.2.2 Row-based Access Control
In most cases Table-based access restriction is sufficient, but there can be situations where
you also want to restrict which rows can be downloaded within a table.
Use the /n/QTQVC/USERCONTROL transaction to define row-based access to specific tables
for a user. This transaction is only to be used, if download restriction on row-level is needed. If
the tables are empty, the table-based access restriction is used instead (see section 4.2.1). If
there is at least one row in this row-based restriction, it takes precedence over the table-based
restriction.

16
To use this functionality, create an additional Admin user that is allowed to use this transaction.
Create the user in the same manner as above, but assign the role QTQVCADMIN instead. The
Download users must not have this role assigned.
In the left-hand table, Restriction tables, define the table to download data from:
 If restriction on row-level is not needed, enter * as FieldName and ALL as Domain.
 Any user assigned to a domain with a * in the TableName column has access to all
tables.
 To restrict on row-level, enter the FieldName for which to make a value-based
restriction. The Domain field is a free text field. Several field names in different tables
can be linked to the same domain (to ease the maintenance of values).
In the right-hand table, Restriction users, define per user allowed values per domain:
 If all values are allowed, enter * in the Value field and ALL in the Domain field.
 To restrict, enter one or more values in the Value field. Multiple values must be
separated by , (comma). Non-numeric values must be enclosed with ‘x’ (single quotes).
Ranges can be specified as BT(‘a’-‘d’).

17
 To restrict on more than one field in a table, create more lines in each table.
 To create OR conditions, use the Group field to link the values together in pairs (or
triplets).
Example:
(VKORG = 1000 AND SPART = 10) OR (VKORG =2000 AND SPART =20) 
VKORG value=1000 group=1
SPART value=10 group=1
VKORG value=2000 group=2
SPART value=20 group=2
To get an overview of what has been entered for a specific table or user, click Overview. This
screen is only used to display the defined access.
The left-hand and right-hand tables are joined together using the Domain field.
Filtering can be done on table and/or user.

18
To ease the maintenance, there is a copy user function. Click Copy User to open the dialog
below. If the Copy to user already exists, the lines of the Copy from user are appended to any
existing lines.
4.3 QlikView SAP SQL Connector Client
4.3.1 Prerequisites
 QlikView version 9 or later
 If there is a firewall between the connector and the SAP system, port 33nn has to be
open (where nn = system number of the SAP system).
4.3.2 Windows Folders
The different parts of the connector are installed in two different places in the Windows folder
structure. The first folder is for the program installation, C:Program FilesCommon
FilesQlikTechCustom DataQVSAPConnector. The second folder is for ScriptBuilder,
licenses, and log files. This path differs depending on the Windows version:
 Windows XP: C:Documents and SettingsAll UsersApplication
DataQlikTechCustom DataQvSAPConnector
 Windows Vista and later: C:ProgramDataQlikTechCustom
DataQvSAPConnector
4.3.3 Installing SAP SQL Connector Client
There is a 32-bit (x86) and a 64-bit (x64) installation package for the Windows part of the
connector. Check if the QlikView software is 32-bit or 64-bit and then select the corresponding
installation package.
The package includes all the SAP connectors and they are all installed.

19
Proceed as follows to install the SAP connectors:
1. Double-click the installation file.
2. Click Next.
3. Choose a region and then click Next.

20
4. Select I accept… and then click Next.
5. Click Next.

21
6. Click Install to start the installation.
7. Click Finish.
4.3.4 Using SAP SQL Connector
Proceed as follows to start using the SAP SQL connector:
1. Start QlikView.
2. Open the Script Editor.

22
3. Select the Custom Data tab.
In QlikView 10, the Data and Custom Data tabs are combined.
If everything is correctly installed, QvSAPConnector.dll is displayed.
4. Click Connect…
5. Enter the Application Server Host address, Client, and System Number of the target
SAP system, or select the Message Server Host option and enter the Message
Server Address, Client, System ID, and Group.
If passing through a message server, an entry may have to be added in the
C:WINDOWSsystem32driversetcservices file. Add sapmsxxx
36nn/tcp, where xxx is the system ID and nn is the system number. If it is the
last line in the file, add a new line break after the entry.
If passing through an SAP router, paste the router string in the Host address field.

23
In addition, enter the Username and Password of the user that is to be used for this
specific download. Remember that different users can get different results due to
row-based access control.
6. Click Test Connection to verify that all fields are correctly filled in.
7. Finally, click OK to get a connection string in the script.
There are a number of parameters that can be added to the connection string, if needed.
Normally, the default values for these parameters are sufficient. Separate parameters with ;
(semi-colon) in the connection string:
 ConvRoutine=0/1 (default = 0, on = 1): Indicates that output conversion routines are
used. This is commonly used for fields like Material Number (MATNR).
 KeepCasing=0/1 (default/off = 0, but all newly generated connection strings have
value 1): Indicates that lowercase characters in the SELECT statement remain
lowercase. In previous versions (530 and below), the complete statement is converted
to uppercase, thus preventing the use of lowercase characters in Where clause values.
 CheckSeparator=0/1 (default/off = 0): A specific combination of characters is used
as field separator in the connector. This combination may occur in a field in the
database and cause an error. If that happens, turn on this parameter to make the
connector try alternative character combinations. Since this slows down the
performance, it is only to be used when necessary.
 Nulldate=0/1 (default/off = 0, but all newly generated connection strings have value
1): If on, date type fields with the value ‘00000000’ are returned as NULL to QlikView.
 RemoveAllBlanks=0/1 (default/off = 0): If on, provides the possibility to get the “old”
behavior, where all blanks in fields in SAP containing only blank characters are
trimmed. The default behavior leaves one blank character in order to differentiate from
NULL fields.
 TargetServer=xxxxxxx: If specified, forces the background job to be executed on
the specified application server. The correct name can be found in transaction SM51.
The name is case-sensitive.
 JobClass=A/B/C (default = C): Sets the priority for the background job, which can be
useful for small jobs that need to be reloaded often.
 BufferPercentage=nn (default = 10): Defines the amount of the free shared
memory buffer that can be used by the job. A higher value increases the speed, but
also increases the risk for conflicts with other jobs.
 TimeOutBatch=n (default = 600 seconds): The number of seconds that the
background job waits for the client side to fetch data.
 TimeOutFetch=n (default = 1200 seconds): The number of seconds spent trying to
fetch from SAP without getting any records back.

24
 TimeOutStartBatch=n (default = 2400 seconds): The number of seconds that the
client side waits for the background job to start.
 PacketSize=n (default = 20000): The maximum number of rows that the connector
tries to download for each fetch operation. This is re-calculated by the connector and
might be reduced automatically, depending of the actual amount of shared memory in
the SAP system.
 Log=0/1 (default/off = 0, on = 1): If on, writes a log file in the Windows folder
C:Documents and SettingsAll UsersApplication
DataQlikTechCustom DataQvSAPConnectorLog.
 Logpath=xxxx: Places log files in a subfolder named xxxx. The folder is created, if
needed. xxxx can be any text string that can be a valid part of a folder name in
Windows.
 LogFile=yyyy: Names the log file yyyydatetime-n.txt. yyyy can be any text
string that can be a valid part of a filename in Windows.
 Trace=0/1 (default/off = 0, on = 1): Turns on/off the trace functionality in SAP
programs. The trace information is written in the table /QTQVC/TRACE.
4.3.5 ScriptBuilder
ScriptBuilder is a QlikView application that is used to find tables to download from the SAP
system and to generate the script code.
You can select Start>Programs>QlikView to start ScriptBuilder, but we recommend you copy
the complete folder to be able to use this application for several SAP systems.
The application is located in C:Documents and SettingsAll UsersApplication
DataQlikTechCustom DataQVSAPConnectorScriptBuilder.
Start with the ReLoadSAPDD.qvw application, which downloads data from the data dictionary
of the SAP system. Since the content of the dictionary differs for different variants and versions
of SAP, this is a necessary first step.
ReLoadSAPDD.qvw creates .qvd files that can be loaded to the ScriptBuilder application.
Change the script regarding the connection and language in this application prior to doing a
reload.
The Popular Tables and Data Models sheets may refer to tables that do not exist in the version
of SAP used.
Detailed usage instructions can be found in the application.

25
4.3.6 SQL SUBSELECT Syntax
The SQL connector has one addition to the standard SAP OPENSQL syntax, SUBSELECT. This
addition has been developed since JOIN or SUBSELECT cannot be done with cluster tables.
Quite often this is required for tables like BSEG or KONV in order to do delta loads.
Note that the SUBSELECT method cannot be used, if the row-based security concept of the
QlikView SAP SQL connector is activated.
The result of the select from the main table is temporarily stored in the ABAP program in an
internal table. There is a size limitation to internal tables, so try to avoid SELECT * – only
select the fields necessary.
The syntax of SUBSELECT in the QlikView script is as follows:
SQL SUBSELECT BUKRS BELNR GJAHR BUZEI BUZID AUGDT FROM BSEG WHERE BUKRS BELNR GJAHR IN (
SELECT BUKRS BELNR GJAHR FROM BKPF WHERE BLDAT GE '20070101' );
Only one SUBSELECT is allowed (within the parenthesis).
The SUBSELECT can have condition(s).
One or many comparison fields can be passed.
If the SELECT of the subtable returns duplicates, they are removed before selecting from the
main table. So, there is no need (and it does not work) to use the DISTINCT addition to the
SUBSELECT.
The comparison field or fields has to match between main and SUBSELECT. The field names of
the comparison fields do not have to be the same in the main and SUBSELECT, but the
corresponding fields (of main and SUBSELECT) must have the same data types.
To achieve good performance, it is important to provide as many of the key fields in the main
table as possible. Try to select them from the subtable. The most important item to provide is
the first key field (after client).
If the SUBSELECT fails, the reason can often be found in the log for the job
/QTQVC/READ_DATA in transaction SM37.
Other examples of SUBSELECT statements:
SQL SUBSELECT KDATU KAWRT KBETR WAERS FROM KONV WHERE KNUMV IN ( SELECT KNUMV FROM VBRK
);
SQL SUBSELECT CHANGENR TABNAME TABKEY FNAME CHNGIND VALUE_NEW VALUE_OLD FROM CDPOS WHERE
OBJECTCLAS OBJECTID CHANGENR IN ( SELECT OBJECTCLAS OBJECTID CHANGENR FROM CDHDR WHERE
CHANGENR BETWEEN '0000100000' AND '0000300000' );
4.3.7 SAP SQL Connector Log
The SAP SQL Connector Log is a QlikView application that analyzes the usage of the SQL
connector and shows the security setup.

26
Select Start>Programs>QlikView to start the application. It is located in C:Documents and
SettingsAll UsersApplication DataQlikTechCustom
DataQVSAPConnectorSAPConnectorLog.
Start by adding a connection string to the script and then do a reload from the SAP system.

27
5 QlikView SAP OLAP Connector
5.1 SAP System
5.1.1 Prerequisites
SAP BW/NetWeaver BI:
 3.0B with Support Pack 30 or higher
 3.1 with Support Pack 24 or higher
No transports have to be installed.
5.1.3 User Configuration
A transport role, E6DK900314, which can be imported, is supplied. It contains a ready-made
role named QTQVCBWACCESS with the content listed below.
This is a suggested Role only intended to be used in a Development environment. As part of
the development process you should create a more restricted Role to be used in Production
environment.
If importing into SAP BW versions below 7.00, errors/warnings regarding missing objects are
received, but these can be ignored.
Alternatively, go to transaction PFCG and proceed as follows to manually create a role with the
access rights below:
1. Add the following authorization objects:
 S_RFC
i. ACTVT: 16
ii. RFC_NAME: RFC1, RRT0, RSAB, RSOB, SDIFRUNTIME, SYST,OCSB,
SYSU, SRTT
iii. RFC_TYPE: FUGR
 S_TABU_LIN
i. ACTVT: Restrict according to customer (* to access all)
ii. ORG_CRIT: Restrict according to customer (* to access all)
iii. ORG_FIELD1: Restrict according to customer (* to access all)
iv. ORG_FIELD2: Restrict according to customer (* to access all)

28
v. ORG_FIELD3: Restrict according to customer (* to access all)
vi. ORG_FIELD4: Restrict according to customer (* to access all)
vii. ORG_FIELD5: Restrict according to customer (* to access all)
viii. ORG_FIELD6: Restrict according to customer (* to access all)
ix. ORG_FIELD7: Restrict according to customer (* to access all)
x. ORG_FIELD8: Restrict according to customer (* to access all)
 S_RS_AUTH
i. BIAUTH: 0BI_ALL
 S_RS_COMP
i. ACTVT: 03,16, 22
ii. RSINFOAREA: Restrict according to customer (* to access all)
iii. RSINFOCUBE: Restrict according to customer (* to access all)
iv. RSZCOMPID: Restrict according to customer (* to access all)
v. RSZCOMPTYPE: Restrict according to customer (* to access all)
 S_RS_COMP1
i. ACTVT: 03, 16, 22
iii. RSZCOMPID: Restrict according to customer (* to access all)
iv. RSZCOMPTYPE: Restrict according to customer (* to access all)
v. RSZOWNER: Restrict according to customer (* to access all)
 S_RS_ERPT
i. ACTVT: 03, 16, 22
ii. RSERPTID: Restrict according to customer (* to access all)
iii. RSZOWNER: Restrict according to customer (* to access all)
 S_RS_HIER
i. ACTVT: 71
ii. RSHIENM: Restrict according to customer (* to access all)
iii. RSIOBJNM: Restrict according to customer (* to access all)
iv. RSVERSION: Restrict according to customer (* to access all)
 S_RS_ICUBE
i. ACTVT: 03
ii. RSCUBEOBJ: DATA, DEFINITION
iii. RSINFOAREA: Restrict according to customer (* to access all)
iv. RSINFOCUBE: Restrict according to customer (* to access all)
 S_RS_MPRO
i. ACTVT: 03

29
iii. RSMPRO: Restrict according to customer (* to access all)
iv. RSMPROBJ: DATA, DEFINITION
2. Create one or more download user(s) with the above role. Do not use the same
download user as the SQL connector.
d. On the Logon data tab, assign the user to User Type: Service or
Communications.
e. On the Roles tab, add the role just created.
3. If download users with different access rights to cubes/queries are needed, copy the
role created above and change the second role according to the requirements. Create
a new user with the second role assigned.
5.2 QlikView SAP OLAP Connector Client
5.2.1 Prerequisites
5.2.2 Installing SAP OLAP Connector Client
The OLAP connector is included in the same installation package as the other connectors. For
installation instructions, see section 4.3.3.

30
5.2.3 Accessing BEX Queries
To access BEX queries through the OLAP interfaces, they need to have the below property set
in the BEX Query Designer (differs slightly between BEX versions).
5.2.4 Using SAP OLAP Connector
Proceed as follows to start using the SAP OLAP connector:
1. Start QlikView.
If everything is correctly installed, QvSAPOLAPConnector.dll is displayed.
4. Click Connect…

31
last line of the file, add a new line break after the entry.
specific download.

32
Normally, the default values for the parameters are sufficient. Separate parameters with ;
 Log=0/1 (default/on = 1, off = 0): If on, a log file is created in the Windows folder
Windows.
 Lang=(EN/DE…): The logon user’s default language is used by default. For available
languages, see table T005. If texts have to be downloaded in multiple languages, the
relevant info objects have to be downloaded with separate connection strings.
 ConsistencyCheck=0/1 (default/on = 1): If on, optimization is done for maximum
speed. If this fails due to inconsistent metadata, change this parameter to off and retry.
 PartitionSize=nnnnnnn (default = 4000000): Increasing this parameter increases
the speed, but also the risk of getting dumps in the SAP system. If many dumps are
received, adjust this parameter downwards. In most cases, the download recovers.
 MinMembersInSlicedCharacteristic=nn (default = 10): Automatic slicing only
chooses among characteristics that have more members than this value. In odd cases,
no other suitable characteristic is available, which means this value might have to be
lowered.
5.2.5 Defining Query
Proceed as follows to define a query:
1. Click Cubes in the Script Editor.

33
2. Select an InfoCube in the Info provider drop-down list.
The drop-down lists all cubes that have at least one query that allows external access
(see the restriction above). The first item in the drop-down is $INFOCUBE, which is a
top level for all InfoCubes in the system.
3. Select a query in the Query drop-down list.
The drop-down lists all queries (that allow external access) built on the selected cube.
If $INFOCUBE is selected, all InfoCubes are returned.
4. Select at least one characteristic (or navigational attribute) in the Characteristics box
to get any rows downloaded. A key figure does not have to be selected.
When selecting a characteristic, the bottom part of the window is populated. If there is
more than one hierarchy, select one of them (since only one hierarchy/characteristic
can be downloaded). Additional display attributes for the characteristic can also be
selected. The default attribute is always downloaded.

34
Uncheck the Include All Values of Characteristic box to display the possible values
for the members of the characteristic. Selecting a value generates a slice with that
value. If the box is checked, all members of the characteristic are downloaded.
The Variables box contains any variables defined for the selected query. These can be
Optional or Mandatory, Single-value or Ranges.
The generated pseudo-MDX statement can be manipulated manually, but this is
generally to be avoided.
Select PseudoMDX (
Dimensions (
[0APO_PROD] (),
[0CUSTOMER] (),
[0MATERIAL] (),
[0CALWEEK] ()),
Measures (
[64381YV80FHCMZ26ZQQD1003D].[7A9LKMEDKUB9T6IKWEQ73C3PV], //Base Sales Quantity
[64381YV80FHCMZ26ZQQD1003D].[CD68DKVB8003MAL0SAICC8R6F], //Cost of Sales
[64381YV80FHCMZ26ZQQD1003D].[AEAIWVOIFO6I466U6IDWVT3D8], //Discount 1
[64381YV80FHCMZ26ZQQD1003D].[7UBTSBFL7JOPKTEUVINKD4TX6], //Ind. Sales Costs
[64381YV80FHCMZ26ZQQD1003D].[ETLOUTKELIRDGUSQNJ5CVLRS5], //Net sales
[64381YV80FHCMZ26ZQQD1003D].[CJQ2FSM751JT7SSRRFJ0T8ICL], //Planning Status
[64381YV80FHCMZ26ZQQD1003D].[9X0UTMFZ5VWQT208HAJSLV3QM]), //Revenue
From (0CSAL_C02/LWT1));
//*****
5.2.6 Optimizing Query
If dumps are produced in the SAP system or if the performance is slow, there are a number of
performance improvements that can be implemented.
By default, the connector suggests the “D” (direct) parameter in the script. This is only intended
for small amounts of data, since no slicing is performed.
Select PseudoMDX D (
Dimensions (
[BUD_CTRY] (),
[BUD_LOC] (),
[BUD_PROD] (),
[BUD_SECT] (),
[0CALMONTH] ()),
Measures (
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[05N6UOUENHI2PSWMWNWV0HQS0],
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[6VMTYSJE733GVSGXA7WME01WO],
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[AN043YDNYQQUUJIIW73G7SLCX],
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[AYC6O2WD0MJ1CXERY8AHAKUVC]),
From (ZBUD_CUBE/ZZBUD_LWT));
If “D” is removed, automatic slicing is performed. The automatic method primarily uses a time
characteristic for slicing. If this fails or is missing, the largest characteristic is used instead. If
this fails or is too slow, the connector can be forced to slice on a specific characteristic by using
the “S” parameter. Check the connector log file for details when the job has failed.
Select PseudoMDX (
Dimensions (

35
[BUD_CTRY] (),
[BUD_LOC] S (),
[BUD_PROD] (),
[BUD_SECT] (),
[0CALMONTH] ()),
Measures (
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[05N6UOUENHI2PSWMWNWV0HQS0],
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[6VMTYSJE733GVSGXA7WME01WO],
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[AN043YDNYQQUUJIIW73G7SLCX],
[3ZAJ9QPTM5D8U5L9A1RCNSWWE].[AYC6O2WD0MJ1CXERY8AHAKUVC]),
From (ZBUD_CUBE/ZZBUD_LWT));
The automatic performance optimizations only work for basic InfoCubes and if the O parameter,
PseudoMDX O, is added. In all other cases, it is recommended to download the characteristics
and key figures in one load and create separate loads for each characteristic with its attributes
and hierarchies. If these separate loads are stored in QVD files, they can be easily merged
together using the KEY field of the characteristic:
//*** Load Characteristics and Key Figures
LOAD [Country - Country Level 01 (Text)],
[Country - Country Level 01 (Key)],
// [Location - Location Level 01 (Text)],
[Location - Location Level 01 (Key)],
mid([Location - Location Level 01 (Key)],index([Location - Location Level 01
(Key)],'.[')+1) as [Location_Key], // link to Region hierarchy bottom level
[Month - Month Level 01 (Text)],
[Month - Month Level 01 (Key)],
[Organization - Organization Level 01 (Text)],
[Organization - Organization Level 01 (Key)],
// [Product - Product Level 01 (Text)],
[Product - Product Level 01 (Key)],
mid([Product - Product Level 01 (Key)],index([Product - Product Level 01 (Key)],'.[')+1)
as [Product_Key],
[Sector - Sector Level 01 (Text)],
[Sector - Sector Level 01 (Key)],
// [Calendar Year/Month - Calendar Year/Month Level 01 (Text)],
[Calendar Year/Month - Calendar Year/Month Level 01 (Key)],
Factor, Cost, Budget, Revenue
FROM D:Testing5.2olapZBUD_CUBE_Measures.qvd (qvd);
//*** Load Region Hierarchy and Display attributes
LOAD [Location - Regions Level 01 (Text)],
[Location - Regions Level 01 (Key)],
"Location - Regions Level 01 - [1BUD_LOC]",
[Location - Regions Level 02 (Text)],
[Location - Regions Level 03 (Text)],
mid([Location - Regions Level 03 (Key)],index([Location - Regions Level 03

36
(Key)],'.[')+1) as [Location_Key], // link to Location
"Location - Regions Level 03 - [5BUD_LOC]"
FROM D:Testing5.2olapZBUD_CUBE_BUD_LOC.qvd (qvd);
LOAD [Product - Product Hierarchy Level 01 (Text)],
[Product - Product Hierarchy Level 01 (Key)],
"Product - Product Hierarchy Level 01 - [1BUD_PROD]",
[Product - Product Hierarchy Level 02 (Text)],
[Product - Product Hierarchy Level 02 (Key)],
mid([Product - Product Hierarchy Level 02 (Key)],index([Product - Product Hierarchy
Level 02 (Key)],'.[')+1) as [Product_Key], // Link to Product
"Product - Product Hierarchy Level 02 - [2BUD_PROD]"
FROM D:Testing5.2olapZBUD_CUBE_BUD_PROD.qvd (qvd);
LOAD
[Calendar Year/Month - Calendar Year/Month Level 01 (Text)],
[Calendar Year/Month - Calendar Year/Month Level 01 (Key)], // link to Calendar
Year/Month
"Calendar Year/Month - Calendar Year/Month Level 01 - [20CALMONTH]",
"Calendar Year/Month - Calendar Year/Month Level 01 - [20CALMONTH2]",
"Calendar Year/Month - Calendar Year/Month Level 01 - [20CALYEAR]",
"Calendar Year/Month - Calendar Year/Month Level 01 - [20DATEFROM]",
"Calendar Year/Month - Calendar Year/Month Level 01 - [20DATETO]",
"Calendar Year/Month - Calendar Year/Month Level 01 - [20NUMDAY]",
"Calendar Year/Month - Calendar Year/Month Level 01 - [20NUMWDAY]"
FROM D:Testing5.2olapZBUD_CUBE_0CALMONTH.qvd (qvd);
5.2.7 Delta Loads
A special template, OLAP_delta.qvw, has been produced as an example of how delta loads
can be performed. The procedure is described in a separate document,
OLAPDeltaLoad.doc. Both can be downloaded from QlikCommunity under SAP User
Group>Documents.

37
6 QlikView SAP DSO/ODS Connector
6.1 SAP System
6.1.1 Prerequisites
SAP BW/NetWeaver BI:
 3.0B with Support Pack 30 or higher
No transports have to be installed.
Use the same role as defined for the OLAP connector (see chapter 5), if manually created you
need to add the items below:
 Two additional function groups, RSAB and RSODSO_BAPI
 Authorization object S_RS_ODSO with DATA and DEFINITION

38
 Use the same download user as the OLAP connector
6.2 QlikView SAP DSO/ODS Connector Client
6.2.1 Prerequisites
6.2.2 Installing SAP DSO/ODS Connector Client
The DSO/ODS connector is included in the same installation package as the SQL connector.
For installation instructions, see section 4.3.3.
6.2.3 Using SAP DSO/ODS Connector
Proceed as follows to start using the DSO/ODS connector:
1. Start QlikView.
If everything is correctly installed, QvSAPDSOConnector.dll is displayed.
4. Click Connect…

39
specific download.

40
 ODSMAXROWS: By default, this parameter is 10 000 000 records. This is to avoid huge
memory consumption, which is a problem with this BAPI. The connector stops reading
data when reaching the maximum number and returns an error message. Be careful
when reading very large tables, since memory consumption may get high.
Windows.
1. Click DSO/ODS in the Script Editor.

41
2. Select an InfoArea in the InfoArea drop-down list or leave it as-is (<All>) to display all
InfoAreas.
3. Select a DSO object in the DSO Object box.
4. Select the fields in the Info Object box.
The script appears in the bottom box.
To reduce the memory need, the slice functionality can be used to slice by column (row
slicing is not possible). The generated script stores the result in separate QVD files,
which have to be merged later on. All QVD files have a common key field to simplify
the merge.
No navigational attributes are available.
5. Using the following syntax, a WHERE clause can be added manually:
WHERE
ColumnName1 sign option value,
ColumnName2 sign option value1 value2
No display attributes or key characteristics are allowed as columns in the WHERE
clause.

42
The following values are valid in the SIGN field:
 ‘E’ = exclude
 ‘I’ = include
The following values are valid in the OPTION field:
 ‘EQ’ = equal to
 ‘GE’ = greater than or equal to
 ‘LE’ = less than or equal to
 ‘GT’ = greater than
 ‘LT’ = less than
 ‘NE’ = not equal to
 ‘CP’ = contains
 ‘BT’ = lies between (upper and lower limits)
Conditions for the same column (regardless of the number and sequence in the table)
are treated as OR operations. Conditions for different columns are treated as AND
operations.
Example:
from 0SAL_DS01
where 0DIVISION I EQ 01;
or
WHERE 0CREATEDON I BT 20100101 20101231

43
7 QlikView SAP Query Connector
7.1 SAP System
7.1.1 Prerequisites
See section 4.1.1.
See section 4.1.2.
Use the same user as defined for the SQL connector.
In addition to this; go to transaction SQ03 and provide the user with access to the relevant SAP
query user groups. All queries in the user groups assigned are available via the query
connector. For some queries, additional authorization may be needed. This is then to be added
to an additional role (for example, QTQVCACCESS_CUSTOM). In most cases, the connector
log reveals the missing authorization. If not, the Infoset definition and/or logical database
definition have to be checked.

44
Proceed as follows to configure the query connector:
1. Go to transaction SQ03.
2. Enter the user ID in the User field.
3. Click Change.
4. Check all the User group boxes that the download user is to have access to.
5. Click Save.

45
7.2 QlikView SAP Query Connector Client
7.2.1 Prerequisites
7.2.2 Installing SAP Query Connector Client
The query connector is included in the same installation package as the SQL connector. For
installation instructions, see section 4.3.3.
7.2.3 Using SAP Query Connector
It is strongly recommended to test the query in transaction SQ01 prior to testing it via QlikView.
If the query prompts for variable input, create a variant of the query with pre-defined values for
the variables.
Proceed as follows to start using the query connector:
1. Start QlikView.
If everything is correctly installed, QvSAPQueryConnector.dll is displayed.
4. Click Connect…

46
specific download.

47
Windows.
1. Click Queries in the Script Editor.

48
2. Enter the search criteria (query name and/or query description) in the Search for field.
To re-sort the list, click the header of the field to sort on.
3. Select a query and click Preview or Add to Script.
4. Click OK to return to the Script Editor with the generated script.

49
8 QlikView SAP Report Connector
8.1 SAP System
8.1.1 Prerequisites
See section 4.1.1.
See section 4.1.2.
Use the same user as defined for the SQL connector.
Each Report can check any number of authorization objects and it is not obvious which objects
are used.
The pre-defined role for the QlikView connector, QTQVCACCESS, does not cover the
authorization objects that could be used by the reports to be executed. These should be added
to an additional role (for example, QTQVCACCESS_CUSTOM), to avoid being over-written
when installing new versions of the QlikView supplied transport.
If wide authorization roles are not to be added to the download user, an authorization trace on
each report to be used has to be performed.
Proceed as follows to configure the report connector:
1. Go to transaction ST01.
2. Start an authorization trace.

50
3. Run the report with a user that has sufficient access.
The results show the authorization objects used.
4. Add the authorization objects used to the download user.
5. Go to transaction SU03.
6. Perform a Where Used analysis.
If existing roles are added to the download user instead, do a Where Used analysis on
the objects to figure out appropriate roles to add. In addition, change the User Type
from Service to Communication to avoid the user from being used to log on with
SAPGui.
8.2 QlikView SAP Report Connector Client
8.2.1 Prerequisites
8.2.2 Installing SAP Report Connector Client
See section 4.3.3.

51
8.2.3 Preparing SAP Report
Some reports in the SAP system cannot be handled by the QlikView SAP report connector:
 Reports where the layout is too complex
 Reports that are too large (the maximum width is 1000 characters)
 Reports that do not create a spool file (which is the output format that the connector
retrieves). To check this, chose Execute and Print or Execute in Background when
running the report and inspect the spool queue afterwards.
If only the transaction code, but not the report program name, is known, the name can be found
by clicking the system icon at the bottom of the SAPGui window, which shows the program
name in the highlighted line.
The report can sometimes run without a variant, but in most cases a variant is needed to pre-fill
mandatory variables, since these cannot be added through the report connector.
If the report is long-running, it is recommended to create a variant with a limited amount of
pages to use during development.

52
Create a variant when the desired variable values have been entered.
It is strongly recommended to test the report in SAPGui prior to testing it via QlikView.
8.2.4 Using SAP Report Connector
Proceed as follows to start using the report connector:
1. Start QlikView.

53
If everything is correctly installed, QvSAPReportConnector.dll is displayed.
4. Click Connect…
specific download.

54
Windows.
8.2.5 Defining Report
The report connector tries to retrieve a table that can be imported to QlikView from the spool
file. Since reports can have different looks, QlikView Developer has to assist the connector by
defining how to interpret the spool file.
Proceed as follows to define the report:
1. Click Reports in the Script Editor.
2. Enter the report program name in the Report field and, optionally, a variant in the
Variant field.
It is not possible to search, so the name of the report must be known, and it is
recommended to test the report in SAPGui prior to testing it via QlikView.

55
3. Click Get.
The report is executed and shown in the two major areas of the window. The top area
is used to define the rows to skip or consider as data lines or header lines. Sub-header
lines can be defined to be added as columns in the major table.
By default, the Action column shows all lines as data lines. This can be changed by
selecting a line and using the options below:
 The Category column can sometimes be used as an identifier for lines that are to
be treated in the same way (skipped, header, or added as column), but scroll
through the entire list to make sure all lines that have the same category can be
treated in the same way.
 If the category cannot be used, look for substring values in certain positions that
characterize the type of line.
 Added as Columns can be used when there are data values in header lines that
are to go into the table. In the example above, Line 1 contains the company name,
“IDES AG”, which probably changes to other company names in subsequent
pages. By using the “add as columns” function and category 1, these lines are
added as an extra column to the table.
The bottom area shows the final result and also defines the columns.

56
The field delimiter can only be used if the column position has the same value for all
rows (usually an “!” character). The ruler line automatically shows that a separator has
been found.
If a field separator cannot be found, the positions for the field separators have to be
added manually using the Field delimiter after position field.
4. Click OK to return to the Script Editor with the generated script.
Since all data comes from the spool file, the data types are not known to the connector, which
means it cannot modify fields according to data type as the other connectors can. This means
that negative field values are shown as in SAP with the minus sign at the end of the field (for
example, 12256-) and that date fields are not recognized by QlikView as dates. This can be
handled using scripting in the load statement.
 Move the minus sign to the front of the field:
if (right([Field1_Amount],1)='-', (left([Field1_Amount],(len([Field1_Amount])-
1)))*-1
// else
, replace([Field1_Amount],',',''))
// end if
as Local_Curr,
 Make a date field recognizable as a date:
date#([Field2_Doc. Date],'DD.MM.YYYY') as [Field2_Doc. Date],

57
9 QlikView SAP Extractor Connector
In the SAP ERP system, there are pre-defined data sources available to use for transferring
data to SAP BI systems.
The Extractor Connector uses these data sources and the standard SAP extract method.
9.1 SAP System
9.1.1 Prerequisites
 SAP BASIS system 620 or later (R/3 4.7 or later / BW 350 or later)
 Data transport (data extraction)
 Access transport (user profile)
 BW knowledge like SAP education – BW350-BI Data Acquisition
See section 4.1.2.

58
9.1.3 User Configuration for SAP BASIS System 6.10, 6.20, 6.40, and 7.00
After the transports have been installed in the system, proceed as follows to create new User
for the extractor connector (QTQVCEXTRACTOR)
Administrative Roles QTQVCEXTSETUP and QTQVCEXTRADM can be added to existing
Admin users of the SAP system.
1. Create one or more users:
f. On the Roles tab, add the role QTQVCEXTRACTOR.
g. Click Save.
2. If the installation is an upgrade from a previous version and the roles
QTQVCACCESS/QVEXTRACTOR have been updated, update all users assigned to
the role:
b. Enter the role name QTQVCACCESS or QTQVCEXTRACTOR.
c. Click Change Role.
d. On the User tab, enter the name of the user(s) created above.
e. Click User comparison.
f. Click Complete comparison.
g. Click Save.
9.1.4 Setting up SAP Side Extractor
A series of standard extractors are delivered within SAP for data transfer to the SAP Business
Information Warehouse. If BI/BW is not used, proceed as follows to activate a series of
processes within SAP:
1. In some cases, it has to be set up from the customizing side, which is reached through
the SPRO transaction and the Activate Business Functions menu.
2. Go to transaction SBIW to transfer and activate the BI/BW DataSources.
3. Check that the tree hierarchy and data sources are activated.

59
4. If this is not the case, transfer the Application Component Hierarchy and then the
Business Content DataSources.
 Transfer Application Component Hierarchy:
 Transfer Business Content DataSources: Start by activating the tree hierarchy and
then activate each data source to be used.
9.1.5 Setting up QlikView SAP Extractor
Configuration changes to the clients are required to execute the processes involved in the
QlikView extractor (QTQVC/EXTRACTOR_ADM). The SAP client is required to have “changes
to repository and cross-client customizing allowed”.
Note: The SAP client must be set to “Open” when processing the administration setup.
Proceed as follows to set up the extractor connector:
1. Go to transaction SCC4.
2. Select Client.

60
3. Change the system to reflect the options below.
9.1.6 Setting up QlikView Extractor Administration
To initiate the capabilities of the QlikView extractor connector, a one-time task is required to
create a logical system to receive the generated Idocs/RFC used in the extractor process.
Go to transaction /n/QTQVC/EXTRACTOR_ADM and perform the setup:
 Create: Creates the logical system of the receiver. See the SALE transaction.
 Creates the RFC connection (same name as the logical system).
 Creates the partner profile of type LS (same name as the logical system).
 Creates the Basic Idoc type for data transfer. The name is hard-coded like
“ZSQAQTQVCEXTR1”.
 Verify: Verifies that all necessary components of the extractor environment are
configured.
 Delete: Deletes all components in the extractor environment.
Note: Close the SAP client after the setup.

61
9.1.7 Activating/Generating Data Sources/Extractors
Once the setup is complete and the extractors have been activated in the SAP system, proceed
as follows to activate the extractors for use with the QlikView extractor connector:
1. Go to transaction RSA6.
2. Select a DataSource/Extractor in the transaction by high-lighting it and copying the
technical name (using Ctrl+Y on the keyboard). This can also be done manually.
3. Go to transaction /n/QTQVC/Activate.
4. Paste the selected extractor in the Extractor name field.
5. Click Get Extractor.
6. Select the field to activate (X) or select all fields.
7. Click Activate Extractor.

62
9.2 QlikView SAP Extractor Connector Client
9.2.1 Prerequisites
9.2.2 Installing SAP Extractor Connector Client
See section 4.3.3.
9.2.3 Using SAP Extractor Connector
Proceed as follows to start using the extractor connector:
1. Open the QlikView application.
2. Edit the QlikView script.

63
3. Look for “SAPEXTRConnector” and click Connect…
This generates a connection string in the QlikView system.

64
9.2.3.1 Timeouts
There are a few timeout parameters that can be set in the QlikView script in the connection
string. If not set in the connection string, each timeout has a default value. All timeout values
are given in seconds.
 TimeoutSAP: This timeout is used in the SAP part of the connector. When trying to
start a new extractor job in SAP, there is a check to see that no other extractor job is
already started for the given logical system. An extractor job in SAP consists of two
parts. The first part is an extraction batch job that creates all Idocs containing the
extraction data. The second part is the RFC transfer of the Idocs to QlikView.
Sometimes there can be interruptions in the RFC transfer. A number of retries to send
the data is then performed. The value of the TimeoutSAP parameter determines the
amount of time that SAP waits to start a new job, if there is an ongoing RFC transfer of
a previous job. When the number of seconds in the timeout has passed, it is likely that
there is a permanent error in the previous RFC transfer. The previous job is then
regarded as failed (the corresponding record in the SAP status table is set to “aborted”)
and the new job is allowed to start. The default value is 14400 seconds (240 minutes).
 TimeoutInit: This timeout is used in the Windows part of the connector. It
determines the maximum amount of time that Windows wait to receive data from SAP
regarding the activated extractors and hierarchies possible to use. If the timeout is
exceeded, the QlikView job is aborted. The default value is 900 seconds (15 minutes).
 TimeoutActivity: This timeout is used in the Windows part of the connector. It
determines the maximum time that Windows wait to receive the first Idoc from SAP
created by the extraction job. If the timeout is exceeded, the QlikView job is aborted
and the status value in the corresponding record in the SAP status table is set to
“aborted”. The default value is 3600 seconds (60 minutes).
 TimeoutIdoc: This timeout is used in the Windows part of the connector. It
determines the maximum amount of time that Windows wait between the receiving of
each Idoc. If the timeout is exceeded, the QlikView job is aborted and the status value
in the corresponding record in the SAP status table is set to “aborted”. The default
value is 7200 seconds (120 minutes).
Proceed as follows to set the timeout parameters:
1. Select a system in the Logical System drop-down list.
2. Select a language in the Language drop-down list.
3. Click Search to get the activated extractors.

65
4. Select an extractor in the Activated Extractors box (A) and then click Get Fields (B).
5. To edit the selection to add filters, click the edit button (not all fields are editable).

66
6. Click Add in the pop-up window.
7. Click Add to Script to add the selection to the script.
A predefined script is added to the QlikView application:
The standard script is a proposal and the functionality to activate has to be
uncommented.
In the example above, the selection is initially loaded from the logical system
QTQVCEXTR1 and only for KOKRS (controlling area) 1000. The QVD is stored in the
qvd/init/ folder and the name of the QVD file is INIT_0COSTCENTER_TEXT.QVD.

67
9.2.4 Delta Loads
One of the major advantages of the extractor connector is the ability to use delta load
capabilities (if allowable in the extractor itself).
To execute a delta load, proceed as follows:
1. Uncomment the required UPMODE statement in the script:
UPMODE C – initial extraction followed by delta load
This creates a QVD file with all of the data through the extractor and also tells SAP that
a delta load process is required in the future.
2. Modify the extractor script:
UPMODE D – delta extraction
3. Concatenate the QVD to the output.
Note: When using the delta loads, use the same template and the same logical system as have
been used for the initialization.
4. To do a new initial extraction (UPMODE C) on an existing initial extraction load, delete
the data source in this transaction (/N/QTQVC/DELETE_INIT) before the new load
starts. Fill in the logical system and then the data source/extractor to delete.
9.2.5 Hierarchy Properties
9.2.5.1 Definition
Hierarchy properties are the properties of all hierarchies for a hierarchy basic characteristic,
delivered by SAP, and freely definable according to the needs of the customer.
9.2.5.2 Use
Hierarchy properties are fixed in InfoObject maintenance for a characteristic and valid for all
hierarchies that have been created for the characteristic.
During hierarchy maintenance, the hierarchy attributes can be set and, as a result, influence
the display and processing of hierarchies in reporting.

68
9.2.5.3 Load Hierarchies to QlikView
Unlike all other data sources in SAP, hierarchies do not have to be activated. When loading a
hierarchy, proceed as follows to change the screen view in the pop-up window:
1. Select the Show Hierarchies radio button.
2. Select the logical system in the Logical System drop-down list.
3. Click Search.
4. Select a hierarchy in the Hierarchies box (A) and click Get Hierarchies (B).
All available options for the selected hierarchy are displayed.
5. Select an option in the Nodes box.
6. Click Add to Script.

69
As a result, two statements are added to the QlikView script for the hierarchy load.
 First statement:
 Second statement:
The first statement uses the QlikView HIERARCHY function to create nodes for each level. To
link the hierarchy table to other standard extractors, a function can be deployed to NODENAME,
for example:
Mid(NODENAME,5,13) as [SAKNR],
Each hierarchy requires different manipulation to perform the join operation.
The second load statement provides the option for descriptions of the levels in the hierarchy.

70
9.2.6 Overview of Logs and Processes
There are a number of transactions in SAP to monitor the processes involved with the extractor
connector:
 To display the processed Idocs, use transaction code WE02:
 To follow the process in SAP, use transaction code SM50:

71
 To monitor the initialized extractors, use transaction code RSA7:
 The QlikView log is stored in C:ProgramDataQlikTechCustom
DataQvSAPConnectorLog:
The QlikView log provides information on which Idocs have been created for the
request and if the load has been successful.
9.2.7 Error Handling
There are a number of methods to monitor the processes of the extractor connector.

72
9.2.7.1 Status Table
The download for every extractor can be followed in the new status table, /QTQVC/STATUS,
which is available in transaction SE16:
Only a single extraction at a time can run in a logical system. QlikView returns an error
message if multiple extractors run on the same logical system.
In the event of an extractor job not being able to initialize, the status table contains an “S” for
started. A process to cancel the job is required through transaction /N/QTQVC/delete.
9.2.7.2 Canceling a Process
Proceed as follows to cancel a process:
1. In the status table, get the job time and then go to transaction /N/QTQVC/delete.
2. Select /QTQVC/STATUS in the Delete single record from table section.
3. Enter the job time in the JOBTIME field.
4. Run the job in Simulate Deletion mode.
5. Run the job in Delete Records mode.
Note: Take caution not to end an active and relevant job that is running.
9.2.7.3 Re-send Idocs
If a communication error has occurred for a delta or full load and the Idocs have been produced
in the ERP system, the Idocs can be re-sent to QlikView. A new initialization is not needed.

73
Proceed as follows to re-send the Idocs:
1. Get the INITRNR from the QlikView log file:
2. Open the script builder.
3. Select the extractor with the appropriate delta load.
4. Uncomment the INITRNR row.
5. Replace <NR> with the actual INITRNR, and reload:
//INITRNR <NR> // Resend extraction
9.2.7.4 Communication Error
If the logical system is correctly set up and the SAP system can be contacted when connecting,
the standard setting for tRFC in the logical system setup may have to be changed. This is done
in transaction SM59 and TCP/IP connections.
The figure below shows the default settings.
9.3 QlikView SAP Extractor Connector in BW System
The SAP extractor connector can be used against an SAP BW system. The structure of the BW
system differs to that of an SAP ERP system, but the principle is the same.
9.3.1 Prerequisites BW
See section 9.1.1.
See section 4.1.2.

74
9.3.3 User Configuration for SAP BASIS System 6.40 and Later – BW
See section 9.1.3.
9.3.4 Setting up SAP BW Side Extractor
Proceed as follows to set up the SAP BW side extractor:
1. Make sure the source to be used is generated as an export data source:
a. Go to transaction RSA1.
b. Select Cube or DSO/ODS.
c. Right-click and select Additional Functions>Generate Export DataSource.
2. Replicate the internal BW setup:
Choose the BI system from Modeling>Source System.
3. Open Modeling>DataSources.
The internal BI sources are available. In BW, this is referred to as “data marts”.

75
4. Replicate the whole tree or just the data source needed:
Right-click and select Replicate Metadata.
After replicating the data marts, the data sources show up as selectable and can be
activated for the QlikView extractor connector process.
5. Go to transaction code RSA6 and use it as in the ERP system.
The tree differs slightly from the one in ERP. This is because no pre-defined extractors
are used. In BW, the actual data sources are used.
The available sources to be used can be found here. Normally, the technical name
starts with “8” followed by “0” for standard ODSs and cubes. The end of the name uses
“O” for ODS and “C” for cubes.
Example:
6. The technical name can now be activated using the same method as for the ERP
system described previously.
9.4 QlikView SAP Extractor Connector in BW System – Client
9.4.1 Prerequisites
See section 9.2.1.
9.4.2 Installing SAP Extractor Connector Client
See section 9.2.2.
9.4.3 Using SAP Extractor Connector
See section 9.2.3.

76
9.5 Important Issues
9.5.1 Services File
If there is no SAP GUI installed on the machine where the connector is to be installed, the SAP
system gateway port has to be written manually in the folder
C:WindowsSystem32driversetcservices.
Add the following information at the end of the file:
sapgw01 – sapgw99 3301/tcp - 3399/tcp #SAP System Gateway Port
C:WINDOWSsystem32driversetcservices file. Add sapmsxxx 36nn/tcp, where
xxx is the system ID and nn is the system number. If it is the last line in the file, add a new line
break after the entry.
9.5.2 Multiple Loads
If several data sources/extractors have to be loaded at the same time, set up multiple logical
systems. Make sure to use the same logical system when loading the deltas.
9.5.3 Idoc Length
The total length of an Idoc is 1000 characters. The normal length of an extractor is between
250 and 700, but when using a BW or CRM system with many text fields, the length of the
extractor could end up above this. If so, exclude some fields in order to be able to use the
extractor. The total length of an activated extractor can be checked using transaction WE30.
9.5.4 Language Dependencies
All standard datasources/extractors are maintained in every language. A customized data
source is only activated in the log on language, if no action is taken. This has to be taken into
consideration when activating a data source in the SAP system.
9.5.5 Finding Activated Data Sources
The relevant activated data sources are found in the SAP system:
 In transaction SE16 in the SAP ERP, the extractors are found in table ROOSOURCE.
 In BW, the table name is SOLTPSOURCE.
Use transaction WE30 and check the Basic Idoc Type to see which segment that has been
activated.
9.5.6 Logistics Data Sources
In logistics, activities have to be carried out in several areas in order to use the extractors within
the SAP Business Information Warehouse.
Start by going to transaction SBIW.

77
9.5.6.1 Managing Extract Structures
This section is used for customization of extract structures in movement data for logistics. The
old LIS technique for the transfer information structures has some disadvantages compared to
the new technique and is no longer necessary. There are, however, some overlaps between
the two techniques, particularly if LIS and BW are to be used in parallel.
9.5.6.2 Initialization
The initialization must be prepared by OLTP. A setup completes the setup tables, which are
then read during the initialization.
To enable the setup to be reset after a termination, assign a name to each background run for
the setup. Then, if a setup terminates or a setup from the archive documents is interrupted, the
status of the setup at the point of termination can be stored under the assigned name. When
restarting the setup using the assigned name, the processing can continue from the point of
termination without having to go through the entire process again. Once the run has completed
successfully, the in-between status stored in the memory is deleted.
The setup must run in the background.
9.5.6.3 Filling the Setup Table
Completing the setup tables is a critical action that must be carried out with caution. For large
amounts of data, this can take more than a night and may have to be done over a weekend.
The setup log (transaction NPRT) contains information on setups that have already been
carried out.
9.5.6.4 Application-Specific Setup of Statistical Data
This section describes the relevant, application-specific features for applications that can
perform statistical setups.

78
Example: SD-Sales Orders – perform setup
 Standard settings: In this activity, selected sales orders are called and the statistical
update of the BW extraction structures for sales orders is triggered. The statistical
update used here corresponds to the one chosen in the customizing cockpit.
 Requirements: Before this activity can be carried out, at least one extraction structure
per application must have been activated. For more information, see Logistics Extract
Structures Customizing Cockpit.
9.6 Authorizing SAP Extractor Connector in SAP Systems
A QlikView user needs to have certain access rights within the SAP ERP and BW systems to
use the extractor connectors.
The minimum authorization level needed is defined below.
9.6.1 Authorization Profile in SAP ERP
Maint.: 0 Unmaint. org. levels 0 open fields, Status: Unchanged
QTQVCEXTRACTOR QVEXTRACTOR
|
|-- Manually Cross-application Authorization Objects AAAB
| |
| |-- Manually ALE/EDI: Receiving IDocs via RFC B_ALE_RECV
| | |
| | |-- Manually ALE/EDI: Receiving IDocs via RFC T-ED55072400
| | |
| | |----- Message Type RSRQST EDI_MES
| |

79
| |-- Manually Authorization Check for RFC Access S_RFC
| | |
| | |-- Manually Authorization Check for RFC Access T-ED55072400
| | |
| | |----- Activity 16 ACTVT
| | |----- Name of RFC to be protected * RFC_NAME
| | |----- Type of RFC object to be prote FUGR RFC_TYPE
| |
| |-- Manually Transaction Code Check at Transaction Start S_TCODE
| |
| |-- Manually Transaction Code Check at Transaction Start T-ED55072400
| |
| |----- Transaction Code RSA3, RSA6, SE16, SM50, SM51, SM58, SU53 TCD
|
|-- Manually Basis: Administration BC_A
| |
| |-- Manually System Authorizations S_ADMI_FCD
| | |
| | |-- Manually System Authorizations T-ED55072400
| | |
| | |----- System administration function NADM S_ADMI_FCD
| |
| |-- Manually Background Processing: Operations on Background Jobs
S_BTCH_JOB
| | |
| | |-- Manually Background Processing: Operations on Background Jobs T-
ED55072400
| | |
| | |----- Job operations RELE JOBACTION
| | |----- Summary of jobs for a group * JOBGROUP
| |
| |-- Manually Administration Functions in Change and Transport System
S_CTS_ADMI
| | |
| | |-- Manually Administration Functions in Change and Transport System T-
ED55072400
| | |
| | |----- Administration Tasks for Chang TABL CTS_ADMFCT
| |
| |-- Manually Spool: Device authorizations S_SPO_DEV
| | |
| | |-- Manually Spool: Device authorizations T-ED55072400
| | |
| | |----- Spool: Long device names * SPODEVICE
| |
| |-- Manually Table Maintenance (via standard tools such as SM30) S_TABU_DIS
| |

80
| |-- Manually Table Maintenance (via standard tools such as SM30) T-
ED55072400
| |
| |----- Activity 03 ACTVT
| |----- Authorization Group * DICBERCLS
|
|-- Manually Basis - Development Environment BC_C
| |
| |-- Manually ABAP Workbench S_DEVELOP
| |
| |-- Manually ABAP Workbench T-ED55072400
| |
| |----- Activity 03, 16 ACTVT
| |----- Package /QTQVC/QTDEV, SRFC DEVCLASS
| |----- Object name * OBJNAME
| |----- Object type * OBJTYPE
| |----- Authorization group ABAP/4 pro * P_GROUP
|
|-- Manually Basis - Central Functions BC_Z
| |
| |-- Manually WFEDI: S_IDOCDEFT - Access to IDoc Development S_IDOCDEFT
| |
| |-- Manually WFEDI: S_IDOCDEFT - Access to IDoc Development T-
ED55072400
| |
| |----- Activity 01, 02, 03 ACTVT
| |----- Extension * EDI_CIM
| |----- Basic type RSSEND, ZSQ* EDI_DOC
| |----- Transaction Code WE02, WE30 EDI_TCD
|
|-- Manually Authorizations: BW Service API RO
|
|-- Manually Remote Content Activation of SAPI DataSources from a BW
S_RO_BCTRA
| |
| |-- Manually Remote Content Activation of SAPI DataSources from a BW T-
ED55072400
| |
| |----- Activity 07 ACTVT
|
|-- Manually SAP DataSource Authorizations S_RO_OSOA
|
|-- Manually SAP DataSource Authorizations T-ED55072400
|
|----- Activity 03 ACTVT
|----- DataSource * OLTPSOURCE

81
|----- DataSource Application Compone * OSOAAPCO
|----- Subobject for DataSource DATA OSOAPART
9.6.2 Authorization Profile in SAP BW System
In BW, the following objects have to be added:
|-- Manually Business Information Warehouse RS
|
|-- Manually Data Warehousing Workbench - Objects S_RS_ADMWB
| |
| |-- Manually Data Warehousing Workbench - Objects T-BT99020800
| |
| |----- Activity 03, 16, 63, 66 ACTVT
| |----- Data Warehousing Workbench Obj APPLCOMP, CNG_RUN, CONT_ACT,
CONT_ADMIN, DOC_ADMIN, DOC_HIER, DOC_MAST<...> RSADMWBOBJ
|
|-- Manually BI Analysis Authorizations in Role S_RS_AUTH
| |
| |-- Manually BI Analysis Authorizations in Role T-BT99020800
| |
| |----- BI Analysis Authorizations: Na 0BI_ALL BIAUTH
|
|-- Manually Business Explorer - Components S_RS_COMP
| |
| |-- Manually Business Explorer - Components T-BT99020800
| |
| |----- Activity 01, 03, 16, 22 ACTVT
| |----- InfoArea * RSINFOAREA
| |----- InfoCube * RSINFOCUBE
| |----- Name (ID) of a reporting compo * RSZCOMPID
| |----- Type of a reporting component * RSZCOMPTP
|
|-- Manually Business Explorer - Components: Enhancements to the
Owner S_RS_COMP1
|
|-- Manually Business Explorer - Components: Enhancements to the
Owner T-BT99020800
|
|----- Activity 02, 03, 16, 22 ACTVT
|----- Name (ID) of a reporting compo * RSZCOMPID

82
|----- Type of a reporting component * RSZCOMPTP
|----- Owner (Person Responsible) for * RSZOWNER
The role used to run the setup of the logical system needed is called QTQVCEXTRSETUP.
QTQVCEXTRSETUP SETUP EXTRACTOR
|
| |
| |-- Manually Administration for RFC Destination S_RFC_ADM
| | |
| | |-- Manually Administration for RFC Destination T-ED55072500
| | |
| | |----- Activity 01, 02, 03, 06, 36 ACTVT
| | |----- Internet Communication Framewo * ICF_VALUE
| | |----- Logical Destination (Specified * RFCDEST
| | |----- Type of Entry in RFCDES 3, T RFCTYPE
| |
| |
| |
| |----- Transaction Code /QTQVC/EXTRACTOR_ADM, SM59, SU53 TCD
|
| |
| |-- Manually Maintaining QVC-Authorisations /QTQVC/AUT
| |
| |-- Manually Maintaining QVC-Authorisations T-ED55072500
| |
| |----- * ADMIN
|
|
|-- Manually WFEDI: S_IDOCDEFT - Access to IDoc Development S_IDOCDEFT
|
|-- Manually WFEDI: S_IDOCDEFT - Access to IDoc Development T-ED55072500
|
|----- Activity 01, 02, 03, 06 ACTVT
|----- Extension * EDI_CIM
|----- Basic type RSSEND, ZSQ* EDI_DOC
|----- Transaction Code WE30 EDI_TCD

83
To activate and generate the extractors, use the QTQVCEXTRADM role.
QTQVCEXTRADM EXTRACTOR ADM
|
| |
| |
| |
| |----- Transaction Code /QTQVC/ACTIVATE, QTQVC/DEACTIVATE, QTQVC/DELETE,
QTQVC/DELETE_INIT, RS<...> TCD
|
| |
| |-- Manually Table Maintenance (via standard tools such as SM30) S_TABU_DIS
| |
| |-- Manually Table Maintenance (via standard tools such as SM30) T-ED55072600
| |
| |----- Activity 02, 03 ACTVT
| |----- Authorization Group * DICBERCLS
|
| |
| |-- Manually WFEDI: S_IDOCDEFT - Access to IDoc Development S_IDOCDEFT
| |
| |-- Manually WFEDI: S_IDOCDEFT - Access to IDoc Development T-ED55072600
| |
| |----- Activity 01, 02, 03 ACTVT
| |----- Extension * EDI_CIM
| |----- Basic type RSSEND, ZSQ* EDI_DOC
| |----- Transaction Code WE30 EDI_TCD
|
|-- Manually Authorizations: BW Service API RO
|
|-- Manually Remote Content Activation of SAPI DataSources from a BW
S_RO_BCTRA
| |
| |-- Manually Remote Content Activation of SAPI DataSources from a BW T-
ED55072600
| |
| |----- Activity 07 ACTVT

84
|
|-- Manually SAP DataSource Authorizations S_RO_OSOA
|
|-- Manually SAP DataSource Authorizations T-ED55072600
|
|----- Activity 03 ACTVT
|----- DataSource * OLTPSOURCE
|----- DataSource Application Compone * OSOAAPCO
|----- Subobject for DataSource DATA OSOAPART
The three roles can be combined to complete the different purposes of the user.
9.7 Tips and Recommendations
9.7.1 Delta Mechanism
The big advantage of using the SAP Extractor Connector is the delta mechanism, which is
built-in in some of the standard extractors.
It is also easier to use a pre-defined data source from SAP, as no knowledge is required of the
complex table structures in the SAP systems. Most of the data sources and extractors are
self-explanatory.
9.7.2 Load Time
A time lag is experienced during the initialization of the connector whilst the SAP processes
run.
The amount of time to load from an ERP system is similar to that of the SQL connector. To get
good loading performance from a BI/BW system, use the connector against a DSO/ODS
source.
9.7.3 Sample Extractors
The following sample extractors are available for use:
 0FI_GL_4 – General Ledger: Line Items with Delta Extraction
 0FI_AP_4 – Vendors: Line Items with Delta Extraction
 0FI_AR_4 – Customers: Line Items with Delta Extraction
 CO_OM_CCA_9 – Cost Centers: Actual Costs Using Delta Extraction
 0CO_PC_ACT_02 – Material Valuation: Per Ending Inventory
 0CO_PC_01 – Cost Object Controlling: Plan/Actual Data

85
 0EC_PCA_3 – Profit Center: Actual Line Items
 PA – Personnel Management
…and so on.
9.7.4 Transaction Codes
The following transaction codes are available for use:
 QTQVC/ACTIVATE Activate an Extractor (datasource)
 /QTQVC/DELETE Delete Database Table Records
 /QTQVC/DELETE_INIT Delete Initialization
 /QTQVC/DEACTIVATE Deactivate Extractor
 SE 16 Data Browser
 /QTQVC/Status
 /QTQVC/Convert
 RORQSTPRMS (Protocol table Request)
 ROOSPRMSC (Control Parameter Per Data Source Channel)
 ROOSGEN (Generated Objects for OLTP Source)
 SM50 Process Overview
 SM37 Background Job
 RSA6 Post process Data Sources and Hierarchy
 RSA7 BW Delta queue Maintenance
 SMGW Gateway Monitor
 SM58 Transactional RFC
 SMQ1 qRFC Monitor (Outbound Queue)
 WE02 Idoc List
 WE30 Idoc Types

86
10 BAPI Connector
The BAPI connector enables QlikView to call Function Modules or BAPIs (Business Application
Programming Interface) in SAP systems. QA method of a BAPI is implemented as Function
module, so the Connector makes no distinction of these.
The Function Module has to be Remote-enabled to be used from the Connector.
10.1 SAP System
10.1.1 Prerequisites
 SAP BASIS system 610 or later (R/3 4.7 or later)
See section 4.1.2.
10.1.3 User Configuration for SAP BASIS System 6.10, 6.20, 6.40, and 7.00
When the transports have been installed in the system, proceed as follows:
1. Create one or more users:
f. Click Save.
2. If the installation is an upgrade from a previous version and the role QTQVCACCESS
has been updated, update all users assigned to the role:
b. Enter the role name QTQVCACCESS.
c. Click Change Role.
d. On the User tab, enter the name of the user(s) created above.
e. Click User comparison.
f. Click Complete comparison.
g. Click Save.
To run an authorization-related object in a BAPI, the authorization object has to be adjusted in
the QTQVCACCESS role. Alternatively, create a complemented role for those running the BAPI
connector.

87
The QlikView log indicates if something is missing in the authorization:
2012-02-27 09:53:23 Error Returned: TYPE='E', ID='M7', NUMBER='120', MESSAGE='You
have no authorization for this transaction in plant 3000', LOG_MSG_NO='000000',
MESSAGE_V1='3000', ROW='0', SYSTEM='T90CLNT090'
Returned: TYPE='E', ID='M7', NUMBER='121', MESSAGE='You have no authorization for this
transaction with movement type 501', LOG_MSG_NO='000000', MESSAGE_V1='501', ROW='0',
SYSTEM='T90CLNT090'
10.1.4 Function modules in the SAP System
You can find and test Function Modules in SAP in at least two ways:
Use transaction SE37, but difficult to use as a search tool
or
use transaction code BAPI to look for available BAPI functions in the SAP system, proceed as
follows:
1. The transaction provides an overview of the different areas in the SAP system and the
BAPIs that can be used.

88
2. Select an area and a specific BAPI function for test.
3. Click Single Test to go to the test of the function screen.

89
4. Enter the values needed to run the function.
5. Run the function and wait for the result.
If the result is satisfactory, it can be used in the QlikView script to retrieve the same
result.

90
10.2 QlikView
10.2.1 BAPI Function in QlikView
1. In the QlikView script editor, select the BAPI connector and connect to the SAP
system.
2. Click BAPI to select a function.
3. In the pop-up dialog, enter the name of the BAPI function found in the SAP system.
Then click Get parameters.
Note: The parameters field must be filled out with zeros (for example, “0000001234”).

91
4. Enter the parameters needed to run the function.
5. Some Functions return more than one table, but QlikView can only handle one for each
statement. Select the output table you want and then click Add call to script.

92
11 BW Process Chain Status and QlikView tasks
11.1 Background
Today it’s a problem to know when a BW process chain has finished loading data and QlikView
can start loading their part. Below is an example of how you can use the BAPI connector to
check the status of a Process chain and start the QlikView load when ready.
11.2 BW Process Chain Overview
Process chains are a robust graphical scheduling & monitoring tool to maintain automation,
visualization & monitoring of tasks/processes. Typically this is used to update DSOs and
InfoCubes
11.3 How to do it
The Connector transports include a Report program named /QTQVC/PROCESS_STATUS.
Two variants should be created of the program for each process chain, to be used in the
beginning and end of the process chain setting the status of the process. The QlikView script
has to be updated with a loop to be able to check the status and finally change the status.
Variant 1 of the Report program sets the indicator to ”N” = Not Ready and
Variant 2 sets the indicator to ”R” = Ready. When calling the report program the status is stored
in our table /QTQVC/Status.
In the QlikView Script we utilize the BAPI connector to check when there is a ”R” in the table,
then proceed with normal load, and finally set the status to ”F” = Finish when the load is
completed. The BAPI connector calls a function module named /QTQVC/PROCESS_STATUS,
which in turn calls the report program /QTQVC/PROCESS_STATUS.

93
1. Variant to change the indicator to ”N”
2. The process chain load data to BW
3. New variant update the status indicator to ”R”.
4. In the QlikView script the BAPI connector is used to Check
the status and if ”R”,
5. QV starts the normal load.
6. QlikView update the indicator to ”F” using the BAPI
connector.
Mode:
C = Check
U = Update
Status:
N = Not Ready
R = Ready
F = Finished
11.4 Set-up in SAP BW system
You need to be skilled in creating Report variants and maintaining Process chains to do the
below tasks:
Create two variants (N and R) of the program /QTQVC/PROCESS_STATUS, for each process
chain.

94
In the process chain, add this ABAP program with variant at the start and at the end of the
chain. The Task ID has to be unique for each process chain.
11.5 Setup in Qlikview
You need to schedule the QlikView task to start when the Process chains normally ends.
Script Example:
Add a loop in the beginning of the script, using the BAPI connector to check
the Status of the Process chain.
The script will leave the loop when status changes to “R” (Ready) and continue
with the normal load of BW data.
When that is finished it should set the status to “F” (Finished) to avoid the
same data being loaded twice.
CUSTOM CONNECT TO
"Provider=QvSAPBAPIConnector.dll;ASHOST=10.88.20.43;SYSNR=10;CLIENT=800;XUserI
d=QCWJORBOPLTA;XPassword=OUZKbYRNJbaATYMX;";
set Status1='N';
do while Status1 <> 'R'
//CHECK STATUS
Out:
LOAD *;
SQL {

95
"function":"/QTQVC/PROCESS_STATUS",
"output":"STATUS_OUT",
"parameters":
[
{ "direction":"out", "length":1, "name":"STATUS_OUT",
"optional":false, "type":"CHAR", "value":" " },
{ "direction":"in", "length":10, "name":"CONNECTOR",
"optional":false, "type":"CHAR", "value":"PRCHAIN_02" },
{ "direction":"in", "length":1, "name":"MODE",
"optional":false, "type":"CHAR", "value":"C" },
{ "direction":"in", "length":1, "name":"STATUS_IN",
"optional":true, "type":"CHAR", "value":" " },
{ "direction":"in", "length":40, "name":"TASK_ID",
"optional":false, "type":"CHAR", "value":"DATA_01" }
]
};
Let Status1=peek('STATUS_OUT' ,-1,'Out');
exit do when Status1='R';
trace 'Waiting for BW process to finalize';
sleep 10000;
loop
//****************************************************************************
//Load Data
CUSTOM CONNECT TO
"Provider=QvSAPEXTRConnector.dll;ASHOST=10.88.20.43;SYSNR=10;CLIENT=800;XUserI
d=MXMDKRBOPDAB;XPassword=cHNLSYRNJbaATYcc;";
[80COMP_CODET]:
LOAD
[COMP_CODE],
[LANGU],
[TXTMD];
SQL EXTRACTOR 80COMP_CODET
UPDMODE F // full extractor
EXTRLANGUAGE E
LOGSYS QTQVCEXTR1
WHERE
LANGU I EQ E
;
//STORE * FROM [80COMP_CODET] INTO FULL_80COMP_CODET.QVD;
//DROP TABLE [80COMP_CODET];
//****************************************************************************
CUSTOM CONNECT TO
"Provider=QvSAPBAPIConnector.dll;ASHOST=10.88.20.43;SYSNR=10;CLIENT=800;XUserI
d=QCWJORBOPLTA;XPassword=OUZKbYRNJbaATYMX;";
//UPDATE STATUS
drop table Out;
Out:

96
LOAD *;
SQL {
"function":"/QTQVC/PROCESS_STATUS",
"output":"STATUS_OUT",
"parameters":
[
{ "direction":"out", "length":1, "name":"STATUS_OUT", "optional":false,
"type":"CHAR", "value":" " },
{ "direction":"in", "length":10, "name":"CONNECTOR", "optional":false,
"type":"CHAR", "value":"PRCHAIN_02" },
{ "direction":"in", "length":1, "name":"MODE", "optional":false,
"type":"CHAR", "value":"U" },
{ "direction":"in", "length":1, "name":"STATUS_IN", "optional":true,
"type":"CHAR", "value":"F" },
{ "direction":"in", "length":40, "name":"TASK_ID", "optional":false,
"type":"CHAR", "value":"DATA_01" }
]
};
//****************************************************************************

97
12 Secure Network Communication
Secure Network Communication (SNC) is the SAP technology used for safe communication
between SAP components. If the customer has SNC installed, this can also be used for the
RFC communication between the connector and the SAP system.
A cryptographic library must be installed on the connector machine. This is not supplied by
QlikTech. The technology is used between SAP components only. For technical details, see
http://help.sap.com/saphelp_nw04/helpdata/EN/69/b0bbd6dde71141bee8806586144796/frame
set.htm.
Proceed as follows to set up SNC:
1. Open Control Panel>System>Advanced.
2. Create a system variable, SNC_LIB to hold the path to the local crypto library.

98
3. Specify the SNC name in the connection dialog, p:CN=sncname. In addition, specify
the quality of the protection – the available values are specific to the library used.

Qlik view connector manual

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Qlik view connector manual (20)

Qlik view connector manual