AA BO40 SP02 WebIntelligencev1.0

SAP BO-4.
0 SP02
Web Intelligence
BusinessObjects 4.0 SP02 Web Intelligence

Amit Agarwal
Slide - 1
Agenda
BusinessObjects Solution Overview
Butterfly Model
BI Platform Architecture
Decision Tree
BI Launch Pad Portal
1. Introduction to Web Intelligence
Core Functionality & Concept
Query Process
2. Create Web Intelligence Documents with Queries
Slide - 2
Querying with Web Intelligence
Create a Document
Modify a Document Query
Working in the Query Panel
Query Properties & Data Tab

Agenda Contd
3. Restricting Data Returned by a Query
Modifying a query with a predefined query filter
Applying a single-value query filter
Using prompts to restrict data

Using complex filters
4. Design Web Intelligence Reports
Working with Web Intelligence Documents
Displaying data in Tables and Charts
Presenting data in Free-Standing cells
5. Enhancing the Presentation of Reports
Slide - 3
Using Breaks, Calculations, Sorts and Report filters
Ranking data to see top or bottom values, Using Alerts
Organizing a report into sections
Copying data to other applications

Agenda Contd
6. Formatting Reports
7.
Document formatting
Formatting charts
Creating Formulas and Variables
Formulas and Variables

Using formulas and variables
8. Using Multiple Data Sources
Synchronizing Data from Multiple Data Sources
Creating Multiple Queries in a Document
Synchronizing Data with Merged Dimensions
Using a Personal Data Provider
9. Analyzing Data
Slide - 4
Analyzing the Data Cube
Drilling in an Interactive Analysis Document
Agenda Contd
10. Managing and Sharing Interactive Analysis Documents
Slide - 5
Scheduling Documents
Managing Documents in BI Launch Pad
Viewing Documents in BI Launch Pad
Sharing Documents
Setting BI Launch Pad Preferences
Butterfly Model
Enterprise Performance
Management
USE
Strategy
Planning, Budgeting
Management
and Forecasting
INSIGHT TO
Profitability and
DRIVE
Consolidation
Cost Management
PERFORMANCE
Spend and
Supply Chain
Business
Intelligence
TURN
Query, Reporting,
Reporting
and Analysis
INFORMATION
Dashboards and
Search and
INTO
Visualization
Navigation
INSIGHT
Advanced
Analytics
Governance Risk
and Compliance
OPTIMIZE
Risk
Access
Management
Control
PERFORMANCE
Process
Global Trade
BY
CONTROLLING
Control
Services
RISK
Environmental,
Health and Safety
Information
Management
Data
Data Quality
TAME
Integration
Management
INFORMATION
CHAOS
Master Data
Management
Metadata
Management
BOE Architecture
The BOE technical architecture is

composed of a set of tiers optimized for
specific tasks and operations.
The five tiers are:
1. Client: Web browser and rich clients
2. Application: Java web application
servers and tools
3. Intelligence: System server
processes
4. Processing: Data analysis and
report generation
5. Data: Source repositories
Conceptual Tier
Slide - 8
Decision Tree Select Right Tool
Client Tools for Biz Users and Report Designers
Tools for Data Managers
Tools for Administrator
BI Launch Pad User Interface
BI Launch Pad Document Tab
Preferences
Folders & Categories
Searching in Launch Pad
Web Intelligence Rich Client
Slide - 18
user 7
abcd1234
Slide - 19
Unit 1
Web Intelligence
Introduction
Slide - 20
Unit 1. Introduction
Objectives
Unit Presents Key Concepts and Vocabulary required to understand Web

Intelligence (Interactive Analysis)
We will cover the following Concepts.

Core Functionality.
Slide - 21
Interactive Analysis Core Functionality
Reporting
Analyzing
Access, Analyze and

Share Corporate data
from both OLTP & OLAP
servers
Query your organizations

database using your
everyday business terms
Sharing
Querying
Slide - 22
Web Intelligence Concepts

Semantic Layer
BO Universe is a semantic layer that isolates
users from the technical complexities of the
databases where corporate information is stored.
Universes are based on business terminology
that is familiar to users and is shared throughout
the organization. Universes allow users to create
queries and get information using everyday terms
defined in the universe.
Semantic Layer Comprises of:

Universe
Universe Comprises of:
Objects
Class
Slide - 23
Universe objects and the Query panel

Objects in classes
Database
Universe schema
Purchase
orders
Inventory
Materials
Universe used in this course
Classes
Dimension
Objects
Detail
Predefined
Filters
Measure
Objects
Dimension
Maps to character-formatted data or date-formatted
items. Retrieves data that you are likely to base
queries on.
Detail
Maps to information that you might want to see in a
report, but that would not form the basis of a query.
For example, telephone numbers of stores.
Predefined query filter
Restricts the information returned, such as data
concerning revenue to a specific year. Filters can
also prompt the person refreshing a report to a
selected value, such as Which category?
Measure
Retrieves numerical data that is the result of
calculations on data in the database, and represents
a dynamic aggregate. For example,. Sales revenue
is based upon Quantity Sold x Unit Price.
Types of objects
The types of objects that can be in a universe:
Dimension
combined with a detail...
Detail
to clarify the data.
Measure
to analyze
summary information
Easy Access to Information
Whats the top-selling

summer item?
9
8
7
6
5
4
3
2
1
0
Est
1
1er
trim.
Im calling to place my
summer inventory order!
Run Query
Class
Objects
Result Objects pane
Query Filters pane
About the Query Process
Client Workstation
Run the query

IMAGE
AREA
Web Intelligence Server
Query is converted
IMAGE
AREA
to SQL
Database
IMAGE AREA
SQL is executed
to extract data
Report is displayed
Report is generated
About the Query Process

Client
Server
IMAGE AREA
User asks
a business question
IMAGE AREA
Database
Results
Web Intelligence
Server
Report is displayed
Data Provider
Note :
Information is returned to BOE server as Microcube of data, also called a data provider.
Reporting with Web Intelligence

:
As a table
As a Crosstab
As a Chart (Bar, Line, Pie,

Area, etc)
As a multiple-block report
containing large amount of
data
Block Concept
Analyzing with Web Intelligence
Switch business
perspective
Multi-dimensional analysis
Web Intelligence panels

Rich Client
Interactive HTML
Sharing
Web Intelligence
Slide - 35
Q&A
1. True or False: Web Intelligence is a single tool for

understanding, controlling and sharing business
information.
2. What is universe?
3. What is the core functionality of Web Intelligence?
4. Describe three ways for sharing Web Intelligence
documents with others.
Q&A
True or False: Web Intelligence is a single tool for understanding, controlling
and sharing business information.
Answer: True
What is universe?
Answer: A Universe is the BusinessObjects semantic layer that maps to data in a database and is
used for creating queries in Web Intelligence, Desktop Intelligence and Crystal Reports.
What is the core functionality of Web Intelligence?

Answer. Web Intelligence core functionalities are - Querying, Reporting, Analysis and Sharing.
Describe three ways for sharing Web Intelligence documents with others.
Answer:
Sending to a users Inbox

