BO Designer _Intelligroup

8/6/2019 BO Designer _Intelligroup

1/168

Business Objects

Designer


2/168


3/168

3 2005 Intelligroup, Inc. Confidential & proprietary3

Universe ?

Universes are nothing but a business intelligent semantic layer between the

end user and the database, that isolates the end user from technical issuesof the database.

Universe maps to data in the database in everyday terms that describe

business situations.

Universes are made of Classes and Objects.

Objects

- Maps to column of a table in the database.

Classes

- Logical Grouping / collection of objects.


4/168

4 2005 Intelligroup, Inc. Confidential & proprietary

Business Objects Designer


5/168


The semantic layer may consist of one or more separate universes

Each universe is a partial representation of a database, in the

form of business vocabulary

Sales/MarketingSales/Marketing

HumanHuman

ResourcesResourcesEmployee

Salary

Benefits...

Sales Revenue

Sales ExecutiveCustomer

Product

Price

Order Date ...

The Semantic Layer


6/168


Class & Object

A class is a logical grouping of objects within a universe. In general, the

name of a class reflects a business concept that conveys the category ortype of objects.

A class can be further divided into subclasses.

As a designer, you are free to define hierarchies of classes and

subclasses into a model that best reflects the business concepts of your

company.

An object is the most refined component in a universe. It maps to data or a

derivation of data in the database.

Object Categories Dimension

Detail

Measure


7/168


A typical universe layout

Universe Pane

Classes

Objects

Structure Pane


8/168


Creating aUniverse

Define the Parameters

Insert Tables

Make the Joins

Resolve the Loops

Create Classes and Objects

Set up Hierarchies


9/168


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

Setting Parameters


10/168


Definition Tab

A universe is identified with a universe name and a connection to the

database A detailed description can also be added


11/168


What Is a Connection?

Definition:

A connection is a link from the universe to thetarget database

The link is achieved using middleware (for example ODBC)

An existing connection may be used or a new connection createdfor a universe

There are three different types of Business Objects connection


12/168


Different Types of Connection

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

PersonalCan only be used on the client


13/168


Creating a New Connection

2. Identify the driver to be

used to access the

target database

1. Click on New


14/168


Choose File, Save or click

Saving aUniverse

Save the universe using a maximum of 100 characters

This makes it possible to distribute the universe across different

kinds of computers

By default the universe is saved in the folder:

C:\Documents and Settings\user\Application Data\Business Objects\

Business Objects 11.5\Universes

When you save a universe, you save the version of the universe on the file system.

This is not the same as exporting the universe to the repository. When you export a

universe, the version in the Central Management System (CMS) is updated. This is

the version that replaces the file system version when you import the universe.


15/168


Universe Default Save Settings

You can change the default folder where universes are saved

You can also set up Designer to automatically save at specified intervals

Choose Tools, Options:


16/168


Access the Connections dialog box by selecting Tools,Connections

Displaying Existing Connections

All the available

connections can be

displayed, modified or

removed with the

Connections dialog box


17/168


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

ParameterTab: For defining SQL

parameter


18/168


The Summary tab displays general information about the universe

Setting up Parameters : Summary Tab


19/168


Provides automated strategies for:

Setting up Parameters : Strategies Tab

Creating objects Setting joins

The Table browser listing


20/168


These allow you to limit the size of results and restrict the time allowed for

executing queries The Administrator can change these parameters for specific groups or

users

Setting up Parameters : Controls Tab


21/168


SQL parameters are used to define the limits of the SQL that may be

generated by the universe

The Administrator can change these parameters for specific groups and

users

Setting up Parameters : SQL Tab


22/168


Enables dynamic links with other universes

Setting up Parameters : Links Tab


23/168


In Parameter tab, SQL generation parameters that you can set for the

universe.

Setting up Parameters : Parameter Tab


24/168


Using Find and Replace

You can use Find to locate characters or a text string in both the universe

and structure panes. You can use Find and Replace to locate and replacecharacters or text in the names and descriptions for any structure in the

