Designer

Cognizant Data Warehouse Solution Center
BusinessObjects Training
Data Warehouse & Business Intelligence Practice
Creative MindsInnovative Approach
Course Outline
Universe Designer
Creating a Universe
Resolving Loops
Managing Universe
Aggregate Awareness
Hands On
Using @ Functions
Setting Hierarchy & LOV
Import\Export of Universe
Locking a Universe
Setting Object Security level
Mapping Table
Copyright 2002 Cognizant Technology Solutions
Universe
Universe Designer
Designer
Extracting information from Database

Many different attempts have been made to
resolve issues surrounding reporting:
The Bureau Approach:
MIS
The SQL Education

Approach:
MIS
SQL
End Users
SQL
End Users
The Business Objects Solution
Corporate Database
Information access
through a Semantic
Layer
Database and Security

Design
Sales
Stock
Finance
Universe Design
End-User Needs
Ease of use
Reliability
Integrated reporting and
analysis tools
IS Needs
Security and control
Maintainability
Cost-effective set-up
Enterprise-wide
interoperability
Universe
A Universe is a semantic layer between
Database and end users.
A Universe is a business-oriented mapping of
the data structure found in databases: tables,
columns, joins, etc.
A Universe can represent any specific
application, system, or group of users. For
example, a universe can relate to a department in
a company such as marketing or accounting.
A Universe can also pertain to a section within a
department or just about any set of organized
procedures such as a payroll or inventory system.
A Universe consists of a set of objects, grouped by
Advantages of using Universe
Business
Knowledge
Users can access data in an easy

way using their own terminology
Users can make queries without

knowing SQL
The organization has a shared

business content
The Universe Development Process
Prepare
Know the data
source
HR on
Sybase
Financials
on Oracle
Analyze
Identify the needs
of the end user
population
Plan
Design the
universe(s)
The Universe Development Process

Implement
Create the universe(s)
Test
Using a test team (including
end users)
Deploy
Distribute the universe to
end users
Evolve
Adapt and extend
universe over time
Creating a Universe
Define the Parameters

Resolve the Loops
Insert Tables
Create Classes and Objects
Make the Joins
Set up Hierarchies
10
Creating a Universe
To begin creating a new universe:
Select File, New
11
Setting up Universe Parameters

Definition Tab: name,
description and connection to
the database
Summary Tab: author and

statistics about the universe
Strategies Tab: internal or

personal wizards to make
creating a universe easier
Controls Tab: manages

access and control of resources
SQL Tab: queries and SQL
parameters
Links Tab: enables dynamic
links with other universes
12

The Summary tab displays general information
about the universe
13

Strategies Tab
Provides automated
strategies for:
Creating objects
Setting joins
The Table browser
listing
14

Controls Tab
These allow you to limit
the size of results and
restrict the time allowed
for executing queries
The Supervisor
can change these
parameters for
specific groups or
users
15

SQL Tab
SQL parameters
are used to define
the limits of the
SQL that may be
generated by the
universe
The Supervisor
can change these
parameters for
specific groups
and users
16

Link Tab
Enables
dynamic links
with other
universes
17
Inserting Tables
Use the Table browser:
Double-click on the background of the
Structure
Click on
Choose Insert, Tables from the menu
The Table browser displays all the

tables and views of the database
You can select multiple tables using
the Shift key or Ctrl key
18
Making Joins
What do joins achieve in SQL?
19
Making Joins
What is Join?
A join is a condition that restricts the result set of a
query
There are several different kinds of join:
Equi-join (otherwise known as a standard or

inner join)
Outer join
Theta join
Self join
20
Making Joins
Equi - Join
21
Making Joins
Creating a Join in Designer
A join can be entered manually using two methods:
Graphically
With the menu option

Insert, Joins and the Edit
Join box
To delete a join, click on the join line and press Delete
22
Making Joins
Automatic Join Detection
The Strategy for automatic detection of joins is

based on common column names between tables
You can choose from one of three specific

strategies for join detection:
Smart Matching Column Names (no key info.)
All Matching Column Names
All Matching Numeric Column Names

23
Making Joins
Theta Join
A theta join contains an expression that is based on
something other than equality:
Theta Join
Theta Join Result Set:
24
Making Joins
Creating Theta Join
A theta join is created by converting an existing equijoin
CTRL-CLICK
25
Making Joins
Self Restricting Join
This is not really a join at all. It is a method used to set
a restriction on a table in the universe Structure.
26
Making Joins
Adding Cardinalities
Manually using the Edit Join dialog box
Automatically using
(but can take a long time)
27
Check Integrity
Always check integrity after defining joins
28
Resolving Loops
What is a loop?
A loop exists when the joins between tables form a continuous

path
29
Resolving Loops
Cardinality Detection
Click Detect Cardinalities:
30
Resolving Loops
What is an Alias?
An Alias is an exact duplicate of the original table

with a new name. The data in the table is exactly
the same.
The Alias is used only to resolve the loop in the
structure of the universe. There is no impact on
the schema of the database
Easy to define
Easy to maintain
Easy to use
31
Resolving Loops
When to Alias?
A loop with a single
lookup table should be
resolved by an alias
A lookup table can be

identified by its
cardinality
N
1
A lookup table only has