Saving the document to a corporate folder or category
Saving a document as an Excel or PDF file
Q&A
?
Slide - 38
Unit 2
Creating Web Intelligence

Documents with Queries
Slide - 39
Unit 2: Creating Webi Documents with Queries
Objectives:
Slide - 40
Create a Document
Modify a Document Query
Working in the Query Panel
The Data Tab
Universe used E-Fashion
Sample Database of eFashion
What is eFashion
Slide - 41
A successful retail store selling fashion merchandise in 11 US cities.
The company currently sells 211 products across 12 different product lines.
Your Objective:
As analyst working at eFashion Head Quarters in New York produce and distribute
BusinessObjects reports to all eFashion stores.
Prepare series of reports on the companys performance over this last year, to be sent to
company management. Other reports to be published and available to all company
employees.
Objects
E-Fashion
E-Fashion
Classes
Universe
OLTP
Demo Create a Simple Webi Document & Save it

1. Launch Web Intelligence Rich Client
2. Or Use the Web based Web Intelligence Tool
3. Create a New Document to display Annual Sales Revenue using e-Fashion
Universe
4. Save the Document
5. Check the Various Option available to save the Web Intelligence Document
Locally and on SAP BOBJ BI Platform.
6. Modify the Query and Run Query Again. Save the Document.
NOTE: Use Connected Mode and not offline mode.
Slide - 42
Data Aggregation
Data aggregation depends on the dimensions used in the view block.

Example - Report shows Sales revenue broken down by Year and Quarter.
(Example of a high-level aggregation)
Aggregation of data changes if the dimension objects are changed.

Add the Store name object to the table and Sales revenue is broken down
even further. Values re-aggregated to display the sales revenue earned by
each store. (Example of low-level aggregation).
Slide - 43
Measure objects are Dynamic in Nature. Their values change depending

on which dimension objects are used with them.
Web Intelligence officially supports a maximum of 15 queries per document.
Unit 3. Restricting Data Returned by a Query
Objectives
Slide - 44
Modifying a query with a predefined query filter
Using prompts to restrict data
Using multiple filters (also called - Complex Filters)
Restricting Data with Query Filters
Query filters allow you to:
Slide - 45
Retrieve only the data you need to answer a specific business question
Hide the data you dont want specific users to see when they access the document.
Minimize the quantity of data returned to the document to optimize performance.
Query Filter
A Query Filter has three elements:

Financial Year
Filter
Equal to
FY05-06
Object
Operator
Operand
Object:
a column of data
Operator:
specifies the relationship between the

object and the operand
Operand:
the object value to be searched for
Data concerning any year other than FY05-06 will not be returned by the query.
Slide - 46

The following is a list of operators you can choose from
Slide - 47
Operator
Retrieves Data
Example
Equal to
Equal to a value specified
[Country] Equal to US retrieves data for the

US country value only.
Different from
Different from a specified value
[Quarter] Different from Q4 Retrieves data

For all quarters Except Q4.
Greater than
Greater than a Specified value
[Customer Age] Greater than 60 retrAnd

ieves data for Customers over age 60.
Greater than or equal to
Greater than or equal to a specified

value
Revenue Greater than or equal to 10000

retrieves data for revenue starting from
$10000 and up. in an
Less than
Lower then the specified value
[Exam Grade] less Then 40 retrieves data

for Exam grades below 40.
Less then or equal to
Lower or equal to specified value
[Customer] Age Less than or equal to 30

retrieves data for Customers age 30 or
less.
Between
Between two specified values, Also

includes values specified
[Weeks] between 25 and 36 retrieves data

for weeks from week 25 to 36, including
week 25 and week 36.
Not between
Outside the range of values specified
[Weeks] not between 25 and 36 retrieve data

for all weeks of the year excluding week
25 through week 36. Week 25 and 36
are not included.
Slide - 48
In list
Same as values specified
[Country] in list US, Japan, UK retrieves data

for counties US, Japan and UK
Not in list
Different from multiple values specified
[Country] in list US, Japan, UK retrieves data

for all countries excluding US, Japan
and UK
Is null
For which there is no value entered in the

database
[Children] is null Retrieve data for customers

without children where Null is entered as
a value for their database under the
children column.
Is not null
For which a value was entered in the

database
[Children] is not null Retrieve data for

customers with children where any value
is entered as a value for their database
under the children column.
Matches pattern
Including a specific string
[Phone] Matches Pattern 773 retrieves data

for all phone numbers that have 773 in
them.
Different from pattern
Doesnt include a specific string
[Phone] Different from Pattern 773 retrieves

all phone numbers that do not have 773
in them.
Both
Corresponds to two specified values
[Account type] Both fixed and mobile

retrieves data for customers who have
both a fixed and mobile telephone.
Except
Corresponds to one specified value and

does not correspond to another
specified values
[Account type] Both fixed Except mobile

retrieves data for customers who have a
fixed telephone but dont have a mobile
phone.
FOUR Types of Query Filters

1. Predefined query filters These are built right into the universe.
2. Single and multi-value filters
3. Prompted Filters
4. Complex filters
Slide - 49
Using Predefined Filter
Click the Edit Query button on the

toolbar to open an Edit Query View.
The document opens in the Edit
Query view.
Edit the query by dragging the This

Year predefined filter to the query
filters pane.
Slide - 50
Slide - 51
Applying a single-value with value from list
Slide - 52
Applying a single-value with value from list
Slide - 53
Using Wildcards
Slide - 54
In the Search All Values text box, you can:
Perform wildcard searches using (*) to replace one or several characters

of the value searched for. For example, clicking in the Search All Values
text box, typing C*, then clicking the binoculars button retrieves all
categories starting with C (Cardigan and Causal Dresses).
Or, Use(?) t to replace one data to for the value searched for. For example,
clicking in the Search All Values text box, typing S?irts, then clicking the
binoculars button retrieves the values skirts and Shirts.
Prompted Filters
Advantages:
Multiple users viewing a single document to specify a different subset

of the database information, and yet still display it in the same tables
and charts in the report.
Ask user for input every time data in the document is refreshed. Users
can insert the prompt either by typing or by selecting values.
Prompts can be defined on any Dimension, Measure or Detail object

listed in the Data Tab in Query view.
Note:
You cannot use the operators Is Null and Not Null while creating
prompted filters.
Slide - 55
Using Prompts to Restrict Data
Slide - 56
Prompt Options
Click the Prompt but then next to the Enter Category:

text box, in the query filter definition. The Prompt on
dialog box appears.
The options for creating a prompt are displayed. Several

of the prompt options are selected by default.
Prompt text - You cant buy any text that you want to
prompt the user to select a Category value. All text will
appear each time the user refreshes this document.
Prompt with List of Values useful when you want the

user to view all the values for the object and then select
from those values.
Select only from list this option is useful in preventing

users from typing a value that may not exist in the
database.
Keep last value(s) selected the value that was

selected the last time the report was refreshed is
selected by default in the Prompt list box.
Set default value(s) the value specified as default. If