universe.

To search in a universe:

1. Click in the UniverseorStructure pane.

You want to find a string

in this pane.

2. Select Edit > Find.


25/168


The box for an active Structure pane appears below.

Using Find and Replace

The box for an active Universe pane is below.


26/168


What YouWillBe Able To Do

Add tables to the Structure

Move tables

Know about different ways of viewing tables

Using Derived Tables


27/168


Adding 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 keyor Ctrl key

3 ways to use the Table browser: Double-click on the background of the Structure


28/168


Click on and to zoom in and out

Click on to arrange the tables to fit in the window

Use the View, Change Table Display option

Use the Speed menu on a table or row

Organizing Your Tables

A lot of options allow a better view of the tables:

Use drag and drop to move the tables around the Structure


29/168


Customizing 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 internal strategies

to:

automatically extract joins

detect cardinalities

create objects when

inserting tables


30/168



Set equi-joins manually

Delete and modify joins

View joins in List Mode

Set cardinalities

Be able to set outer, theta and self-restricting joins

Full Outer Join


31/168


Joins

A join is a condition that restricts the result set of a multi-relational query

Equi-join (otherwise known as a standard or inner join)

There are several different kinds of join:

Theta join

Self restricting join

Outer join

Full Outer Join

Short Cut Join


32/168


Equi-Joins


33/168


Ajoin can be entered manually using two methods:

Creating and Deleting Inner Joins Manually

With the menu option

Insert, Joins and the Edit

Join box

Graphically

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


34/168


Outer Joins


35/168


Creating Outer Joins

An outer join is created by converting an existing equi-join

By default you can create either a left outer, or a right outer join dependingon which side of the join the outer table is designated.

You can also create a full outer join by activating ANSI 92 support for joinsin the universe. This is achieved by setting a universe SQL parameterANSI92 to YES (File >Parameters > Parameter).

Outer Join


36/168


Example: Outer join

The tables Resort_Country and Resort below are linked by an equi-join.

Each resort belongs to a country, but each country may not have a resort.

If you use an equi-join, the result set of a query would only show

information on the countries that have a resort;Australia, France, and the

US.


37/168


However, you may wish to show all countries irrespective of an equivalent

value in the foreign key of the Resort table. To achieve this you define anouter join so that all counties are returned, despite having no match in the

Resort column, as shown below:


38/168


You can define an outer join using the ANSI 92 standard for defining outer

joins.T

his allows you to specify a full outer join.To use the

AN

SI 9

2standard for outer joins, you must set the ANSI 92 parameter to YES. This

parameter is available on the Parameter page

(File > Parameters > Parameter).


39/168

397/1/2011 2005 Intelligroup, Inc. Confidential & proprietary

ThetaJoin

A theta join contains an expression that is based on something other

than equality:

ThetaJoin Result Set:

ThetaJoin


40/168


Creating ThetaJoins

A theta join is created by converting an existing equi-join

CTRL-CLICK


41/168


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.


42/168


Creating Self Restricting Join


43/168


Shows the relationship between tables on the basis of the join

Join Cardinalities

Cardinality:

Should only be one to many or one to one. It should never be many to

many

Is not needed to infer SQL in Business Objects

Is only required to resolve loops and alternative routes in the Structure


44/168


Adding Cardinalities

Manually using the Edit Join dialog box

Automatically using (but can take a long time)


45/168


List Mode displays tables, joins and contexts

Using List Mode

It is possible to identify joins related to a specific table


46/168


Always check integrity after defining joins

Checking Integrity


47/168


Testing

REMEMBER: Once you have created the objects for your universe

you must make extensive multi-relational queries to check that the

joins are producing the SQL output intended


48/168



Organize the universe into classes and sub-classes

Create dimension and detail objects

Understand and edit object properties

Test objects


49/168


Objects

DimensionsProjects columns from the database which are key

to a query

DetailsProjects columns from the database that provide

detailed information related to a dimension

Measures

Contains aggregates to project statistics


