Build the Perfect Web Intelligence Report

Henri Theuwissen BI Knowledge Sharing

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 Objects user conferences, since 2005 Member of steering committee BI BOUG BeLux Author of two white papers for SAP Business Objects on conversion to Web Intelligence

2009 SAP BusinessObjects User Conference

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

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
2009 SAP BusinessObjects User Conference
5

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:

City S from Query 1 City M from Query 2

City MD from the Merged Dimension

The required result:

2009 SAP BusinessObjects User Conference

Introduction
Example 2
Create a query showing male players from USA and Russia

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

Notice that the result is incorrect: Davydenko from Russia is displayed in the table

2009 SAP BusinessObjects User Conference

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

2009 SAP BusinessObjects User Conference

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

Business Case
Four queries Two queries on the same universe Three different universes

2009 SAP BusinessObjects User Conference

10

Business Case
Four queries on three universes, each generating a table On one query, two tables are created

2009 SAP BusinessObjects User Conference

11

Automatic Linking
Through the default option Auto-merge dimensions a link is created between the result of the two queries on the same universe

2009 SAP BusinessObjects User Conference

12

Automatic Linking
Build a table using objects from the linked queries; the result is correct
Q_S1 Q_S2

2009 SAP BusinessObjects User Conference

13

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

2009 SAP BusinessObjects User Conference

14

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

2009 SAP BusinessObjects User Conference

15

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

2009 SAP BusinessObjects User Conference

16

Manual Linking
Modify the table structure: select the two (common) dimensions from query Q_T, and two measures, one from each query

2009 SAP BusinessObjects User Conference

17

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

2009 SAP BusinessObjects User Conference

18

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

2009 SAP BusinessObjects User Conference

19

Merge Dimensions
Use the Values button to review the values in each query

2009 SAP BusinessObjects User Conference

20

Merge Dimensions
Create a second link on the common object Year

2009 SAP BusinessObjects User Conference

21

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

2009 SAP BusinessObjects User Conference

22

Merged Dimensions
Since both queries are linked on City and Year, the table shows correct results now Only City values from query Q_S1 are shown
Q_S1 Q_T

2009 SAP BusinessObjects User Conference

23

Merged Dimensions
With the dimension variables from query Q_T, only City values from query Q_T are shown
Q_S1 Q_T

2009 SAP BusinessObjects User Conference

24

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_M
Q_S1 Q_T

2009 SAP BusinessObjects User Conference

25

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

26

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

2009 SAP BusinessObjects User Conference

27

Merged Dimensions Properties

Depending on the query from which the City dimension is used the result changes Some of the results are unexpected

2009 SAP BusinessObjects User Conference

28

Merged Dimensions Properties

Use City from the query on Sales (Q_S1) The default result does not contain Moscow or New York

2009 SAP BusinessObjects User Conference

29

Merged Dimensions Properties

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

2009 SAP BusinessObjects User Conference

30

Merged Dimensions Properties

Use City from the query on Target (Q_T) The default result does not contain Moscow or Dallas

2009 SAP BusinessObjects User Conference

31

Merged Dimensions Properties

Moscow and Dallas have no value for Manager Review the table properties: by default rows with empty dimension values are not displayed

Correct Result

2009 SAP BusinessObjects User Conference

32

Merged Dimensions Properties

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

2009 SAP BusinessObjects User Conference

33

Merged Dimensions Properties

Brussels does not exist in the queries Q_S1 and Q_T Review the table properties: by default rows with empty measure values are displayed

Correct Result

2009 SAP BusinessObjects User Conference

34

Merged Dimensions Properties

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

2009 SAP BusinessObjects User Conference

35

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

36

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

2009 SAP BusinessObjects User Conference

37

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

2009 SAP BusinessObjects User Conference

38

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

2009 SAP BusinessObjects User Conference

39

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

2009 SAP BusinessObjects User Conference

40

Extending Merged Dimensions

Using merged dimensions in a table by default returns only the dimension values from the selected query

2009 SAP BusinessObjects User Conference

41

Extending Merged Dimensions

Select the option Extend merged dimension values in the Document Properties to include City values from all contributing queries

2009 SAP BusinessObjects User Conference

42

Extending Merged Dimensions

Combine Extend merged dimension values with the table properties on empty values

2009 SAP BusinessObjects User Conference

43

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

44

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
Universe Structure

Aliased Table Data Base Table

2009 SAP BusinessObjects User Conference

45

The Need for Multiple Queries

Build two queries:
Count employees per city Show managers per city

Data Base Table

2009 SAP BusinessObjects User Conference

46

The Need for Multiple Queries

Build two queries:
Count employees per city Count employees per city manager

Data base table

2009 SAP BusinessObjects User Conference

47

The Need for Multiple Queries

Solution: build two queries on the same universe, with merged dimensions

2009 SAP BusinessObjects User Conference

48

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

49

The Power of Ranking

Tables with one dimension
Specifying a Ranked by object or not will return the same result

2009 SAP BusinessObjects User Conference

50

The Power of Ranking

Tables with multiple dimensions
Specifying a Ranked by object will consolidate the measure by the selected dimension and then apply the ranking

2009 SAP BusinessObjects User Conference

51

The Power of Ranking

Tables with multiple dimensions
Not specifying a Ranked by object will rank on the combination of the dimensions

2009 SAP BusinessObjects User Conference

52

The Power of Ranking

Working with Calculation mode
Show accumulated sales value up to 100

2009 SAP BusinessObjects User Conference

53

The Power of Ranking

Working with Calculation mode
Show accumulated sales value up to 80% of total sales

2009 SAP BusinessObjects User Conference

54

Agenda
1. 2. 3. 4. 5. 6. 7. 8. Introduction Merged Dimensions Basics Working with Table Properties Complex Query Linking The Need for Multiple Queries Extra: the Power of Ranking Conclusion Q&A

2009 SAP BusinessObjects User Conference

55

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

2009 SAP BusinessObjects User Conference

56

Q&A
Questions Henri Theuwissen, Partner, BI Knowledge Sharing I will repeat questions to ensure everyone can hear Contact information Henri.Theuwissen@BIKnowledgeSharing.be +32 (0) 495 54 52 53 www.BIKnowledgeSharing.be

2009 SAP BusinessObjects User Conference

57

Thank you for participating Please remember to complete and return your evaluation form following this session.
SESSION CODE: 1104

2009 SAP BusinessObjects User Conference

58