perfect web intelligence report 20091018

7/29/2019 Perfect Web Intelligence Report 20091018

1/58

Build the Perfect Web Intelligence Report

Henri Theuwissen

BI Knowledge Sharing


2/58

2009 SAP BusinessObjects User Conference 2

About Henri Theuwissen

Co-founder and managing partner BI Knowledge Sharing,

experts in Business Intelligence

SAP Business Objects experience since 1998 Specialized in customized training, with in-house developed

course material

Speaker at all worldwide and European Business Objectsuser conferences, since 2005

Member of steering committee BI BOUG BeLux

Author of two white papers for SAP Business Objects onconversion to Web Intelligence


3/58


Agenda

1. Introduction

2. Merged Dimensions Basics

3. Working with Table Properties4. Complex Query Linking

5. The Need for Multiple Queries

6. Extra: the Power of Ranking7. Conclusion

8. Q&A


4/58


Agenda

1. Introduction





8. Q&A


5/58


Introduction

Example 1: Consider a report with 2 queries

Query 1: Total Sales per City

Query 2: City and Manager

Notice: both queries do not contain the same City values

Both queries are linked on City


6/582009 SAP BusinessObjects User Conference 6

Introduction

Example 1

Use the two queries to show all City values and their Sales

value. Also show the Manager for each City

Many trials result in incorrect reports:

The required result:

City S from Query 1

City M from Query 2 City MD from the

Merged Dimension



Introduction

Example 2

Create a query showing male players from USA and Russia

Create another query, on the same universe showing playersfrom the USA, with their expenses

Notice that the result is incorrect: Davydenko from Russia is

displayed in the table



Introduction

When you are working with multiple queries in 1 document,

take into account the role and impact of the following

options and table properties:

Auto-merge dimensions

Extend merged dimension values

Show rows with empty measure values

Show rows with empty dimension values

This presentation will demistify these options and illustrate

their power and impact



Agenda

1. Introduction





8. Q&A



Business Case

Four queries

Two queries on the same universe

Three different universes



Business Case

Four queries on three universes, each generating a table

On one query, two tables are created



Automatic Linking

Through the default option Auto-merge dimensionsa link is created between the result of the two queries on

the same universe



Automatic Linking

Build a table using objects from the linked queries; theresult is correct

Q_S1 Q_S2


14/58


Automatic Linking

In the example 2 in the introduction, the two queries are

automatically linked, and the second table uses by default

the merged dimension, resulting in the incorrect table

To correct the problem, deselect the check box Auto-merge

dimensions


15/58


Manual Linking

Consider 2 queries on two different universes

Both queries have common objects (City and Year); though

there is no automatic link created Build a table with two (common) dimensions from query

Q_S1, and two measures, one from each query


16/58


Manual Linking

Since no link exists between the queries, a request is sent

to query Q_T to get just one column: the total Target

This single cell is combined with each row of query Q_S1

Q_S1 Q_T


17/58


Manual Linking

Modify the table structure: select the two (common)

dimensions from query Q_T, and two measures, one from

each query


18/58


Manual Linking

Since no link exists between the queries, a request is sent

to query Q_S1 to get just one column: the total Sales

This single cell is combined with each row of query Q_T

Q_S1 Q_T


19/58


Merge Dimensions

Use the Merge Dimensions icon to open the Merge

Dimensions window

Select the dimensions to create the link between the

queries (City and Year) Optionally assign a new name to the merged dimension


20/58


Merge Dimensions

Use the Values button to review the values in each query


21/58


Merge Dimensions

Create a second link on the common object Year


22/58


Merge Dimensions

The merged dimensions are presented in a separate map

in the Data tab of the Report Manager

Notice the name of the merged dimension


23/58


Since both queries are linked on City and Year, the table

shows correct results now

Only City values from query Q_S1 are shown

Merged Dimensions

Q_S1 Q_T


24/58


Merged Dimensions

With the dimension variables from query Q_T, only City

values from query Q_T are shown

Q_S1 Q_T


25/58


Merged Dimensions

Replace the dimension variables by the

merged dimension columns to receive

all values for City and Year from the