50/168


Classes

Used to group related objects

Used to provide subsets of

related objects


51/168


The Classes and ObjectsWindow

Order of dimensions in a

class hierarchically

Details are attached to

dimensions


52/168


The Classes and ObjectsWindow

Measures are grouped in aseparate class

Except where they can only be used withobjects from a given class


53/168


Use to create a

class

Use the Description field

to provide information for

users

Creating and Editing Classes


54/168


Sub-classes allow a better

organization of objects

Avoid too many levels of sub-

classes Use the Speed menu on a class to

create a sub-class

Creating aSub-Class


55/168


Creating a Class from a Table

Use Drag and Drop

This wizard will create one object for each field


56/168


Different Ways:

Manually with

Drag and drop from a database column into a class

Insert objects from another universe (copy and paste)

Creating an Object


57/168


Object Properties : The Definitions Tab

By default the type is

the same type as used

by the database

Add a description to the

object

Inferred SQL for Select

statement


58/168


The Select andWhere EditWindows

Inferred SQL

Pick Lists


59/168


Object Properties : The Properties Tab

Define the type of object

Associate a List of Values

for end users conditions if

appropriate


60/168


Object Properties : The Advanced Tab

Uncheck the Sort option


61/168


Remember to check integrity after creating objects

Checking Integrity

Wh t i M Obj t?


62/168


What is a Measure Object?

A measure object returns numeric information

A measure object is created by using aggregate functions

The five basic aggregate functions are:

Sum

Count

Maximum

Average

Minimum

AM i D i


63/168


AMeasure is Dynamic

Measure objects are semantically dynamic

H M W k t S l t L l (1)


64/168


How a MeasureWorks at Select Level (1)

H M W k t S l t L l (2)


65/168


How a MeasureWorks at Select Level (2)

Levels ofAggregation in Business Objects


66/168


Levels ofAggregation in Business Objects

Select

database

Project

Query Results

Aggregation

Aggregation

Aggregation at Projection Level


67/168


Aggregation at Projection Level

When projecting all variables in the micro cube no aggregation takes

place

When projecting only some variables from the micro cube aggregation

occurs

Setting Select / Projection Aggregates


68/168


Setting Select / Projection Aggregates

Statistically, only certain select / project aggregates are compatible.

Select Aggregate Recommended ProjectAggregate

Sum Sum

Count Sum

Average None or Average (not recommended)

Maximum Maximum

Minimum Minimum

Measure Object Properties : Definitions


69/168


Measure Object Properties : Definitions

Data Type must be a number

Select must be an aggregate

Measure Object Properties : Properties


70/168


Measure Object Properties : Properties

Object Type must be a

measure

Aggregate Function must

be appropriate for the

Select aggregate

Measures should not have

an Associated List ofValues

Viewing Object Parent Table(s)


71/168


Viewing Object Parent Table(s)

You can view the parent tables of an object by right-clicking on anobject and selecting the View Associated Table option

Testing Measure Objects


72/168


There are three elements to testing a dimension or detail object :

Testing Measure Objects

Measure objects need more thorough testing :

1 Check objects exist.

2 Check inferred SQL.

3 Check query results.

1 Check objects exist. 2 Check inferred SQL.

3. Check query results.

4. Repeat with otherdimensions.

5 Make a query with aminimum of twodimensions and ameasure.

6. Check projection with

Slice & Dice.

Testing Measure Objects at Select Level


73/168


GROUPBYCountry.country

GROUPBYCountry.country,Region.Region_Name

Testing Measure Objects at Select Level

Testing Measure Objects at Project Level


74/168


Testing Measure Objects at Project Level

An Aggregation Problem


75/168


An Aggregation Problem

The Group By clause groups each distinct dimension attribute and produces asingle measure value for that group. If you are not careful when creating a

query with dimensions and measures, this can result in misleading

information.

What is a loop?


76/168


What is aloop?

A loop exists when the joins between tables form a continuous path

How to deal with loops


77/168