the one end of joins
attached to it
Alias needed here
32
Resolving Loops
How to Alias?
Designer routines
detect loops and
candidates for
aliases
Break the loop by
creating an alias of
the lookup table for
each side of the loop
Some DBs require a
separate alias for
both sides of the
loop
33
Resolving Loops
Using aliases in Multi star situation
Normalized dimensions are not amenable to loop
resolution using Aliases
Candidates for Aliases
34
Resolving Loops
If you try to resolve the loop using Aliases:
All candidates for

there Aliases
is still a loop
35
Resolving Loops
Resolving Loops Using Contexts
There are two possible routes to

link Clients with Models:
Working with rentals

Working with sales
36
Resolving Loops
Resolving Loops Using Contexts
Rental context
Sale context
37
Resolving Loops
Sequence for resolving loops
1. Detect and set cardinality on all joins

2. Use Detect Aliases to detect candidates for aliases
3. Insert all required alias tables and joins
4. Use Detect Contexts to detect candidates for
contexts
5. Create the required contexts
6. Test in the User module
38
Managing
Managing Universe
Universe
39
Managing Universes
Reason for Universe Maintenance
New tables added to database
Tables deleted, changed or renamed in database
Users request new classes or objects
Note: Your primary concern when you introduce a
new version of a universe should be what
effect it will have on existing end user
reports
Tip: Do not distribute new versions of universes
too frequently!
40
Managing Universes
Changes to target database
The implications of modifying the underlying database
for BusinessObjects universes varies in severity:
No Impact:
Adding new
columns
Adding new tables
Severe Impact:
Renaming/moving database
Changing existing column

and table names
Deleting tables and columns
41
Managing Universes
Detecting changes to database
Choose View, Refresh
Structure
Changed tables are
highlighted in the Structure

A message on the screen
indicates that tables have
been deleted
42
Managing Universes
Effect of changes to existing Objects
Changes to existing Objects in a Universe can have an
impact on existing Documents created from the
Universe:
No Impact:
Redefining Object SQL
Impact:
Deleting an existing
Object
Renaming an Object
Copying to different Class Deleting and then
recreating an object with
Moving in same Class or to
exactly the same
a different Class
definition
Adding new Objects
43
Managing Universes
Adding new tables to Universe
The workflow is:
Add tables to the universe structure

Insert joins and set cardinalities
Delete existing contexts
Detect aliases
Detect contexts
Create new objects
Set up hierarchies
44
Managing Universes
Making maintenance more efficient
Maintenance can be made easier by:
Copying and pasting objects between universes
Linking universes
Embedding the structure, classes and objects from one
universe to another
Including universes
Copying the structure, classes and objects from one
universe to another
45
Managing Universes
Copy and pasting Objects
You can copy
objects from
one universe
to another
Both
universes
must have
the same
connection
46
Managing Universes
Linking Universe
Linking can mean reduced maintenance but there are
limitations
Universe A
Universe A
Universe B
47
Managing Universes
Two approaches to linking
Kernel approach
Master approach
48
Managing Universes
Kernel Approach
Kernel
Kernel
Human Resources
Kernel
Kernel
Motors2000
Staff
Kernel
Kernel
+
49
Managing Universes
Master Approach
Master
Master
Master
Master
Human Resources
HR
and
Motors2000
Motors2000
Master
Master
50
Managing Universes
Making a link
Click
and click on the Links tab
Click Add Link...
Choose universe to
link and click Open
51
Managing Universes
The derived Universe
The linked universe structure and objects cannot be

edited in the derived universe
The linked universe should be treated as though they
were new tables inserted in the derived universe. The
same procedure should be applied
52
Managing Universes
Including Universes
Including a Universe COPIES structure and objects to
the derived universe:
Universe A
Everything
from
Universe A
Universe A
Universe B
53
Aggregate
Aggregate Awareness
Awareness
54
Aggregate Awareness
What is aggregate awareness?
Some databases have Summary Tables which contain
figures aggregated to a high level.
These are used to speed up queries which contain
statistics (for example, Revenue) reported at, for
instance, year rather than event level.
Aggregate Awareness is the BusinessObjects process by
which these higher level aggregates are incorporated
into a universe.
55
Aggregate Awareness
Summary Tables
Check the columns in the Summary Table:
Foreign Key columns are
used for the joins
The other columns relate to

objects that require
@AggregateAware
definitions
Note that Summary Tables without Foreign Keys do not
need joins - they can be free floating tables.
56
Aggregate Awareness
Procedure for applying Aggregate
Awareness
1 Insert the Summary Table(s) in the universe structure;
set joins and cardinality
2 Set the contexts
3 Redefine objects using @AggregateAware
4 Define incompatible objects using Aggregate
Navigation
57

Designer

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Designer

Загружено:

Авторское право:

Доступные форматы

Cognizant Data Warehouse Solution Center

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Copyright 2002 Cognizant Technology Solutions

Creative MindsInnovative Approach

Data Warehouse & Business Intelligence Practice

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Extracting information from Database

The SQL Education

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

The Business Objects Solution

Database and Security

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Advantages of using Universe

Users can access data in an easy

Users can make queries without

The organization has a shared

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

The Universe Development Process

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

The Universe Development Process

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Define the Parameters

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Setting up Universe Parameters

Summary Tab: author and

Strategies Tab: internal or

Controls Tab: manages

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Setting up Universe Parameters

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Setting up Universe Parameters

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach

Setting up Universe Parameters

Copyright 2002 Cognizant Technology Solutions

Data Warehouse & Business Intelligence Practice

Creative MindsInnovative Approach