What BW queries are used by Qlikview ? 

Queries used for qlikview should follow a special naming convention (see Souce Query for QV in BW Naming Conventions) so you search using that name.

In general those queries will have "QV" or "Dashboard" in the description.

Summary of impacts

Reminder on the BW query elements dependencies.

In BW several elements of the queries can be shared between several queries. Modifying it will therefore modify it for all queries using that element :

• All variables : variables are never local to a query. 
• Key figures saved into info-provider : the key figures that show with a technical name.

• Structures saved into the info-provider : If you modify anything, on that structure, it will change for all queries using that structure

How does qlikview use & map BW queries ?

Make sure Qlikview can access the query

The "By OLE DB for OLAP" parameter

Qlikview uses OLE DB to access the BW Queries, so for Qlikview to be able to even see the query, you need to check the "By OLE DB for OLAP" option in the "Extended" query properties in the query designer : 

The QV BW account access

Qlikview uses a special user account to connect to BW and access the data so you need to : 

• The BW user account for Qlikview has the roles to access the query in that infoprovider/infoarea
• The BW user account for Qlikview has the roles to access the data perimeter you need to extract (Usually we give all).

Usually the BW user account is "bw_qlikview".

Generating the extractor and script

To extract data from BW to Qlikview :

• You first need to generate a Qlikview extractor : this reads the query elements.
• You then select the elements you need from the extractor and add them into the qlikview script mapping.

The query itself

For the query itself, Qlikview will use the technical name of the query (Ex : QVSBS_BW_QRY_MV_PROVG_0001)

Variables

• Authorization variables will work and will return the values the Qlikview account has access to (Usually all).
• Mandatory variables will need to be filled.
• Variables will default values will keep the default unless changed in the Qlikview script

Characteristics

Other considerations :

• The Qlikview user for BW has full perimeter access :
  • Authorisation variables will work and return ALL *.
  • Mandatory variables will need to be filled.

• Exceptions & Conditions are ignored by qlikview

• Default values filters are ignored by qlikview

• None of the Characteristics display options impact Qlikview
  • Sort - No impact
  • Result rows - Not received by QV
  • Display as key/text or lengh of the text - Are chosen in the script, not from the query parameters
•