How to deal with loops

One of two routines can be used to resolve most loop situations in theuniverse structure window.

Alias DetectionRoutine

Context DetectionRoutine

...and...

Must be done prior to usingdetection routines and done

correctly. Otherwise,routines may recommendincorrect solution.

Set Cardinality ManuallyforAll Joins

Cardinality Detection


78/168


Cardinality Detection

Cardinality not set: Set Cardinalities:

Do this manually:

What is an Alias ?


79/168


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

When to Alias


80/168


When to Alias

A loop with a single lookuptable should be resolved by

an alias

A lookup table can beidentified by its cardinality

N N

N

N

N

1 1

1

1

1

Alookup table only has theone end of joins attached to it

Alias needed here

How to Alias


81/168


Designer routines detectloops and candidates for

aliases

Break the loop by creating an

alias of the lookup table foreach side of the loop

Some designers like to

create an alias for both

sides of the loop.Do not remove the

original table

Detecting and Creating Aliases


82/168


g g

Use the Alias Detection routine

Manually insert an alias

Use the Loop Detection routine

To create an alias table to break a loop, you can:

Using automatic loop detection


83/168


g p

Click the Detect Loops button

The routine checks the structure for loops

The Loop Detection window identifies each loop

The window suggests candidate contexts or aliases

Using Detect Aliases Routine


84/168


g

Click the Detect Aliases button

The routine lists candidate

Alias tables

You can rename the Alias

tables if required

Inserting an Alias Manually


85/168


g y

Select the table and click the Insert Alias button

Name the Alias table and click OK

Then reset the joins manually

Choosing which Alias Method to Use


86/168


g

Met A t es Disadvantages

Detect s Canview l s ef reappl ing t em

Mayshowother loops tobe resolvedbycontexts

Detect Aliases Findsall candidatealiasesexcl sively

Novisual checkprior toacceptance

Insert Alias Choose table toalias -minimizingobjectredefinition

Must understandhow toidentify theneed foracandidateanalysis

Whichever method you choose, you must always redefine objects that

now use the Alias table

Listing & Renaming Aliases


87/168


g g

You can list all aliases in a universe via the Tools > List ofAliases.

Drop down menu option.

You can also rename an alias via this panel.

Resolving Loops using Contexts


88/168


Customers

Sales SalLines

Loans LoansLines

Country

There are two possible routes through

the structure:

Sale_Model context

Rental_Model context

A context is merely a collection ofALL the joins on a single route.

Context name = table name on a route with only many cardinality.

Resolving Loops using Contexts


89/168


Rental_Model context

Sale_Model context

Each context represents

what may be inferred in a

single SELECTstatement.

Any query which infers

some SQL code

exclusive to one context

and some exclusive tothe other will infer two

separate SELECT

statements

A context is detected for

each route on which

there is a table with just

many cardinality.

Detecting and Creating Contexts


90/168


Detect Contexts detects and proposes a list

of contexts to create

Loop Detection routine: suggests candidates for both

aliases and contexts

Insert Contexts inserts a context manually

Display the contexts : View List Mode


91/168


Editing Contexts


92/168


Double click the context in the List Mode window

The context name

The highlighted joins are

included in the context

The description appears in theUser module Help panel

Loop Detection routine - the drawback


93/168


When you use Loop Detection and detect a number of loops:

The routine does not offer the Alias candidates first, so you may have to

update the Contexts after you have added the Alias tables

Loop 1 of 10


94/168

Shortcut Joins


95/168


If a query includes Client andCountry but NOT Region, the

Region joins are still needed in

the SQL.

But joining Country to Client

directly creates a loop

Inefficient!

Shortcut Joins - the solution


96/168


Edit the join to create a Shortcut join:

This is not a Loop!

Be aware of existing Contexts when you add the join: Shortcut joins are

not automatically added

Recursive table structures


97/168


These occur when a table acts as a lookup for itself

Each Employee has a Manager, who is also an Employee

But adding a Self Join creates

a single table loop where the

