universe xi r3

8/2/2019 Universe XI R3

1/113


2/113

A universe is a semantic layer that maps the data

structure found in databases (tables, columns, etc) in

business terms.

A universe can represent any specific business area,

process, or department. For example, a universe can

relate to a department in a company such as

marketing or accounting.

What is a UniverseWhat is a Universe


3/113

Business Objects DesignerBusiness Objects Designer


4/113

A typical universe layout...A typical universe layout...

Classes

Objects

Universe Pane Structure Pane


5/113

ClassClass

A class is a logical grouping of objects within auniverse. In general, the name of a class reflects abusiness concept that conveys the category or typeof objects.

A class can be further divided into subclasses.

As a designer, you are free to define hierarchies ofclasses and subclasses into a model that bestreflects the business concepts of your company.


6/113

ObjectsObjects

An object is the most refined component in a

universe. It maps to data or a derivation of data in thedatabase.

Types of objects -

Dimension Objects -

Focus of analysis in a query.

Maps to one or more columns in a database that are key to a

query.

Measure Objects -

Aggregate functions that map to statistics in a database.

Map to fact attributes of a star schema.

Detail Objects

Descriptive data about the dimensions.

Always attached to a dimension.


7/113

Five stages in universe development processFive stages in universe development process

User RequirementsDetailed analysis of the information needs of the

users.

Data Analysis

Detailed data analysis of the database breaking itdown into functional areas that users can relate to.

Design

Information from first 2 phases must be

amalgamated to create the conceptual design of the

Universe, its objects and other components.


8/113

Development and distributionCreate using the Designer module.

Test using the User module.

Distribute to the users via the repository.

Maintenance

Designer is responsible for updating and maintaining

Universe and keeping it up to date with any changes

in the User Requirements.

Five stages in universe development processFive stages in universe development process


9/113

Define the Parameters

Insert Tables

Make the Joins

Resolve the Loops

Create Classes and Objects

Set up Hierarchies

Creation of the UniverseCreation of the Universe


10/113

Select File, Parameters

To begin creating a new universe:

Select File, New

To access the Universe Parameters dialog box for an

existing universe:

or

Click on

Creating a UniverseCreating a Universe


11/113

A universe is identified with a user name and a connectionto the database

A detailed description can also be added

Setting up Parameters : Definition TabSetting up Parameters : Definition Tab


12/113

What Is a Connection?What Is a Connection?

Definition:A connection is a link from the universe to the

target database.

The link is achieved using middleware (for example

ODBC).

An existing connection may be used or a new

connection created for a universe.

There are three different types of connections.


13/113

Different Types ofConnectionDifferent Types ofConnection

PersonalCan only be used on the client

Shared

Can be used by more than one user to send queries to the

target database from a shared server

Secured

This connection is used when you wish to distribute the

completed universe to the user population via the repository


14/113

3. Identify the driver to be

used to access the

target database

Creating a New ConnectionCreating a New Connection

2. Choose the middleware

1. Click on New.


15/113

Setting up Universe ParametersSetting up Universe ParametersDefinition 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 SQLparameters

Links Tab: enables dynamic

links with other universes


16/113

The Summary tab displays general information about theuniverse

Setting up Parameters : Summary TabSetting up Parameters : Summary Tab


17/113

Provides automatedstrategies for:

Setting up Parameters : Strategies TabSetting up Parameters : Strategies Tab

Creating objects

Setting joins

The Table browser

listing


18/113

A strategy is a script that reads structural informationfrom a database or a flat file.

DESIGNER uses strategies as an aid for creating thecomponents of the universe - objects, tables and

joins.

In DESIGNER, strategies are of 2 types Built-in Strategies

External Strategies

Universe StrategiesUniverse Strategies


19/113

BuiltBuilt--in Strategiesin Strategies

Built-in strategies are pre-decided strategies that areavailable with any installation of Business Objects.