you select this option, the prompt dialog box expands
and displays all the values returned by the Category
Object. This allows you to specify a value that you would
like to display by default when this document is first run
or refreshed.
Slide - 57
Multiple Filters or Complex Filters

Using logical operators
for multiple conditions
ALL
Circle B:
All rows that
Return the values:
Circle A:
All rows that
Return the values:
(Product) Lines =
Accessories
Store = e-Fashion Dallas
Area C: Rows that

Meet conditions A & B
Use AND / OR operator when you need to use more than one filter.
The AND operator is used when both conditions defined in the two filters must be met for a row to
be returned from the database when you run a query.
The OR operator is used when either one or the other of the conditions defined in the filters must
be met for a row to be returned from the database when you run a query.
The result of combining two or more filters can be visually represented using a Venn diagram as
illustrated.
Slide - 58
Using AND Operator
Slide - 59
Using OR Operator
Slide - 60
Using AND-OR to define complex condition
Key is to set proper priority
Slide - 61
Question
Create a report to display:
Sales Revenue for Florida for Category Bermudas & for Colorado
the Category is Hats. Gloves, Scarves.
Slide - 62
Using Complex Filters
As we said key is Prioritizing Operators
Slide - 63
Q&A
?
Slide - 64
Unit 4
Designing Web
Intelligence Reports
Slide - 65
Unit 4. Designing Web Intelligence Reports
Objective
Working with Web Intelligence Documents
Displaying data in Tables and Charts

Presenting data in Free-Standing cells
Slide - 66
Web Intelligence Document Components

1. One or more Reports
One document may contain several reports, organized as tabs along the bottom
of the window. Reports contain blocks of formatted data as well as text and
graphics. You specify the layout when you create a report, and you can also
change the layout of existing reports.
2. One or more Blocks
A block is a table, Crosstab, or chart that displays information in the report.
3. The Microcube of data returned by the query, also known as the data provider.
The Microcube or date provider contains the actual data that was retrieved from
your corporate database. The data provider is the structure in which the
retrieved data is stored in the document. It contains all the data that you can
display in the report(s) inside the document.
Slide - 67
Application Mode
Application Mode
Features
Data
Create , Edit and Manage Queries that supply data to

reports.
Provides Data Access Toolbox
Reading
View and perform analysis task on report. Opening a

existing report opens it in a reading mode.
Design Mode
Features available in Data & Reading Mode and

additional analysis and formatting features.
User Preferences:
1. General: General preferences
2. Viewing: Document viewing preferences

3. Locale: Preferences for interface and formatting locales and how to use them
4. Drill: Document drill preferences
5. Proxy: Proxy settings for hosts and ports
Slide - 68
Slide - 69
Accessing User Preferences on Webi rich client.
Preferences in BI Launch Pad.
Display Document Summary
Slide - 70
Document Properties Description

Group
Property
Description
Document Information
Created by
The document creator.
Last modified by
The last user to modify the document
Creation date
The date the document was created.
Name
The document name.
Description
The document description.
Keywords
The document keywords.
Locale
The document formatting locale.
Data Tracking
Indicates whether data tracking is activated.
Refresh on open
Tells Web Intelligence to refresh the document when it is opened.
Enhanced Viewing
Optimizes the document appearing for on-screen viewing.
Use query drill
Tells Web Intelligence to drill in query drill mode.
Permanent regional
formatting
Permanently associates the current document locale with the

document.
Document Options
Slide - 71
Document Properties Description

Data Synchronization
Options
Auto-merge dimensions
Tells Web Intelligence to synchronize data providers by

merging dimensions automatically under certain
conditions.
Extend merged dimension

values
Tells Web Intelligence to extend dimension values in

reports with synchronized data providers.
Report Order
Sets the report order in a Report Order document.
Note: The Help Link at the bottom of the pane provides help on each of these options.
Slide - 72
Close the Document Properties pane.
Add a Report to the Document
Right Click & Select

Add Report
Slide - 73
Table Types
1. Vertical Table
2. Horizontal Table
Slide - 74
Displaying Data in Tables and Charts
3. Cross-Tab Table
Slide - 75
Table Types
4. Forms Table
Slide - 76
Viewing Tables in Different Display Modes
Slide - 77
Quick Display mode on the Status Bar.
Quick Display mode is the default display mode.
Use Table Templates and Turn-Into option
Select Table and

Right Click
Slide - 78
Duplicating Tables and Deleting Rows and Columns

Duplicating Tables
Position your cursor by the edge of the horizontal

table. A gray border appears around the table.
Click on the gray border, the entire block is

selected.
Hold down CTRL Key, click the gray border of the

table, and drag the duplicate table to an empty area in
the document zone. Release your mouse.
Delete Table
Right-Click in the gray table border and select remove

from the shortcut menu. Table is deleted.
In the original table, right-click the Margin row. A shortcut

menu displays. Select remove row. The row is deleted.
Close the document without saving the changes.
Slide - 79
Free Standing Cell
Slide - 80
Free-standing cells are single cells that

stand alone in a report.
Used to display information that adds

meaning to your report, such as:
1.
Text comments
2.
Images
3.
Formulas or Calculations
4.
Last Refresh Date
5.
DrillFilter function display the names of

the objects by which the data on a drilled
report is filtered
6.
Page numbers
7.
Anda ton of additional options for us

to choose from
Formatting Date in Free Standing Cell
Saturday, January 21, 2012
Slide - 81
Adding Charts
Slide - 82
Assign Data
Right Click inside chart

and Select Assign Data
Slide - 83
Creating Chart from a table & vice-versa
Right Click inside chart

and Select Turn Into
Slide - 84
Q&A
?
Slide - 85
Unit 5.
Enhancing Reports
Presentation
Slide - 86
Unit 5. Enhancing Reports Presentation
Objectives
Slide - 87
Using Breaks, Calculations and Sorts
Using Report Filters
Ranking Data to see Top or Bottom values
Using Alerter to highlight information
Organizing a report into Sections
Copying data to other Applications
Breaks
Slide - 88
Group Data according to the values you

selected.
Webi separates all the data for each unique

value of the selected variable. It inserts a
blank row or column after each value, which
allows you to easily insert subtotals for the
group of data.
In the extra row that is inserted into the table

after each group, you can easily insert sum
totals for the revenue over the year.
Two main advantage of using Breaks

1. Data is better organized and easy to understand.
2. Subtotals can be now displayed in report.
Slide - 89
Applying break on a dimension (object) automatically sorts the values in ascending order:
In case of numeric values (Eg. Company code) the lowest value is displayed on top and highest at
bottom.
Sort order can be changes anytime.
How to Apply Breaks
Click the Insert/Remove Break button.
Multiple breaks can be inserted by

repeating the same process on another row
or column.
Click inside the column and then

click the Break Button on
Display sub-tab in Analysis Tab
Slide - 90
Remove Breaks
Click a cell in the column or row where
you want to remove a break. click the
Insert/Remove Break button.
Slide - 91
Calculations
Slide - 92
Calculations are available from the drop-down list