cardinality is unknown

These loops must be resolved

manually

Recursive table structures - the solution


98/168


Create an Alias of the lookup table

Manually set the cardinality

Test the results in the user module

Test the structure ofa universe


99/168


Check the syntax

Test in the User Module

What are Contexts


100/168


A context is simply a list of joins denoting a path between tables.

Contexts are set to identify alternative routes in the universe structure.

BusinessObjects detects a context for each alternative route on which

there is a table with just the many end of joins attached to it.

Contexts identify joins (and therefore tables) which are compatible withinthe same SELECT statement

Alternative Routes


101/168


Alternative routes do NOT only exist in loop scenarios.

Loop

2 Routes = 2 Contexts

Context 1

Context 2

Fork

Context 1

Context 2

2 Routes = 2 Contexts

How Contexts are Detected


102/168


A separate context is identified for each table with only the many end of

joins attached:

The joins in a context are identified by working back from the table with

only the many end of joins attached - many-one, many-one.

Identifying how many Contexts are required


103/168


You can arrange your universe structure so that all joins are flowing from the many ends at

the left to the one ends at the right.

Number ofcontexts

required = 2

Identifying the joins that make up a Context


104/168


The forward flowing joins form the Sale context No joins flowing back from

one to many are included

Why Apply Contexts


105/168


To resolve Fan Traps

To avoid Chasm Traps

You can also use contexts as part of the means to resolve fan traps.

However, unlike chasm traps, you must identify them first before theycan be resolved.

By detecting and setting contexts you will avoid the possibility of

experiencing a chasm trap. This assumes that you have engineered

cardinality correctly before detecting contexts.

The Chasm Trap


106/168


For a Chasm Trap to occur, there must be:

A

B C

X

Y Z

When a query is run which

uses objects Y and Z the

inferred SQL includes tables B,

C and A which have a many-

one-many relationship

respectively. This results in thevalues for each object to be

multiplied by the other. The

effect is similar to a cartesian

productbut is known as a

chasm trap.

The chasm trap is resolved by executing a separate SELECT statement for object Y and

object Z.

Chasm Trap : Universe Solutions


107/168


How can we avoid the chasm trap?

By inferring two separate SELECT statements and only then combining

the results of each one into microcube(s) for projection into block(s).

To infer two separate SELECT statements from a single BusinessObjects

query you can either:-

1A

lter theSQ

L parameters for theU

niverse

2 Use Contexts

The first method is NOT recommended as it only works with measures

and will result in certain inefficiencies in processing. The second method

works every time and will not result in inefficiencies.

The Classic Fan Trap


108/168


For a Fan Trap to occur, there must be:

X

Y

Z

When a query is run which uses objects Y and Z

the inferred SQL includes tables B and C which

have a one-many relationship. This results in a

value for the Y object being multiplied by the

number of values of the Z object related to that Y

object value. Like the chasm trap, the effect issimilar to a cartesian product.

Like the chasm trap, the fan trap can be resolved by executing a separate SELECT

statement for object Y and object Z. The alternative solution is to avoid it in the first place!

A

B

C

This is a common structure and will not normally

result ina fan trap. The trap only occurs where

(due to DB design) a column in table B holds data

values which are already a sum of those values

held at table C.

Classic Fan Trap : Solution


109/168


How can we avoid the fan trap?

By inferring two separate SELECT statements and only then combiningthe results of each one into microcube(s) for projection into block(s).

By avoiding the fan trap scenario in the first place!

Classic Fan Trap : Universe Solutions


110/168


1 Alter the SQL parameters for the Universe

2 Use a combination ofAliases and Contexts

NOTE: The first method is NOT recommended as it only works with measures and will

result in certain inefficiencies in processing. The second method works every time and

will not result in inefficiencies.

To infer two separate SELECT statements from a single BusinessObjects

query you can either:-

To avoid placing a measure on anything other than the last table in a

table path (i.e. the table with only many cardinality attached to it).

How Data is Restricted


111/168