DESIGNER uses the following built-in strategies forcreating the components of universes:

the Objects Creation strategy, which tells DESIGNER howto define classes and objects automatically from thedatabases tables and columns.

the Joins Creation strategy, which tells DESIGNER how todefine joins automatically from the databases tables andcolumns.

the Table Browser strategy, which tells DESIGNER how toread the table and column structures from the databasesdata dictionary.


20/113

BuiltBuilt--in Strategiesin Strategies

To enable automatic creation, the following must be checked


21/113

ExternalStrategiesExternalStrategies

External Strategies enable designers to specify theirown strategy for creating the universe components.

External strategy files are declared in the STG sectionof .PRM files and are specific to RDBMSes.

Use of external strategies

To insert Objects - Insert --> Candidate Objects

To insert Joins - Tools --> Detect Joins

To insert Tables - Insert --> Tables


22/113

These allow you to limit thesize of results and restrictthe time allowed forexecuting queries

Setting up Parameters : Controls TabSetting up Parameters : Controls Tab

The Supervisor can

change these

parameters for

specific groups orusers


23/113

SQL parameters areused to define the

limits of the SQL

that may be

generated by the

universe.

The Supervisor can

change these

parameters for

specific groups andusers.

Setting up Parameters : SQL TabSetting up Parameters : SQL Tab


24/113

Enables

dynamic links

with other

universes

Setting up Parameters : Links TabSetting up Parameters : Links Tab


25/113

Configures certain

SQL parameters

common to most

RDBMS to optimize

the SQL generated.

Setting up Parameters : parameter TabSetting up Parameters : parameter Tab


26/113

Choose File, Save or click

Saving a UniverseSaving a Universe

Save the universe using a maximum of eight characterswith up to three characters as an extension

This makes it possible to distribute the universe acrossdifferent kinds of computers

By default the universe is saved in the folder:

C:\Documents and Settings\\Application

Data\Business Objects\Business Objects 11.5\universes


27/113

Adding TablesAdding Tables

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

Use the Table browser:Double-click on the background of the

Structure


28/113

Customizing Table InsertionCustomizing Table Insertion

Select Tools, Options then click on the Database tab

From here you can select

and deselect options

related to table insertion

You can set internalstrategies

to:

automatically extract joins

detect cardinalities

create objects when

inserting tables


29/113

Creating classesCreating classes

Manual CreationUse Insert > class from the menu. An Edit Properties

box appears. Enter class description.

OR

Use to create a class


30/113

Automatic creation

Select a table in the structure pane.Drag it to the universe pane.

A class is created in the universe pane with the same name as the

table name.

Objects are also created automatically in the class corresponding

to the fields in the table.

Creating classesCreating classes


31/113

AliasesAliases

In SQL an alias is an

alternative name for a

table. The purpose of

aliases is to resolve

structural issues in a

database arising from

SQL limitations. In

DESIGNER, an alias is

just a pointer to anothertable

Aliases


32/113

Creating objectsCreating objects

Manual Creation

Select the class where object is to be created.

Use Insert--> Object from the menu. An Edit Properties

box appears. Enter object details.

Automatic creationSelect a column from a table in the structure pane.

Drag it to the universe pane.

An object is created under the nearest class to the point

where you drop the column.Default object name is column name with underscores

replaced with spaces.


33/113

Object Properties

Three property pagesDefinition

Name

Datatype

Description

SELECT

statement

WHERE clause

Object PropertiesObject Properties


34/113

Properties

Qualification

Associated List of

Values



35/113

Aggregate

projection

Applicable only

to measures.

Defines how the

measure will be

aggregated

when projected

from a micro-cube.



36/113

Advanced

Security

User rights on

Objects Date Formats



37/113

Joins


38/113

JoinsJoins

WHAT THEY ARE

Relationship between 2 or more tables that help

restrict the result set of a query run against those

tables.

WHY USE