of calculations on the Edit Report view toolbar.
Multiple Calculations
Slide - 93
Delete a Calculation
Right-click the table row that contains the Count calculation.
From the drop down menu, select Delete and then Remove Row..
Note: If you were working with a Crosstab or percentages, you would select Remove Column.
Close the document without saving the changes.
Slide - 94
Add & Remove Sort
Slide - 95
Report Filters
1. They only Hide Data and displays just the

information that we are interested in.
2. Data is still present in Document.
3. Can be used at Report or Block Level.
4. Do not impact Query Performance.
Slide - 96
Ranking data to see Top or Bottom values
Ranking can be applied at a:
Database Level by clicking the Add a

database ranking button in the Edit Query
panel (this feature is database specific).
Report level by clicking the Add/Remove

ranking button in the Edit Report Panel.
Applying ranking to data

Display a report showing the three stated
earning the highest sales revenue per year.
Slide - 97
Removing Ranking
To Remove a Ranking
Slide - 98
Click in the State data column.
Select Analysis Tab, From Filters Tab click on

Remove Ranking
Close the document.
Conditions / Alerts
Allow us in highlighting Data that meets specific requirements
using colors.
Example
Highlight City/State/ etc which have margin above US $1.1 million.
An alerter contains five elements:

1. A name
2. An object or cell contents
3. An operator
4. An operand value(s) or another object
5. The conditional formatting
Slide - 99
Alerts Rules
Slide - 100
Alerters can be applied to tables, forms, section cells and free-standing cells.
Alerters cannot be applied to charts.
Business Objects officially supports up to 30 Alerters in a Web Intelligence document.
You can apply those Alerters to a maximum of 20 table columns or rows, free-standing
cells, or section cells on the reports. Business Objects officially supports up to 10 different
Alerters on a single table column or row, free-standing cell, or section cell.
Web Intelligence applies a default format to display the alerter. You can make changes to this
default format. You can insert multiple conditions within an alerter. You can also create an
advanced alerter by inserting a formula.
Creating a Alert
Assign Name and then define the condition for Alert.
Slide - 101
Assign Alert
1. Select the column to which the condition/alert need to be

assigned.
2. Click on Formatting Rules and select the Rule.
Slide - 102
Edit Rule
1. Select Manage Rules form Formatting Rules

Tab.
2. On the next dialog box, select the rule and click
Edit button.
3. The Rule is displayed and can be modified.
Slide - 103
Creating Complex Conditions and Multiple Rules
Click to create additional

rules/conditions (Sub-Alerts)
Click to create a complex

condition
Slide - 104
Sections
Unlike Breaks, Sections can also be used

to Group Data.
Grouped value appears as a header

outside the block, while in breaks they are
within the block.
Break only groups within a block, whereas

sectioning groups the entire report.
Check out the section line, they run across

the width of the report.
Advantages:
Multiple blocks projected from the

same microcube within a single report,
all sub-grouped to the sectioned level.
You can insert subtotals calls
Insert Charts into sections.
Use Fold/Unfold feature
Slide - 105
Creating Sections
Right Click the column and then
select Set as Section
Slide - 106
Display Aggregate in a Free standing cell in Section
Slide - 107
Insert Chart into Section
Slide - 108
Navigating from Section to Section:
Use MAP
Slide - 109
Deleting a Section
Use View Structure Mode.
Select the section divider and press

delete Key.
Slide - 110
Copying Data to other Applications

1. To copy a Table to MS-Clipboard press Ctrl
+ keys or right click and select copy.
2.
Paste it in MS-Excel.
3.
An Image is pasted in Excel.
To get Values use Copy as Text Option
Repeat for Powerpoint
Slide - 111
Q&A
?
Slide - 112
Slide - 113
Unit 6
Formatting Reports
Slide - 114
Unit 6. Formatting Reports

Objective
Document Formatting
Elements that can be formatted using report manager Properties tab.

Modifying Default Report, Table, Cell & Section Properties
Slide - 115
Formatting Charts
Unit 6. Formatting Reports

Displaying the Report Mangers Properties Tab
Documents can be formatted at various levels.
Choose appropriate part of the report and change setting under the Properties Tab.
Click as shown in the picture to format the various elements of Web Intelligence Document:
Report
Cell
Table
Section
Slide - 116
Format a Table
Right Click the Table and select Format Table
Slide - 117
Format Table Dialog Box
Slide - 118
Select Appropriate Tab to Format
General
Border
Appearance
Layout
Format a Cell
Right Click in cell and select Format Cell
Slide - 119
Format Cell Dialog Box
Slide - 120
General
Alignment
Font
Border
Appearance
Format Section, Similar to Table and Cell

Right Click in Section and select Format
Section
Slide - 121
Prepare for PDF Printing
Insert Page Number into the Report Footer.
Check the display in page format.
Make necessary changes like format tables to avoid page breaks.
Slide - 122
Format Charts (Apply Style)
Click the Report Element toolbox. Select the chart to apply a chart style.
The Chart Style tab displays in the Report Element toolbox. Click the arrow beside the
Chart Style button and select the Chart Style from the dropdown menu.
Slide - 123
Format Chart
Right Click on the chart and select Format

Chart.
Slide - 124
Format Chart Dialog Box
Slide - 125
Q&A
?
Slide - 126
Unit 7.
Creating Formulas & Variables
Slide - 127
Unit 9. Creating Formulas and Variable

Objective
Understand Formulas and variables
Using Formulas and Variables
Slide - 128
Formula
Can be a Simple or Complex calculation create by User to display data (string/values) that is not
retrieved by existing objects in the universe.
Formulas can be added in following two ways:
Slide - 129
Type or drag and drop the formula components into the formula toolbar
Use the Formula Editor to build the formula.
Formula editor can be used when you are viewing a web Intelligence document in InfoView, in
interactive mode.
Create a Simple Formula

1. Using the Formula Bar
2. Formula Editor
Slide - 130
Apply a Simple Formula
Slide - 131
Variables
Variable is a formula that users save by a name.
Variable acts like a object in the document and is displayed in the Data tab in the
Report and can be used like any other object.
To display the result of the calculation in multiple block and reports throughout the
web intelligence document.
Advantage of variables is reuse of the formula without having to enter in each time.
Use of Variables:
Helps is re-use of Formula within a document.
Online Help:
Online help can be used for creating formulas and saving them as variables in the
report
Online help contains complete set of functions available for creating formulas.
Slide - 132
Create a Variable
Slide - 133
Using formulas and variables in the Java Report Panel
Create a variable that captures the

users response to a prompt
Create a prompted filter in the report
Slide - 134
Q&A
?
Slide - 135
Unit 8
Synchronizing Data
Slide - 136
Unit 8. Synchronizing Data

Objectives:
Synchronizing data from multiple data sources
Creating multiple queries in a document
Synchronizing data with merged dimensions
Slide - 137

Working with multiple data providers
When you run a query against a single data source, the results of the query are stored in the
documents micro cube, also known as the data provider. Each data provider only holds data from
a single data source.
This is very useful when you want to include data from several sources in a single document
irrespective of the format of the original source. It also means you can present related information
in a way that helps you compare or analyze data more meaningfully.
Once the basic report is built with blocks of related data, you can compare and contrast the
information in a single table, add calculations across data sources, create new variables and
develop the analysis further.
Slide - 138