The Where clause in an SQL statement restricts the number of rows

returned in the result set:

WHERE... join definitions ...

WHERE... join definitions ...

AN

D Country=United Kingdom

Methods of Restricting Data in BusinessObjects


112/168


Designers and Users are able to influence the SQL Where clause in

different ways:

Designers: Users:

Where clause in objects:Creating acondition object:

Using a conditionobject:

Self-Restricting Joins:

Additional Join

Information:

Defining a condition:

Filtering a report:

Restricting Objects


113/168


Adding a restriction to an object allows you to give a more precisedefinition:

Restricting Objects: the Drawbacks


114/168


Multiple objects prevent you from building logical default hierarchies.

You have to add a new object for each separate restriction.

The restrictions are not obvious to the end user.

If a combination of similarly restricted objects is included in a query, noresults are produced because the conditions conflict:

The User expects data for both French and Germanclients, but gets no results, because no client is bothFrench and German

For example:

Restricting Objects:Advantages


115/168


The one advantage of applying restrictions to objects is that the User isautomatically forced to apply the restriction - no choice.

On balance, it is better to avoid applying restrictions to an object unless

this is absolutely necessary.

This assists with ease of use.

Restricting Objects - aWorkaround


116/168


If you apply restrictions to objects forSales Revenue 1998 and

1999:

These drawbacks apply: multiple objects, conflicting restrictions.

Restricting Objects - aWorkaround


117/168


Use conditional Select clauses rather than restrictions on objects:

Multiple objects, but no conflicting restrictions

Condition Objects


118/168


Useful for complex conditions and for frequently used conditions

Better than applying restrictions to Objects because the User can choose

to add the condition

No multiple objects

Condition objects do not change the User view of the Dimension objects in

the Classes and Objects window

Condition Objects


119/168


Select Condition Object View

Insert a Condition Object

Condition object name

Description

Where clause

Applying Restrictions to Tables


120/168


If a table in your database has a flag which it uses to switch between 2 or

more domains, you can apply a restriction to the table using a SelfRestricting Join

The Advantage of using Table Restrictions


121/168


The restriction is applied whenever the table is inferred in the SQL,

irrespective of where in the SQL statement the table is inferred.

For example, if the table only appears in the FROM clause, the restrictionstill applies in the WHERE clause.

Multi Purpose Lookup Tables


122/168


Aquery Which countries do our clients come from? may also includecountries that are Showroom countries or Car Maker countries.

AdditionalJoins


123/168


You can restrict the data that is returned for an object by specifying

additional tables in the object properties.

You do this in the Tables

box

The restriction is created from thejoins between the tables

Select the relevant table:

When to Use each Restriction Method


124/168


Apply Restrictions to Objects when you need to force a restriction which is

not automatically inferred whenever the table is included in the SQL.

Use Condition Objects when you want to assist the end users by

predefining optional conditions.

Use Table Restrictions (Self-Restricting Joins) when you want the

restriction to be applied whenever the table is inferred in the SQL.

Use Additional Joins when a lookup table serves more than one purposein the universe.

The @ Functions


125/168


The @ Functions available are:

These Functions are applied in the Select

and Where boxes of objects

They are used to provide flexible

methods of specifying SQL

@Prompt


126/168


@Prompt is placed in an object as part of the Select or Where properties

When a query is run that includes the object, the @prompt of the object

forces a prompt box to appear

@Prompt Syntax


127/168


SHOWROOM.SHOWROOM_NAME = @PROMPT

Free or constrained (to value in LoV).. Constrained

Enter Showroom Name,The prompt.

A,Data Type (A, N or D)...

Showroom\Showroom,LoV Pointer....

Or hardcoded list : {A,B,C}

Mono,Mono or multi (LoV selection)..

(

)

Operator dependent on operand

@Select


128/168


@Select function acts as a pointer to the Select box of another object:

@Select (Class_Name\Object_Name)

Creates a dynamic link between objects, so that update of the original

object Select statement automatically updates the other objects