They limit the occurrence of a Cartesian product, a

situation in which all possible combinations

between each row of each table are retrieved.


39/113

Types ofJoinsTypes ofJoins

Equi-JoinTable 1.Column A = Table 2.Column B

Resulting data set limited to values common in Column A& B.

Outer-Join

Table 1 OUTER JOIN Table 2 on Column A = Column B

Resulting data set limited to ALL the values in Table 1and ONLY matching values in Table 2 based on Column

A and Column B.

Theta-JoinTable 1.Column A BETWEEN .. AND

Links tables based on a relationship other than equalitybetween 2 columns.


40/113

A join can be entered manually using two methods:

Creating and Deleting JoinsCreating and Deleting Joins

With the menu option

Insert, Joins and the

Edit Join box

Graphically

To delete a join, click on the join line and press Delete

40 Copyright 1999 Business Objects SA - All Rights Reserved Issue 2, July 99


41/113

Integrity CheckIntegrity Check

Integrity check allows

the checking of

Universe structure,

Loops , Contexts ,

Cardinality and

Parsing Check on

Joins , Conditions and

Objects .


42/113

HANDSON WORKSHOP


43/113

Create a universe called VACATION

Create a new connection

Use ODBC Driver.

Connection Name Vacation-Connection

Use CLUB datasource

Connection type should be Personal

Remove the limits of 5000 rows and 10 minutes for

query time execution.

Exercise 1Exercise 1


44/113

Identify the windows in the interface...Identify the windows in the interface...

Class and the Object or

Universe Window

Structure Window

Table Window


45/113


The universe Vacation should have two Classes Customer

& Sales Details. Customer must have 2 objects Customer-Id & Customer-

Name (Full Name)

Sales Details must have two objects Invoice Date &

Invoice-Id. Customer (class) must have 2 detailed objects namely

Phone number & Address giving additional info. about

Customer Name.

Create an appropriate join between Customer and Salestables.

Save your work in the default location.


46/113

Observe the Properties for an ObjectObserve the Properties for an Object

Definition Tab

Properties Tab

Advanced Tab

For the object Customer Name -


47/113

Exercise 2AExercise 2A

Query 1 -Create a query which gives details about Customer

Names and their Invoice ID

Run the query

Query 2

Find Out the number of customers for which the

invoices have not been created from Vacation

Universe.


48/113

Exercise 2BExercise 2B

Customer class has 2 detail objects namely Phonenumber & Address giving additional info. about

Customer Name.

Add another detail object called Age Range which

specifies age range for the customer.

Hint :- Use Age Range table ;Use Theta join between

age ; max ; min


49/113

Exercise 2CExercise 2C

In the Vacation Universe create third class called

Sales Measures.

In this class create a measure object called revenue.

Save the universe and test in user module.

Notice the variation in Group By clause.

Hint :- Revenue = (days) x (nb of guest) x (price)

Use Service & Invoice line table


50/113

Exercise 2DExercise 2D

Create dimension objects City , Region & Country in Class

Customer

In the user module create a data provider using Customer

Name, Country & Sales Revenue.

Using Slice and Dice Panel remove Customer name from

the query. See the changes in Sales Revenue.

In Designer Module set Function = None

Repeat all the above steps


51/113

Restricting Data


52/113

Types ofRestrictionsTypes ofRestrictions

Hard Coded / Direct Restrictions

Indirect Restrictions

Flexible Conditioning of the Data

Multiple Prompt


53/113

HardHard--coded Restrictioncoded Restriction

Adding a WHERE condition to an object allows you to givea more precise definition:


54/113

How Data is RestrictedHow Data is Restricted

The Where clause in an SQL statement restricts thenumber of rows returned in the result set:

WHERE

... join definitions ...

WHERE

... join definitions ...

AND Country=United Kingdom


55/113

Indirect RestrictionIndirect Restriction

Achieved using conditional objects In the User Module , user has the option to apply the