The following graphic is
illustration of this concept:
an
Blocks 1 and 2 are different views of the

data provider created by a single query
using the eFashion universe.
Block 3 displays a view of the data

provider created by a second query
using the eFashion universe. Used in
the same document as Blocks 1 and 2,
this is an example of combining data
from multiple queries using a single
universe.
Block 4 displays a view of the data

provider created by a second query
using the eStaff universe,. Displayed
with blocks 1,2 and 3, views of data from
the eFashion universe, this is an
example of combining data from multiple
queries on multiple universes.
Slide - 139
eFashion
Universe
eStaff
Universe

What is data synchronization?
This Unit describes how to synchronize

multiple data providers in a Web Intelligence
report by merging them on common dimensions.
After merging common dimensions you can
place dimensions from different data providers
in the same block.
Merged dimensions and data synchronization
enormously increase the power and flexibility of
Web Intelligence by allowing you to synthesize
data from different sources in the same report,
rather than simply including the data.
Synchronization is the term used to describe

the merging of data from multiple data
sources into a single block in a report.
The graphic illustrates how data from more

than
one
source
is
combined
in
synchronized blocks in the same document.
Block 1 is created by combining data from two

different data providers which contain the results
of queries using the eFashion universe.
Block 2 is created by combining data from data

providers which contain the results of queries
using the eFashion and eStaff universes
Slide - 140
eFashion
Universe
eStaff
Universe

In this unit, you will learn to project data from
several queries into multiple data blocks in a
Web Intelligence document.
After completing this unit you will be able to:
Project data from a single query in different

report blocks.
Project data from more than one query

using a single universe.
Set options to automatically

dimensions with the same name.
Project data from queries using multiple

universes.
merge
Projecting data from a single query

in different blocks
In this example, you will create a document

to analyze the Sales revenue figures for the
last three years and display the Sales
revenue per store:
Block 1 will show the sales revenue of the

stores in the eFashion database for different
years. Block 2 will show only a subset of
this information from the same query.
Slide - 141
eFashion
Universe

To project data from a single query in
multiple blocks
Select the following objects in Query:

Year, State, Lines & Sales Revenue Objects.
Click Run Query.
Delete the vertical table that is created by

default.
Prepare the first view Block as shown suing

Year & Sales Revenue Object.
For Second View Block hold down the Ctrl key

and click on State & Sales revenue and drop
the objects on the report section. Second
Block is created.
Similarly create third Block.
Block 1: Annual Sales Revenue.
Block 2: Revenue for every State.
Block 3: Revenue from each product line.
Save the document to Favorites as XX_Multi

Block 1.
Slide - 142

Projecting data from multiple queries
using a single universe
Now you are going to add a third block of data

to the report. This time you will add a new
query to retrieve new data from the eFashion
universe.
Continue working with the same document.
To project data from two queries in multiple

blocks
Click Edit Query to begin adding the

second query.
When in Edit Query view, click the Add

Query button on the toolbar.
The Universe dialog box displays.
Select eFashion as the data source for the

second query.
Click OK.
A second Edit Query view appears. Note that

at the bottom of the panel, there are two tabs
now: Query 1 and Query 2. You can use
these tabs to toggle back and forth between
the two query definitions.
Slide - 143
In the Query 2 tab, move the store name and

Margin objects into the Result Objects pane.
Click the Properties tab.
The Query Properties panel for Query 2

displays.
In the Name field, type Margin query and

press the Return key to replace the default
name of this query.
Click the Query 1 tab.
The Edit Query view switches to the query

definition for Query 1.
Right-click the Query 1 tab.
Select Rename Query from the drop-down

menu.
In the Name field, type Revenue query and

name of the first query as well.
Click the drop-down arrow next to the Run

Queries button.
Slide - 144
The drop-down menu allows you to decide if

you want to run only one of the queries in the
document, or all of them at once.
Select Margin query from the Run Queries

drop-down menu.
The New Query dialog box displays. The

options to include the data from the new query in
the report are listed.
In the New Query dialog box, Select the Insert a

table in the current report option and click OK.
Web Intelligence executes both queries and

projects the new data in a new table in the
report.
Note: The new table may be positioned

anywhere in the report, even on top of the
existing tables. Scroll in the report to find
where the new table has been projected, then
drag and drop it to the appropriate blank space in
the report.
The objects you selected in the Margin query

appear in the Edit Report Data tab..
Slide - 145
Click + next to the Store name object in the

Data tab. The folder expands.
Expanded, the folder displays two Store

name objects. This indicates that the same
object has been used in two different
queries, once in the Margin query and
once in the Revenue query. The top-level
Store name object is identified by a doublecubed, blue dimension icon, indicating that
the two have been automatically merged to
create a single dimension object.
Now you are ready to project the data from

both queries into a single block in the
report.
Slide - 146

To project data from a merged
dimension into a single block
Insert a new report in the document.
In the Data tab, Click the Store named merged

object, hold down the Ctrl key and
Click the
objects.
Drag all objects and drop them into the new

report.
The aggregate data to calculate sales

revenue per store and margin per store has
been retrieved by two different queries, but
you are still able to combine both in a
single block of data.
Save the documents

XX_Multi Block 2.
Slide - 147
Sales
Revenue
to
and
Margin
favorites
as

About automatically merged dimensions
In the exercise above, you used the same object in two different queries (Store name). When you
ran the queries, Web Intelligence automatically merged the two instances of the same object and
created a combined object, identified by the double-cubed dimension icon, as shown here.
Web intelligence automatically merges dimension only when the same object is used in more than
one query in a document. Ideally, a well-designed universe does not have two different objects of
the same name, or of different data types, but if this does occur and you use them in more than
one query in a document, Web Intelligence will automatically merge them.
If you do not want Web Intelligence to automatically merge multiple instances of the same object
in a single document, you can de-select the Auto-merge dimensions option at the document level,
as described below.
Slide - 148

To change the automatic merge dimension setting
In the Java Report Panel Edit Report view, right-click

anywhere outside of the report blocks in the document.
From the drop-down

Properties.
The Document Properties pane opens to the right of the

Edit Report view.
The Auto-merge dimensions option tells Web

Intelligence whether it should automatically merge a
dimension when the same object is used in more than
one query in a single document. For the purposes of
this exercise, leave the option selected.
If you de-select this option, your change will not be

taken into account until the next time you create a
document with two queries that references the same
object.
Slide - 149
menu,
select
Document

Projecting data from queries using
Multiple Universes
Your first report now shows sales revenue

and margin for each of the stores in two
blocks of data. Your second report shows
data from both queries in a single block,
because you have been able to project the
automatically merged dimension into a
column in the table.
So far, you have used data only from the

eFashion universe to produce the
blocks in both reports. These blocks are
views of data providers with data retrieved
using the eFashion universe.
Now you are going to add a second block