@Where


129/168


The @Where function acts as a pointer to the Where box of another object

Creates a dynamic link between objects, so that update of the original

object Where clause automatically updates the other objects or condition

objects

@Where - Designer Strategy


130/168


You can create a Class containing only Where clause objects, and hide the

Class from end Users - other objects use the Where clauses, but the Users

dont see the base objects.

How do Lists ofValues work?


131/168


A designer can create a LoV which is based on:

A query of the target database

A constant set of values held in a file

In both cases, the result is stored locally in a file on the User s PC.

Creating a List ofValues


132/168


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 for objects that

dont need a List

Controlling How Lists are Refreshed


133/168


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.

Controlling How Lists are Refreshed


134/168


Not normally used - uncheck

this box

Check this box for frequently

changing lists

Check this box for edited lists

Modifying the Content ofa List ofValues


135/168


You can limit the values returned by applying a condition to the LoV

You can simplify the process of choosing a value forUsers 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

Applying a Condition to a List ofValues


136/168

136

2005 Intelligroup, Inc. Confidential & proprietary

Click Edit in the Properties box:

Apply the condition in the Query Panel:

Creating a Hierarchy for a List ofValues


137/168

137


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:

Creating a Hierarchy for a List ofValues


138/168

138


The resulting Hierarchical View of the LoV makes it easier to select the

required value:

Country:

Town:

Showroom:

What Is a Hierarchy?


139/168


U.K.

North South

Liverpool Manchester Newcastle London Southampton Bristol

Level in Hierarchy Data Returned

What Is a Default Hierarchy?


140/168


A Default Hierarchy is the hierarchy based on the order of the

Objects within the Class

Default Hierarchies arerepresented in the Usermodule by the order in whichDimension Objects areorganized in the Classes andObjects box of the QueryPanel

The Key to Creating Default Hierarchies


141/168

141


The designer must ensure, wherever possible, that Dimension Objectsare organized from the most general to the most specific within the

Class

How are Hierarchies used in Analysis?


142/168

14


Dimension Objects represent the levels in a hierarchy:

Top Level

Level 1

Level 2

Level 3

A Measure can be analyzed at each level

What IsA Custom Hierarchy?


143/168

143


A Custom Hierarchy combines Objects from Default Hierarchies

to build a CustomA

nalysis Path

Default Hierarchies

Custom Hierarchy

Creating Custom Hierarchies


144/168

144


Add Objects from Default Hierarchies to build a new Custom Hierarchy

(orTools,

Hierarchies)

The Effect of Custom on Default Hierarchies


145/168

14


User module Scope ofAnalysis after a Custom Hierarchy has been

created:

No Default Hierarchies are shown

The Effect of Custom on Default Hierarchies


146/168

146


Selected Default Hierarchies can be added to the Custom Hierarchies in

Designer module

Why Is Time ASpecial Case?


147/168


Sale Date25/11/99

Month Year

Quarter

Day

Creating Time Hierarchies


148/168


Automatic Time Hierarchies

Using Database Functions

Table Based Time Hierarchies

What is Aggregate Awareness


149/168

149


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.

Summary Tables


150/168

150 2005 Intelligroup, Inc.

Confidential & proprietary

Check the columns in the Summary Table:

The other columns relate to objects

that require @AggregateAware

definitions

Foreign Key columns are used for

the joins

Note that Summary Tables without Foreign Keys do not need joins - they

can be free floating tables.

How Summary Tables are used in SQL


151/168



Aggregates of a normalized database are based on event / fact level data.

Sale

226 rows

Sale_Model

233 rows

Model

33 rows

Sales Revenue = sum(SALE_MODEL.SALE_QTY * MODEL.MODEL_PRICE *((100 - SALE.SALE_SALE_DISCOUNT) / 100))

Summary tables may be added to a database which hold data at a higher

level of aggregate.Annual_Figures

26 rows

Sales Revenue = sum(ANNUAL_FIGURES.ANNUAL_SALE_VALUE)