restriction.

Obviously , more flexible than previous type of

restriction. Once a conditional objects are included, restriction

becomes hard-coded for the query.


56/113

Condition ObjectsCondition Objects

Select Condition Object View

Insert a Condition Object

Condition object name

Description

Where clause


57/113

Flexible / @Prompt type RestrictionFlexible / @Prompt type Restriction

Offers maximum flexibility

Limitation of Indirect type of restriction is overcome

by having flexibility in selecting the where clause.

Achieved using @Prompt Command.


58/113

@Prompt Command Syntax@Prompt Command Syntax

Message in the Prompt Any Message

Data Type A or N or D

List Of Values

Hard Coded List of Values {Japan, USA,France}

Values of existing Objects

Number of Choices Mono ; Multi

Type of Choice Free ; Constrained


59/113

Multiple Prompt ConditioningMultiple Prompt Conditioning

Extension of @Prompt Conditioning

More than one where clause can be prompted.

If the same Message text is used in the next prompt,the user is prompted only once and the same value issubstituted for the next prompt too.

For instance, consider the following where clause -

WHEREcolumn A = @prompt(Enter value,...)

AND column B = @prompt(Enter value,..)

This will result in the user being prompted only once andthe same value will be substituted for column B as well.


60/113

HANDSON WORKSHOP


61/113


Add a dimension object called CustomerName(French) to class Customer. The new object

should show only French Customers.

Save the Universe.

Test in User Module.


62/113


Add a condition object called French Only to classCustomer.

Set the conditions for the new object.

Save the Universe.

Check things in User Module.


63/113


Add another condition Object City-user-prompt toclass Customer.

Set the conditions for the new object using @Prompt

Command

Save the Universe

Check things in User Module


64/113

List of Values


65/113

What is a List ofValues?What is a List ofValues?

A LoV is used on the operand side of a condition in the

query panel of the User module

This is only available if set by the designer

A list of the distinct values from the column or columns to

which the object refers


66/113

Creating a List ofValuesCreating a List ofValues

A LoV is created within the Properties tab of an object

By default,

Associate a List and

Allow Users to edit

are checked:

It is important to

uncheck this box forobjects that dont

need a List


67/113

Controlling How Lists are RefreshedControlling How Lists are Refreshed

Normally, the first time a LoV is used in a User login

session, the system fires a query at the target database.

The results of this query are used to populate the list, and

are stored in the .lov file.

Thereafter, the .lov file from this query is used each time

the List is required.


68/113

Controlling How Lists are RefreshedControlling How Lists are Refreshed

Not normally used -uncheck this box

Check this box for

frequently changing lists

Check this box for lists that

never change


69/113

Modifying the Content ofa List ofValuesModifying the Content ofa List ofValues

You can limit the values returned by applying a condition

to the LoV

You can simplify the process of choosing a value for Users

by creating a hierarchy for the LoV

You can supply a personal data file containing the values

for the list, instead of using the results of the query


70/113

Applying a Condition to a List ofValuesApplying a Condition to a List ofValues

Click Edit in the Properties box:

Apply the condition in the Query

Panel:


71/113

Creating a Hierarchy for a List ofValues

Click Edit in the Properties box:

Place the hierarchy objects (which

must be sorted) to the right of the

LoV object in the Query Panel:


72/113

Creating a Hierarchy for a List ofValuesCreating a Hierarchy for a List ofValues

The resulting Hierarchical View of the LoV makes it easier

to select the required value:

Country:

Town:Showroom:


73/113

Basing a LoV on a PersonalFileBasing a LoV on a PersonalFile

Select Tools,

Lists of Val

ues from the Menu bar:

Select the object:

Select Personal Data:


74/113

Basing a LoV on a PersonalFileBasing a LoV on a PersonalFile

Click OK to acknowledge the message:

Specify the file that contains the values for the list and

click OK


75/113