queries Q_S1, Q_T and Q_MQ_S1 Q_T


26/58


Agenda

1. Introduction





8. Q&A


27/58


Merged Dimensions Properties

Use three query results to build one table

Not every City has Sales and Target and a Manager

Q_S1 Q_T Q_M


28/58



Depending on the query from which the City dimension is

used the result changes

Some of the results are unexpected


29/58



Use City from the query on Sales (Q_S1)

The default result does not contain Moscow or New York


30/58



Moscow and New York have no value for Manager

Review the table properties: by default rows with empty

dimension values are not displayed

Correct Result


31/58



Use City from the query on Target (Q_T)

The default result does not contain Moscow or Dallas


32/58



Moscow and Dallas have no value for Manager


dimension values are not displayed

Correct Result


33/58



Use City from the query on Manager (Q_M)

The default result shows all City values from query Q_M,

even Brussels which does not have Sales or Target info


34/58



Brussels does not exist in the queries Q_S1 and Q_T


measure values are displayed

Correct Result


35/58


Use City from the merged dimension and examine theimpact of the property settings



36/58


Agenda

1. Introduction





8. Q&A


37/58


Merged Dimensions Errors

Query Q_S1 and query Q_T contain

details per City and Year

Query Q_M contains info on City level

Build a table using City, Manager and

Year using the merged dimensions

Year and City


38/58


Merged Dimensions Errors

Q_S1 and Q_T have more detailed data than Q_M (YEAR)

Q_S1, Q_T and Q_M are synchronized through the merged

dimension City_MD

Q_M is not synchronized through the merged dimension

Year_MD, resulting in #DATASYNC and #CONTEXT errors


39/58


Merged Dimensions Issues

Build a table using data from the three queries,

synchronized on the values of city; use City_M from Q_M

Remove City_M from the table: the result is incorrect


40/58


Merged Dimensions Issues

Since the merged dimension City is not in

the resulting table, the queries are not

synchronized

Use the ForceMerge function to force

using the merged dimension and to force

synchronizing the queries

Incorrect Result


41/58


Extending Merged Dimensions

Using merged dimensions in a table by default returns only

the dimension values from the selected query


42/58



Select the option Extend merged dimension values in the

Document Properties to include City values from all

contributing queries


43/58



Combine Extend merged dimension values with the table

properties on empty values


44/58


Agenda

1. Introduction





8. Q&A


45/58


The Need for Multiple Queries

Question: Why do I need multiple queries on the same

universe?

Example: HR data: not every employee has a manager

Data Base Table

Universe Structure

Aliased

Table


46/58



Build two queries:

Count employees per city

Show managers per city

Data Base Table


47/58



Build two queries:

Count employees per city

Count employees per city manager

Data base table


48/58



Solution: build two queries on the same universe, with

merged dimensions


49/58


Agenda

1. Introduction





8. Q&A


50/58


The Power of Ranking

Tables with one dimension

Specifying a Ranked by object or not will return the same

result

Th P f R ki


51/58



Tables with multiple dimensions

Specifying a Ranked by object will consolidate the measure

by the selected dimension and then apply the ranking

Th P f R ki


52/58



Tables with multiple dimensions

Not specifying a Ranked by object will rank on the

combination of the dimensions

Th P f R ki


53/58



Working with Calculation mode

Show accumulated sales value up to 100

Th P f R ki


54/58



Working with Calculation mode

Show accumulated sales value up to 80% of total sales

A d


55/58


Agenda

1. Introduction





8. Q&A

C l i


56/58


Conclusion

Combining data from different queries in one table can

result in different output tables depending on the properties

and options specified

Get familiar with the usage and impact of these options and

properties to build exactly the result that you need

A small option can completely change your output

Q&A


57/58


Q&A

Questions

Henri Theuwissen, Partner, BI Knowledge Sharing

I will repeat questions to ensure everyone can hear

Contact information

[email protected] +32 (0) 495 54 52 53

www.BIKnowledgeSharing.be


58/58

Thank you for participating

Please remember to complete and return

your evaluation form following this session.

SESSION CODE: 1104

perfect web intelligence report 20091018

Documents