to Report 2 using data retrieved from a
different universe. This block will show
the number of employees that work at each
store. This can help you analyze how a
stores staffing level affects the sales
revenue.
In this next step, you add a query to the

document using the eStaff universe.
Continue working with the document from

the previous exercise.
Slide - 150
eFashion
Universe
eStaff
Universe

To display data from two data
sources in multiple blocks
Make sure the Multi Block 2 document is

still open in the Java Report Panel.
Click Edit Query to begin adding the second

query.
While in the Edit Query view, click the Add

Query button on the toolbar.
The Universe dialog box displays.
Select eStaff as the data source for the

third query.
Click OK.
A third Edit Query view appears. Note that

at the bottom of the panel, These are three
tabs now: Revenue query, Margin query
and Query 3. You can use these tabs to
toggle back and forth between the three
query definitions.
Slide - 151
In the Query 3 tab, move the Store and

Number of Employees objects into the Result
Objects pane.
Click the Properties tab.
In the Name field, type Employee query and

name of the first query as well.
Click the drop-down arrow next to the Run

Queries button.
Select Employee query.
In the New Query dialog box, this time select

the Include the results objects without
generating a table option and click OK.
The Store and Number of Employees objects

in the Employee query, from the eStaff
universe, now appear in the Data tab.
Slide - 152
In Report2, hold down the Ctrl key to select the Number of Employees and Store object from the
Data tab and then drag them to position them next to the existing table in the document zone.
A new table is inserted next to the existing table and the table from the Employee query is
projected into the new table:
Save the document to Favorites as XX_Multi Block 3.
We have now displayed data from two different data sources in two tables side-by-side in the
report. These tables allow you to compare each stores margin with the number of employees per
store.
However, it is clear that both data sources, eFashion and eStaff, contain data concerning the same
stores . Next we cover how to show the same data but this time in a single block of data, or a
single table. To do this, we will manually merge two dimension objects, so that you can project the
store names in a single column in the table.
This is known as synchronizing data.
Slide - 153

In the previous exercise, we have seen how to project data from multiple queries in a document,
from both single and multiple universes.
So far, we have not tried to merge data from different data sources into a single block (table
or chart). In order to do this, you need to synchronize the data by merging dimensions. Because
the data comes from two different data providers, if you do not synchronize the dimensions
with similar data, Web Intelligence cannot know in what way the data is related and your report
will not show relevant results.
We will cover
Explain why it is important to merge dimensions that retrieve related data.
Synchronize data by manually merging dimensions.
List rules that are important to be aware of when merging dimensions.
Slide - 154

What happens when dimensions are not
synchronized
In the previous exercise, we retrieved data
concerning stores, but you used two dimension
objects that had different names, even though they
retrieved similar data:
the Store name object in the Revenue query

and the Margin query, from the eFashion
universe.
the Store object in the Employee query, from

the eStaff universe.
Because the dimension object do not have the

exact same name, Web Intelligence cannot
automatically merge the dimensions. if you try to
combine data from the two objects in a single block,
Web Intelligence will not automatically be able to
interpret the relationship between them.
The scenario, you will project data from both the
eFashion queries and the eStaff query into a
single block, but because you have not defined the
relationship between two objects concerning store
names, the data will not be meaningful.
Slide - 155
Insert a new report in the document.
From the Report Manager Data tab, click the

merged Store name object, hold down the Ctrl
key and then click Sales revenue and Number of
Employees objects.
The merged Store name object and the Sales

revenue object are from the same universe and
data source (eFashion). The Number of
Employees object is from a different universe
and data source (eStaff).
Drag the objects and drop them into the blank

report space.
The data retrieved by these objects is projected

automatically into a vertical table. Notice that
every store appears to have 143 employees, yet
this is in fact the total number of employees from
all stores:
The block is projecting data from un-synchronized queries. Although the names of the eFashion
stores are in fact the same, Web Intelligence does not make any assumptions, and it does not
know how to properly interpret the data. Because Store name and Sales revenue comes from the
same universe and the data source, the sales revenue data is aggregated correctly. but not the
number of employees data. Save the document to Favorites as XX_Multi Block 4.
Slide - 156

Synchronizing
queries
merging dimensions.
by
manually
You can define the relationship between objects

from different universes by manually merging the
dimensions in order to synchronize the data they
retrieve. Merging dimensions manually allows you to
identify the objects that retrieve common data in
both queries. Once the merged dimension is in
place, you can compare information between the
queries more accurately.
To manually merge dimensions with different names
Continue working with the same document
In the Java Report Panel Edit Report view, ensure

the Reporting toolbar is displayed.
In the Data tab, click the Store object.
The Store object, which was an object you used in

the Employee query, is highlighted:
Slide - 157
Note that all the dimension objects listed in the Data tab are suddenly displayed in italics.
These objects are highlighted in italics because they are all the same type of object as the Store
object: that is, they are all dimension objects. Web Intelligence indicates that you could choose to
merge the selected object with any of the other dimension objects in the documents queries.
We want to merge the Store object with the Store name objects used in the queries we built using
the eFashion universe. The names of the objects are slight different, but they obviously retrieve
the same type of data.
Click the Merge dimensions

button on the Reporting toolbar.
The Merge Dimensions dialog

box displays.
The dimensions that are available

to be merged appear in the top
zone
of
this
dialog
box,
categorized by the query that they
belong to.
Below and to the left is a list of the

merged dimensions that already
exist in the document: in this
example, we see Store name,
which is a dimension that was
automatically merged when we
used Store name from eFashion in
two different queries.
Slide - 158
In the Employee query list, click the

Store dimension.
Click Store name

dimension list.
Click the Values button to view all the

values returned by this dimensions.
The Merge dimensions dialog box

expands to display all the values
returned by these dimensions. In this
example, the values are exactly the same.
Depending on the dimension objects you
are merging, the values may not be
identical, but they should be of a
similar type.
Click the Merge button.
The Store dimension has been

positioned as one of the objects included
in the merged Store name object.
Click Ok to close the dialog box.
Slide - 159
in
the
Merged
Now, you see in the Data tab

that the merged Store name
dimension includes the Store
object
from
the
eStaff
universe.
This is known as synchronizing

data using merged dimensions
When you project data into a

block using this merged
Store name dimension, it
retrieves
data
from
the
Employee query as well, using
the eStaff universe and data
source.
When you merge dimensions,

Web Intelligence creates a
new dimension that retrieves
all the values from all the
original dimensions that make
up the merged dimension.
The report should appear like

this:
Save the document to Favorites

as XX_Multi Block 5.
Slide - 160