Making use of summary table data speeds up response times.

Procedure forApplying Aggregate Awareness


152/168



1 Insert the Summary Table(s) in the universe structure; set joinsand cardinality

2 Set the contexts

3 Redefine objects using @AggregateAware

4 Define incompatible objects using Aggregate Navigation

Step 1: Inserting a Summary Table & Setting Joins


153/168



Add the Summary Table to the structure

Set the joins and the cardinality

Step 2: Detecting Contexts


154/168



Set the contexts The Annual_Figures context

Step 3: Redefining Objects


155/168


Edit the objects affected by the Summary Table.

@AggregateAware Syntax:

@AggregateAware(Definition1,Definition2,,DefinitionN)

From the most to the least Aggregated

The last definition must be valid for all the queries

Step 4: Incompatible Objects

Aggregate aware objects can only be compatible with objects derived


156/168


Aggregate aware objects can only be compatible with objects derived

from tables in the same context as the summary table

Incompatible objects are specified using Aggregate Navigation

Step 4: Aggregate Navigation


157/168


Select the Summary Table: Check each object for compatibility

against the context and the select

of the object .

Individual objects are checked to

define them as incompatible

The Aggregate Navigation box is opened from the Tools menu

Testing Aggregate Awareness


158/168


As with any universe element, you must always test the results in the

User module.

Run queries using the aggregated measures from the Summary Table.

Use both compatible objects and incompatible objects in different

queries to make sure all levels ofAggregate Awareness are operating

correctly.

Aggregate Awareness as Preferential Coding


159/168


The aggregate awareness functionality in BusinessObjects can be

viewed simply as a method of specifying preferential or conditionalcoding.

When viewed from this perspective you can begin to see the true

potential of aggregate awareness functionality within the Designer

module.

Aggregate awareness functionality can be used for purposes other than

taking into account summary tables to improve the efficiency of a

universe.

Select the Tools, Options menu then click on the Print tab to select what toi t

Documenting a Universe


160/168


print

Select the File, Print menu to print

Linking Universes


161/168


Within a universe (B) it is possible to dynamically link to another universe

(A).

UniverseA

UniverseB

Universe

A

This has the effect of making it appear as though the classes, objects and

structure of universe A are part of universe B. However, they are just a lookup

(signified by the fact they are greyed out) to universe A and can not be edited in

universe B.

Why Link Universes : The Kernel Approach


162/168


One possible reason for linking universes is where you have a number of

universes, each of which contains the same core set of objects. By

creating each universe as a separate entity you are effectively coding thesame objects several times over. By linking you could avoid this.

KernelA

DerivedB Derived C

Universe

A

Universe

A

Holds core objects

Edit objects/structure inKernel universe and changesare automatically reflected

in the Derived universes Band C.

Linking Universes : Things to Watch Out For

You can only link to a universe if that universe has been exported to the


163/168


Linking only links in classes, objects and structure from one universe to

another. It does not link contexts. The contexts of the derived universe

will have to be altered to accommodate the linked tables joins.

The linked structure will have to be joined to the native structure of the

derived universe to avoid Cartesian products.

y p

repository first.

Only ever contemplate linking universes which are part of the same

universe domain in the BusinessObjects repository and will remain so.

You can only use one level of linking.

Making a Link


164/168


Click and click on the Links tab

Click Add Link...

Choose universe tolink and click Open

The Derived Universe


165/168


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

(i.e.insert new joins and edit contexts).

Why Link Universes : Include (Copy)

Another possible reason for linking universes is that you wish to copy

ll th l bj t d t t f i t th Y


166/168


all the classes, objects and structure from one universe to another. You

could do this by first linking from universe B to A and then use the

Include function to sever the link thus making the classes, objects and

structure of universe A part of universe B. In effect this is a way of

quickly copying everything in one universe to another,

UniverseB

UniverseAUniverseA

LINKInclude

UniverseB

Included Universes

I l d d i b t f th i


167/168


Included universes become part of the new universe


168/168

Thank you