HANDSON WORKSHOP


76/113


77/113

Hierarchies


78/113

HierarchiesHierarchies

An ordered set of related dimensions.

For example, A hierarchy called Geography may consistof Country, Region and City.

Necessary to drill up / down to see less or more

details.

Designer uses the class structure as the defaulthierarchy.

Custom Hierarchies can be built using Tools >

Hierarchies. A Hierarchy editor pops up. Use this to

create new hierarchies.Some classic examples for hierarchies -

Products - Category > Brand > Product

Time - Year > Quarter > Month > Week > Day


79/113

U.K.

North South

Liverpool ManchesterNewcastle London Southampton Bristol

Level in Hierarchy Data Returned

What is a Hierarchy?What is a Hierarchy?

An ordered set of related dimensions.

For example, A hierarchy called Geography may consist ofCountry, Region and City.


80/113

A Default Hierarchy is the hierarchy based on the order of

the Objects within the Class

Default Hierarchies are

represented in the Usermodule by the order in whichDimension Objects areorganized in the Classes andObjects box of the QueryPanel

What is a Default Hierarchy?What is a Default Hierarchy?


81/113

The key to creating Default HierarchiesThe key to creating Default Hierarchies

The designer must ensure, wherever possible, thatDimension Objects are organized from the most general to

the most specific within the Class


82/113

A Custom Hierarchy combines Objects from Default

Hierarchies to build a Custom Analysis Path

What is a CustomHierarchy?What is a CustomHierarchy?

Default Hierarchies

Custom Hierarchy

i i hii i hi


83/113

Creating CustomHierarchiesCreating CustomHierarchies

Add Objects from Default Hierarchies to build a new

Custom Hierarchy

(or Tools,

Hierarchies)

A i i i hA i i i h


84/113

Automatic Time HierarchyAutomatic Time Hierarchy

A time hierarchycan be built

automatically for

date objects.


85/113

HANDSON WORKSHOP

E i 7E i 7


86/113


Make a copy of the Island resorts marketing universe(Beach.unv) called TEST.unv

Create a custom hierarchy in this universe thatconsists of Customer, Service Line, Service.

Test this out in the User Module.

For the VACATION universe, create a Automatic TimeHierarchy on the object called Invoice Date in theclass Sales Details.

Save the Universe and test this out in the UserModule.


87/113

Loops

Wh t i l ?Wh t i l ?


88/113

What is a loop?What is a loop?

Multiple paths between the tables selected

in queries.

L b l d bL b l d b


89/113

Loops can be resolved by..Loops can be resolved by..

ALIASES

Alias - Same as the namesake in SQL.

Exact duplicate of the original table.

A different name tricks the SQL query to accept that you

are using 2 different tables.

CONTEXTS

Rule which helps BO decide which of the 2 paths to choose

in a loop.

BO prompts the user to indicate the correct perspective(relevant path) for the query.

Wh t AliWh t Ali


90/113

When toAliasWhen toAlias

A loop with a singlelookup table should beresolved by an alias

A lookup table can beidentified by its

cardinality

N N

N

N

N

1 1

1

1

1

A lookup table only hasthe one end of joins

attached to itAlias needed here

H t AliH t Ali


91/113

How toAliasHow toAlias

Designer routinesdetect loops and

candidates for aliases

Break the loop by

creating an alias of the

lookup table for each

side of the loop

Do not remove the

original table

R l i L i C t tR l i L i C t t


92/113

Resolving Loops using ContextsResolving Loops using Contexts

Customers

Sales SalLines

Loans LoansLines

Country

There are two possible routes to

link Clients with Models:

Working with sales

Working with rentals

D t ti d C ti C t tD t ti d C ti C t t


93/113

Detecting and Creating ContextsDetecting and Creating Contexts

Detect Contexts detects and proposesa list of contexts to create

Loop Detection routine: suggests candidates

for both aliases and contexts