Some rules about synchronizing with merged dimensions
LINK
Merging dimensions is the process of creating a link between two queries based on an
object with common values so that in effect the objects become one.
There are a number of rules to remember when merging dimensions from multiple
queries:
You can only link on dimension objects, for example, Store name and Store.
The dimension objects do not have to have the same names.
The dimension objects must have a common data format. For example, if one object is
character based and the other numeric you cannot link the objects.
Although the actual values do not have to be the same, all data held in a data provider is
case sensitive, and therefore any common values must be in the same case.
Slide - 161
The format of the values must be the same. For example, FY06 and 2006 would be seen as
two separate values. Extra spaces in some values can also mean that the objects cannot
be merged.
Any number of queries can be linked by common dimension objects.
Any number of dimension objects can be merged between two queries.
A measure object can be synchronized successfully only to the lowest level of detail that is
common between the two different data sources. For example, a query with Year can be
linked with another query with Year and Month. However, the synchronized block is only
able to display data at the Year level.
Slide - 162
Q&A
?
Slide - 163
Unit 9.
Analyzing Data
Slide - 164
Unit 9. Analyzing Data

Objectives:
Analyzing the data cube
Drilling in the Java Report Panel
Setting Web Intelligence drill options
Slide - 165
Analyzing the Data Cube

Drill mode is a feature that allows you to view data from different from different levels of details and
zoom in on different trends
About Web Intelligence Data

Cube
The data that is returned by a query is
stored in the documents data provider.
It is convenient to visualize the
standard data as being organized as a
cube. In documents data is displayed
as tables two dimensional view of the
Data cube.
Each column in table represents a axis

in the cube. You can edit the document
by swapping and manipulating the
data within the cube on any axis.
When you swap or change data
between different axes, the new result
is again projected as a flat table in the
resulting document.
Data stored in cube allows you to create a report that that corresponds to your business needs
without having to send another query to the database.
If you want to add information to the document that is not in the data provider, then you must add
the object and run the query again to get the new information.
Slide - 166
Scope of Analysis
The scope of analysis for a query is extra data that

you can retrieve from the database to give more
details on the results returned by each of the objects
in a query. This extra data does not appear in the
initial result report, but it remains available in the data
cube, so you can pull this data in to the report to allow
you to access more detail at any time. This process of
refining the data to lower levels of detail is called
drilling down on an object.
In the universe, the scope of analysis corresponds to

the hierarchical levels below the object selected for a
query. For example, a scope of analysis of one level
down for the object Year, would include the object
Quarter, which appears immediately under Year.
You can set this level when you build a query. It

allows objects lower down the hierarchy to be
included in the query, without them appearing in the
Results Objects pane. The hierarchies in a universe
allow you to choose your scope of analysis, and
correspondingly the level of drill available.
Time
Sales Revenue
Year
Quarter
Month
Week
Slide - 167
In the Java Report Panel and in Web Intelligence Rich

Client, you can also create a custom scope of analysis
by selecting specific dimensions for the Scope of
Analysis pane.
Store
Stores
City
State
Drilling
Building a drillable document
You can build a drillable document if your administrator has authorized your user account to create
document using drill mode.
To build a drillable document:
Create a new document using eFashion universe and use the following objects.
Year, State and Sales revenue.
In the Edit Query view, slick the Show/Hide Scope of Analysis Pane button.
The Scope of Analysis zone opens just below the Query Filters zone in the Edit Query view.
Resize the Query Filter pane and the Scope of Analysis pane by clicking and dragging the
borders so that you can visit the objects displayed there. By default, the level of the scope of
analysis for this query is set to None.
The Scope of Analysis pane displays the hierarchical dimension objects from the Result
Object pane.
Slide - 168
Drilling
Note: The object included in the Scope of Analysis are the dimension objects in your Results Objects
pane that are part of a hierarchy in the universe.
Click the Hierarchies option located below the Data tab pane. The Hierarchies view shows all the
predefined hierarchies that have been defined in the eFashion universe. Fox example, all the
dimension objects that have been linked in the Time period hierarchy appear under time period.
Expand the other hierarchy folders to see how the universe objects are organized in hierarchies.
In the Scope of Analysis pane, click the drop-down arrow to display the menu options. A list of
levels appears in the drop-down list.
Select Three levels from the scope of Analysis drop-down list. All the objects that are three levels
down in the Time period hierarchy and in the store hierarchy automatically appear in the Scope of
Analysis pane.
When you run the query, only the values for the Year, State and Sales revenue will appear in the
table that is generated. The remaining objects will appear in the Data tab, but they will not be projected
into the report automatically.
Slide - 169
Slide - 170
Drilling & Snapshot
Slide - 171
Drilling
As you are drilling, a new toolbar appears at the top of the document, called the Drill Toolbar.
You are now going to use the Drill Toolbar to drill across at the same level of detail.
NOTE: An arrow displays next to the drilled-down data. To drill back up, simply click on the arrow
beside each cell.
Slide - 172

To drill across data in a hierarchy
Continue from the previous exercise.
Click the drop-down arrow in the drill toolbar

besides California to view the other values you
can drill across to.
From the drop-down list, select Texas as the

value that you would like to drill across to.
The Crosstab displays data concerning the cities

in the state of Texas.
To drill down two hierarchies at once:
Continue from the previous exercise.
Position your cursor over the Sales revenue

amount for Dallas in 2004. A tooltip, Drill down to
Store name/Quarter, appears to indicate that by
clicking in the body of the table, you drill down to
both the Store name level and the Quarter level
in both hierarchies at once.
Click the Dallas 2004 Sales Revenue cell in the

body of the Crosstab to drill down both to Store
and Time period hierarchies contained in the
report.
The Sales revenue for the eFashion Dallas

store is displayed at the Quarter level.
Slide - 173

To edit the Scope of Analysis
When you are drilling on a hierarchy, you may discover

that you need to drill to a lower level than you had
previously allowed for when setting the scope of analysis.
Edit the scope of analysis by returning to the Edit Query
view an changing the level of detail that you defined
in the Scope of Analysis pane.
Taking a snapshot of the drill report
Version of Drilled results can be saved by taking a

snapshot. When you take a snapshot, a new report is
inserted after your last report in the document. You
can continue working in your current report, but can
switch to the snapshot by clicking the new report tab.
To take a snapshot of your analysis:
Continue from the previous exercise. Click the Take

Snapshot of drilled Report button on the Report toolbar.
A copy of the report is inserted in the document.
Note: An additional report tab displays at the bottom of

the report.
Click the new Report 1 (1) report tab to view the copied
report. A copy of the table is inserted in the snapshot
report but without the drillable hyperlinks
Save the document within your Favorites as XX_Drill

down
Slide - 174
Setting Web Intelligence Drill Options

Drilling on reports lets you look deeper
into data to discover the details behind a
good or bad summary result displayed on
a table, chart, or section. Before you begin
a drill session, you can set your drill options
in InfoView to specify how reports will change
each time you drill.
Setting general
InfoView:
drill
options
in
Click Preferences on the InfoView toolbar.
Click Web Intelligence Preferences to

display the Web Intelligence options.
Select the drill options under Drill options

and Start drill session.
Slide - 175

Set drill preferences using the following table as guidelines:
Option
Slide - 176
Description
Start drill session on

existing report
option
When you select Start drill session on existing report, the current report becomes
drillable when you start drill mode. When you end drill mode, the report displays the
drilled values.
Start drill session on

a duplicate report
option
When you select Start drill on a duplicate report, Web Intelligence creates a duplicate
of the current report when you start drill mode, and you drill on the duplicate. This allows
you to compare the results of the original report with the results you discover during your
drill analysis.
Prompt when drill