Insert Contexts inserts a contextmanually


94/113

HANDSON WORKS

HOP



95/113

Add following table to the Vacation Universe

Service_line

Resort

Use Alias to Solve the loop Complete the universe Designing

Save the universe as Vct-Als

Test the new universe in the User Module




96/113

Add following table to the Vacation Universe

Service_line

Reservation

Reservation_Lines

Resort

Solve the loop

Complete the universe Designing

Save the universe as Vct-Con

Test the new universe in the User Module



97/113

OLAP Universes

OLAP UniversesOLAP Universes


98/113


OLAP universes are generated from OLAP cube orQuery.

OLAP data sources supported are:

BW SAP

Microsoft Analysis Services

Essbase

OLAP universes are created by selecting a OLAP

connection to a QueryCube or InfoCube. The

universe creation process is automatic once the

connection is selected.



99/113


Creating a OLAP connection.

Select Tools > Connections.

Select Add.

Expand the node for your target OLAP datasource.

Expand the middleware node.

Select the data access driver.Select logon options and click Next.

Expand cube nodes to display the cubes and query cubes

available.

Select Advanced options and click Next.

Click Next.Click Finish to complete the connection creation.



100/113


Generating a OLAP universe

Click the New Universe icon.

Select a connection from the Connections drop down

list box.(It should be an OLAP connection.

Click OK.

Note: Since it is a OLAP connection, the

universe is automatically generated.


101/113

Universe Maintenance

Reasons for Universe MaintenanceReasons for Universe Maintenance


102/113

Reasons for Universe MaintenanceReasons 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

Changes to the Target DatabaseChanges to the Target Database


103/113

No Impact:

Adding new columns Adding new tables

Severe Impact:

Renaming/moving database Changing existing column

and table names Deleting tables and columns

Changes to the Target DatabaseChanges to the Target Database

The implications of modifying the underlying database forBusinessObjects universes varies in severity:

Detecting Changes to the UniverseDetecting Changes to the Universe


104/113

Detecting Changes to the UniverseDetecting Changes to the Universe

Choose View, Refresh Structure

Changed tables are highlighted inthe Structure

A message on the screenindicates that tables have been

deleted

The Effect of Changing ObjectsThe Effect of Changing Objects


105/113

No Impact:

Redefining Object SQL Renaming an Object Copying to different Class Moving in same Class or to

a different Class Adding new Objects

Impact:

Deleting an existingObject

Deleting and thenrecreating an object withexactly the samedefinition

The Effect ofChanging ObjectsThe Effect ofChanging Objects

Changes to existing Objects in a Universe can have animpact on existing Documents created from the Universe:

Linking UniversesLinking Universes


106/113

Linking UniversesLinking Universes

Linking can mean reduced maintenance.

UniverseA

UniverseA

Universe B

Two Approaches to LinkingTwo Approaches to Linking


107/113

TwoApproaches toLinkingTwoApproaches toLinking

Kernel approach

Master approach

Kernel ApproachKernel Approach


108/113

KernelApproachKernelApproach

Human Resources

+

Motors2000

+

KernelKernel

KernelKernel

KernelKernel

Staff

Master ApproachMaster Approach


109/113

MasterApproachMasterApproach

MasterMasterHuman Resources

Motors2000

HR

andMotors2000

-

-MasterMaster

MasterMaster

Making a LinkMaking a Link


110/113

Click and click on the Links tab

Making a LinkMaking a Link

Click Add Link...

Choose universe to

link and click Open

The Derived UniverseThe Derived Universe


111/113

The Derived UniverseThe 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

Including UniversesIncluding Universes


112/113

Including UniversesIncluding Universes

UniverseA

Universe B

Everything

from

Universe A

Universe B

Universe A

Including a Universe COPIES structure and objects to thederived universe:

Included UniversesIncluded Universes


113/113

Included UniversesIncluded Universes

Included universes become part of the new universe