requires additional
data option
When you drill the results displayed on a Web Intelligence report, you may want to drill to
higher- or lower-level information that isnt included in the scope of analysis for the
document. When this is the case, Web Intelligence needs to run a new query to retrieve
the additional data from the data source. Since queries on large selections of data may
take a long time to be completed, you can choose to be prompted with a message every
time a new query is necessary. The prompt message asks you whether you want to run
the additional query or not. In addition, the prompt lets you apply filters to the extra
dimensions you include in the new query. This means you can restrict the size of the
query to only the data necessary for your analysis. You need permission from your
administrator to drill out of the scope of analysis during a drill session.

Synchronize drill on
report blocks option
When you select the Synchronize drill on all report blocks option, the display of all blocks
changes to correspond with your drill actions. For example, if you drill down on a block from
year to quarter, and your report also contains a chart showing data by year, the chart display
also changes to display data by quarter. If you do not select the option, only the drilled block
changes in response to drill actions.
Hide drill toolbar option
When you drill on a value displayed on a report, the Drill toolbar appears and displays the
value on which you drilled. The value displayed on the toolbar filters the results displayed on
the drilled report.
For example, if you drill on year 2003, the results displayed on the drilled table are Q1, Q2,
Q3, and Q4 for year 2003. This means that the quarterly values you drilled to are filtered by
2003.
Click OK to accept the new settings.
Return to the InfoView Home Page.
The next time you create a Web Intelligence documents an define the scope of analysis for drilling,
the settings you define in the InfoView preferences page will apply, regardless of the Web Intelligence
report panel you have chosen for crating documents
Slide - 177

Using Query Drill
When you create, edit, or view a Web Intelligence document, you can set Web Intelligence to drill
in query drill mode, which behaves differently from the standard drill mode described so far in this
unit. When you activate query drill, Web Intelligence drills by modifying the underlying query
(adding and removing dimensions and query filters) in addition to applying drill filters.
When can you use Query drill?
You use query drill when your report contains aggregate measures calculated at the database
level. It is designed in particular to provide a drill mode adapted to databases such as Oracle 9i
OLAP, which contain aggregate functions that Web Intelligence either does not support, or cannot
calculate accurately at the report level during a drill session.
The kinds of aggregate functions that are candidates for drilling in query drill mode are:
percentages, distinct counts, ranks, standard deviations and variances, running aggregates, lead
and lag functions. Because query drill modifies the query at each drill operation, it ensures that
these aggregates are recalculated by the server each time you drill.
Query drill is also useful for reducing the amount of data that Web Intelligence must store locally
during a drill session. Because query drill reduces the scope of analysis when you drill up, Web
Intelligence is able to purge unnecessary data.
Slide - 178

To set Query drill
Create a new document or edit an existing

document in the Java Report Panel.
Display the Document Properties pane.
In the Document Options zone, select the

Use query drill option.
Slide - 179
Q&A
?
Slide - 180
Unit 10
Managing and Sharing

Documents
Slide - 181
Unit 10. Managing and Sharing Documents

Objectives:
Slide - 182
Scheduling Documents
Managing Documents in BI Launch Pad
Viewing Documents in BI Launch Pad
Sharing Documents
Setting BI Launch Pad Preferences.
Sharing Documents
For Sharing documents with other InfoView users, you can directly sent your document to their
InfoView Inbox folder. Or you can also choose to save them as Public Documents in the
Corporate Repository if you are authorized to do the same by BOE administrator.
If the colleagues you want to share with are not InfoView users than you an save your reports in
MS-Excel or Adobe PDF so that they can easily view and print them.
We will cover
Send documents to other InfoView Users
Save documents as a Public Documents
Save a document in PDF or Excel spreadsheet format.
Add discussions to a document
Add a document from your computer.
Slide - 183
Sharing Documents
For Sharing documents with other InfoView users, you can either sent your document to users
Inbox, or save it as a Public Documents, if you are authorized to do so.
1. Sending a Document to a users Inbox

2. Saving in Public Folders
3. E-mail it to users outside BOBJ environment
4. Schedule the documents to be delivered automatically.
Slide - 184
Q&A
?
Slide - 185
Thank You
Slide - 186

AA BO40 SP02 WebIntelligencev1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AA BO40 SP02 WebIntelligencev1.0

Uploaded by

Copyright:

Available Formats

SAP BO-4.

BusinessObjects 4.0 SP02 Web Intelligence

BI Launch Pad Portal

1. Introduction to Web Intelligence

Core Functionality & Concept

2. Create Web Intelligence Documents with Queries

Querying with Web Intelligence

Modify a Document Query

Working in the Query Panel

Query Properties & Data Tab

Using prompts to restrict data

Working with Web Intelligence Documents

Displaying data in Tables and Charts

Presenting data in Free-Standing cells

5. Enhancing the Presentation of Reports

Using Breaks, Calculations, Sorts and Report filters

Ranking data to see top or bottom values, Using Alerts

Organizing a report into sections

Copying data to other applications

Creating Formulas and Variables

Formulas and Variables

8. Using Multiple Data Sources

Synchronizing Data from Multiple Data Sources

Creating Multiple Queries in a Document

Synchronizing Data with Merged Dimensions

Using a Personal Data Provider

Analyzing the Data Cube

Drilling in an Interactive Analysis Document

BusinessObjects 4.0 SP02 Web Intelligence

Managing Documents in BI Launch Pad

Viewing Documents in BI Launch Pad

Setting BI Launch Pad Preferences

BusinessObjects 4.0 SP02 Web Intelligence

BusinessObjects 4.0 SP02 Web Intelligence

The BOE technical architecture is

BusinessObjects 4.0 SP02 Web Intelligence

BusinessObjects 4.0 SP02 Web Intelligence

Decision Tree Select Right Tool

BusinessObjects 4.0 SP02 Web Intelligence

Client Tools for Biz Users and Report Designers

BusinessObjects 4.0 SP02 Web Intelligence

Tools for Data Managers

BusinessObjects 4.0 SP02 Web Intelligence

Tools for Administrator

BusinessObjects 4.0 SP02 Web Intelligence

BI Launch Pad User Interface

BusinessObjects 4.0 SP02 Web Intelligence

BI Launch Pad Document Tab

BusinessObjects 4.0 SP02 Web Intelligence

BusinessObjects 4.0 SP02 Web Intelligence

Folders & Categories

BusinessObjects 4.0 SP02 Web Intelligence

Searching in Launch Pad

BusinessObjects 4.0 SP02 Web Intelligence

Web Intelligence Rich Client

BusinessObjects 4.0 SP02 Web Intelligence

BusinessObjects 4.0 SP02 Web Intelligence

BusinessObjects 4.0 SP02 Web Intelligence

Unit Presents Key Concepts and Vocabulary required to understand Web

We will cover the following Concepts.

BusinessObjects 4.0 SP02 Web Intelligence

Interactive Analysis Core Functionality

Access, Analyze and

Query your organizations