bo xi designer rc

7/26/2019 BO XI Designer RC

1/275

Universe Design XI

Module 1: Introduction to Designing Universes


2/275

2 Business Object XI R3 Designer

What You Will Be Able To Do

Understand the role of a Designer

Know what is meant by the Semantic Layer

Know more about the way usiness!b"ects

generates S#L

e familiar with the different ty$es of database

schemas you can use

Discover the recommended universe develo$ment$rocess

Know what is meant by the %&'2& conce$t


3/275

( Business Object XI R3 Designer

Extracting Information from a Database

Many different attem$ts have been made to resolve

issues surrounding re$orting: The Bureau Approach:

End Users

Developers

SQL

The SQL EducationApproach:

End Users

Developers

SQL


4/275

) Business Object XI R3 Designer

Information accessed

via a semantic layer

Database and Security

Desin

!orporate Database

End"User #eeds

Ease of use $eliability Interated reportin and

analysis tools

IS #eeds

Security and control %aintainability !ost"effective set"up Enterprise"&ide

interoperability

Universe Desin

Stoc*

+inance

Sales

The BusinessObjects olution

Designer En! Users


5/275

, Business Object XI R3 Designer

A!vantages of Using BusinessObjects

Users can access data in an easy&ay usin their o&n terminoloy

BusinessKnowledge

The orani'ation has a sharedbusiness content

Users can analy'e data locally

Users can ma(e )ueries &ithout(no&in SQL


6/275

- Business Object XI R3 Designer

Specific OLTPData Mart/Warehouse

PersonalOLAPServers

A!vantages of Using BusinessObjects

usiness!b"ects allows the user to access data fromdifferent sources using a single tool


7/275


8/275

% Business Object XI R3 Designer

$enerating %" using Des&to'Intelligence


9/275

Business Object XI R3 Designer

$enerating %" Using Des&to'Intelligence


10/275

1& Business Object XI R3 Designer



11/275


/ables to be included in the +rom clause and 3oins to be included in

the 4here clause of a Select statement are inferred via56



12/275




13/275

1( Business Object XI R3 Designer

$enerating %" using Des&to'Intelligence

7ormali8ed 9ggregate

/ablesStar

SchemaMulti$le

Stars

Snowfla*e

Data

4arehouses

roduction

Schema


14/275

1) Business Object XI R3 Designer

Using the Designer (o!ule

;ra$hic


15/275

1, Business Object XI R3 Designer

The Universe Develo'ment )rocess *+,

re$areKnow the datasource

=> onSybase

+inancialson !racle

lanDesign theuniverse(s)

9naly8eIdentify the needsof the end userpopulation


16/275

1- Business Object XI R3 Designer

The Universe Develo'ment )rocess *-,

/est

Using a test team (including

end users)

Im$lementCreate the universe(s)

0volve

Adapt and extend

universe over time

De$loy

Distribute the universe toend users


17/275

1. Business Object XI R3 Designer

01

21

Universe Develo'ment )rocess

Involve users in all the

ste$s of the $ro"ect


18/275

1% Business Object XI R3 Designer

The Universe Develo'ment )rocess Im$lementation Sub rocess:

!reate Universe file 3 set parameters

!reate Structure

Add tables 4 create 5oins 4 chec( interity 4sort loops and other problems as re)uired

!reate and cateori'e ob5ects,

Test Sort default * create custom hierarchies

!reate !ondition /b5ects 6, 72898;


19/275


What You .ave "earne!

/he advantages of using usiness!b"ects

/he role of a universe Designer

=ow usiness!b"ects generates S#L

/he ty$es of data source which usiness!b"ects caninterrogate

/he recommended design $rocess


20/275

Universe Design XI

Module 2: /he Designer Module


21/275



Log in to the Designer module

e familiar with the Designer module and its

commands

e able to mani$ulate the Universe Structure


22/275

Business Objects Designer


23/275

"ogging in to BusinessObjects Designer

pens D!"I#$!%with the speci&caccess rights of theuser'

2(


24/275

Designer (o!ule

bects

andClasses

ormula *ar

"tandard +oolbar

!diting+oolba

r

"tructure

2)


25/275



=ow to log in to the Designer module

4hat the Designer windows loo* li*e

=ow to mani$ulate the universe structure


26/275

Universe Design XI

Module (: Setting arameters


27/275




28/275


/reating a Universe

De0ne the )arameters

Insert Tables

(a&e the 1oins

2esolve the "oo's

/reate /lasses an! Objects

et u' .ierarchies


29/275


Select +ile arameters

/o begin creating a new universe: Select +ile 7ew

/o access the Universe arameters dialog bo? for an

e?isting universe:

or


30/275

(& Business Object XI R3 Designer

9 universe is identified with a user name and aconnection to the database

9 detailed descri$tion can also be added

etting u' )arameters 3 De0nition Tab


31/275

(1 Business Object XI R3 Designer

What Is a /onnection4

Definition: 9 connection is a lin* from the universe to the

target database

/he lin* is achieved using middleware @for e?am$le!D


32/275

(2 Business Object XI R3 Designer

Di5erent T#'es of /onnection

ersonal


33/275

(( Business Object XI R3 Designer

(6 Identify the driver to beused to access thetarget database

/reating a 6e7 /onnection

26


34/275

() Business Object XI R3 Designer

/hese o$tions allow you to set u$ the session

$arameters and the connection mode 666

A!vance! /onnection )ro'erties


35/275

(, Business Object XI R3 Designer

Summary of all connection $arameters

/ustom /onnection )ro'erties


36/275

(- Business Object XI R3 Designer


37/275

(. Business Object XI R3 Designer

Universe Default ave ettings

ou can change the default folder where universesare saved

ou can also set u$ Designer to automatically save at

s$ecified intervals

/hoose +ools, ptions3


38/275

(% Business Object XI R3 Designer

9ccess the


39/275


etting u' Universe )arameters

Definition /ab: name, description

and connection to the database

Summary /ab: author and

statistics about the universe

Strategies /ab: internal or

personal wizards to mae creating a

universe easier


40/275

)& Business Object XI R3 Designer

/he Summary tab dis$lays general information about

the universe

etting u' )arameters 3 ummar# Tab


41/275

)1 Business Object XI R3 Designer

rovides automatedstrategies for:

etting u' )arameters 3 trategies Tab


42/275

)2 Business Object XI R3 Designer

/hese allow you to limitthe si8e of results and

restrict the time allowed

for e?ecuting Bueries

etting u' )arameters 3 /ontrols Tab

/he Su$ervisor

can change these

$arameters for

s$ecific grou$s orusers


43/275

)( Business Object XI R3 Designer

S#L $arametersare used to define

the limits of the

S#L that may be

generated by theuniverse

/he Su$ervisor

can change these

$arameters fors$ecific grou$s

and users

etting u' )arameters 3 %" Tab


44/275

)) Business Object XI R3 Designer

0nablesdynamic lin*s

with other

universes

etting u' )arameters 3 "in&s Tab


45/275

), Business Object XI R3 Designer


/he two com$ulsory $arameters to begin creating a

universe are : 9 user name

9 connection to the database 9 universe is connected to a single database

/here are many $arameters that you will learn more

about later in the course

/he Su$ervisor can modify some $arameters fors$ecific grou$s and users


46/275

Universe Design XI

Module ): o$ulating the Structure with /ables


47/275

). Business Object XI R3 Designer


9dd tables to the Structure

Move tables

Know about different ways of viewing tables

e aware of how to o$timi8e tables


48/275

)% Business Object XI R3 Designer

A!!ing Tables


49/275



50/275

,& Business Object XI R3 Designer

/ustomi8ing Table Insertion

Select /ools !$tions then clic* on the Database tab

+rom here you can select and

deselect o$tions related to

table insertion

ou can set internal

strategiesto: automatically e?tract "oins

detect cardinalities

create ob"ects when

inserting tables


51/275

Universe Design XI

Module ,: 3oins


52/275

,2 Business Object XI R3 Designer


Set eBuiE"oins manually

Delete and modify "oins

Fiew "oins in List Mode

Set cardinalities

e able to set outer theta and selfErestricting "oins

Set strategies for automated "oins


53/275

,( Business Object XI R3 Designer

What !o 1oins Achieve in %"4


54/275

,) Business Object XI R3 Designer

1oins

9 "oin is a condition that restricts the result set of amultiErelational Buery

0BuiE"oin @otherwise *nown as a standard or inner

"oinA

/here are several different *inds of "oin:

/heta "oin

Self restricting "oin

!uter "oin


55/275

,, Business Object XI R3 Designer

E9ui:1oins

/ ti ! D l ti I 1 i


56/275

9 "oin can be entered manually using two methods:

/reating an! Deleting Inner 1oins(anuall#

4ith the menu o$tionInsert 3oins and the 0dit

3oin bo?

;ra$hically

/o delete a "oin clic* on the "oin line and $ress

Delete

,- Business Object XI R3 Designer


57/275

,. Business Object XI R3 Designer

Automatic 1oin Detection

/he Strategy for automatic detection of "oins is based

on common column names between tables

Smart Matching


58/275

,% Business Object XI R3 Designer

Outer 1oins


59/275


/reating Outer 1oins

9n outer "oin is created by converting an e?isting eBuiE"oin

-arning. uter oins

should ideally only bespeci&ed at the end of atable path' If speci&edin the middle of a tablepath all subse/uent oins

in the path will also haveto be speci&ed as outer;


60/275

-& Business Object XI R3 Designer

Theta 1oin 9 theta "oin contains an e?$ression that is based on

something other than eBuality:

Theta


61/275

-1 Business Object XI R3 Designer

/reating Theta 1oins

9 theta "oin is created by converting an e?isting eBuiE"oin

/T2":/"I/


62/275

-2 Business Object XI R3 Designer

elf 2estricting 1oin /his is not really a "oin at all6 It is a method used to set a

restriction on a table in the universe Structure6


63/275

-( Business Object XI R3 Designer

/reating elf 2estricting 1oin


64/275

List Mode dis$lays tables "oins and conte?ts

Using "ist (o!e

-) Business Object XI R3 Designer

It is $ossible to identify "oins related to a s$ecific table


65/275

Shows the relationshi$ between tables on the basis of

the "oin

1oin /ar!inalities

-, Business Object XI R3 Designer


66/275

9utomatically using @but can ta*e a long timeA

A!!ing /ar!inalities

-- Business Object XI R3 Designer

Manually using the 0dit 3oin dialog bo?


67/275

-. Business Object XI R3 Designer

9lways chec* integrity after defining "oins

/hec&ing Integrit#

Be7are=


68/275

-% Business Object XI R3 Designer

Testing

>0M0M0>: !nce you have created the ob"ects for

your universe you must ma*e e?tensive multiE

relational Bueries to chec* that the "oins are

$roducing the S#L out$ut intended


69/275



=ow to set different ty$es of "oins ta*ing into accountusersG needs and technical constraints

=ow to set cardinalities

/o always chec* integrity after defining "oins and

cardinalities


70/275

Universe Design XI

Module -:


71/275

.1 Business Object XI R3 Designer


!rgani8e the universe into classes and subEclasses


72/275

9n ob"ect is the most refined com$onent in a

universe6 It ma$s to data or a derivation of data in thedatabase6

.2 Business Object XI R3 Designer

Objects

Dimensions

0roects columns from the database which

are 1eyto a /uery

Details

0roects columns from the database thatprovide detailed information related to a

dimensionMeasuresContains aggregates to proect statistics


73/275

/lasses

.( Business Object XI R3 Designer

'A class is a logical grou'ing ofobjects 7ithin a universe; Ingeneral> the name of a classre?ects a business conce't thatconve#s the categor# or t#'e of

objects;

A class can be further !ivi!e! intosubclasses;As !esigner> #ou are free to !e0nehierarchies of classes an!

subclasses into a mo!el that bestre?ects the business conce'ts of#our com'an#;


74/275

The /lasses an! Objects Win!o7

.) Business Object XI R3 Designer

!rder of dimensions

in a class

hierarchically

Details are attached

to dimensions


75/275

The /lasses an! Objects Win!o7

., Business Object XI R3 Designer

Measures are grou$ed ina se$arate class

0?ce$t where they canonly be used with ob"ectsfrom a given class


76/275

Use tocreate a class

Use theDescri$tion fieldto $rovideinformation forusers

/reating an! E!iting /lasses

.- Business Object XI R3 Designer


77/275

SubEclasses allow a better

organi8ation of ob"ects

9void too many levels of

subEclasses

Use the S$eedmenu on a

class to create a subEclass

/reating a ub:/lass

.. Business Object XI R3 Designer

i l f bl


78/275

/reating a /lass from a Table

Use Drag and Dro$

.% Business Object XI R3 Designer

/his wi8ard will create one ob"ect for each field

/ i Obj


79/275

Different 4ays: Manually with

. Business Object XI R3 Designer

Drag and dro$ from a database column into a class

Insert ob"ects from another universe @co$y and $asteA

/reating an Object

Obj ) i Th D 0 i i T b


80/275

Object )ro'erties 3 The De0nitions Tab

%& Business Object XI R3 Designer

y default thety$e is the same

ty$e as used by

the database

9dd a descri$tion

to the ob"ect

Inferred S#L for

Select statement

Th l t ! Wh E!it Wi !


81/275

The elect an! Where E!it Win!o7s

%1Business Object XI R3 Designer

Inferred S#L

ic* Lists

Obj t ) ti Th ) ti T b


82/275

Object )ro'erties 3 The )ro'erties Tab

Define the ty$e of

ob"ect

%2Business Object XI R3 Designer

9ssociate a List of

Falues for end usersG

conditions if

a$$ro$riate

Obj t ) ti Th A! ! T b


83/275

Object )ro'erties 3 The A!vance! Tab

Unchec* the Sort o$tion

%(Business Object XI R3 Designer

/ i ! ) ti Obj t


84/275

%) Business Object XI R3 Designer

ou canco$y ob"ectsfrom oneuniverse toanother

/o'#ing an! )asting Objects

@i ! ! 2 l


85/275

%, Business Object XI R3 Designer

ou can use the +indfunction to locatecharacter strings inob"ects and theredefinitions

@in! an! 2e'lace

ou can also use the+ind function in

con"unction with the>e$lace function toedit strings

/h &i I t it


86/275

>emember to chec* integrity after creating ob"ects

/hec&ing Integrit#

%- Business Object XI R3 Designer

T ti Obj t


87/275

%. Business Object XI R3 Designer

Testing Objects

4hile develo$ing a universe observe the

following $roduction cycle

Save UniverseTest Universe

%odify Universe

Testing Objects in 2E)O2TE2


88/275

erform as many tests as $ossible in >0!>/0>:un Bueries and chec* the results

Testing Objects in 2E)O2TE2

%% Business Object XI R3 Designer



89/275



!rgani8ing the universe into classes and subEclasses

to reflect the business usage


90/275

Universe Design XI

Module .:


91/275



Understand what a measure ob"ect is

Know how to test measure ob"ects


92/275


What is a (easure Object4

9 measure ob"ect returns numeric information

9 measure ob"ect is created by using aggregate

functions

/he five basic aggregate functions are:

"um

Count

2aximum

Average

2inimum

A (easure is D#namic


93/275


A (easure is D#namic

Measure ob"ects are semantically dynamic

.o7 a (easure Wor&s at elect "evel


94/275


*+,

.o7 a (easure Wor&s at elect "evel


95/275


*-,

"evels of Aggregation in Business


96/275


Objects

#elect

database

(roject

$uer& Results

)ggregation

)ggregation

Aggregation at )rojection "evel


97/275

. Business Object XI R3 Designer

Aggregation at )rojection "evel

4hen $ro"ecting all variables in the microcube no

aggregation ta*es $lace

4hen $ro"ecting only some variables from the

microcube aggregation occurs

etting elect )rojection Aggregates


98/275


etting elect )rojection Aggregates

Statistically only certain select ' $ro"ect aggregates

are com$atible6

"elect Aggregate %ecommended0roect Aggregate

"um "um

Count "um

Average $one or Average (notrecommended)

2aximum 2aximum

2inimum 2inimum

(easure Object )ro'erties 3 De0nitions


99/275

Business Object XI R3 Designer

(easure Object )ro'erties 3 De0nitions

Data /y$e must be a

number

Select must be anaggregate

(easure Object )ro'erties 3 )ro'erties


100/275

1&& Business Object XI R3 Designer

(easure Object )ro'erties 3 )ro'erties

!b"ect /y$e mustbe a measure

9ggregate +unction

must be

a$$ro$riate for the

Select aggregate

Measures should

not have an9ssociated List of

Falues

ie7ing Object )arent Table*s,


101/275

1&1 Business Object XI R3 Designer

ie7ing Object )arent Table*s,

ou can view the $arent tables of an ob"ect by rightE

clic*ing on an ob"ect and selecting the Fiew 9ssociated/able o$tion

Testing (easure Objects


102/275


/here are three elements to testing a dimension or detail ob"ect :

Testing (easure Objects

Measure ob"ects need more thorough testing :

3 Chec1 obects exist'

4 Chec1 inferred "56'

7 Chec1 /uery results'

3 Chec1 obectsexist'

4 Chec1 inferred"56'

7' Chec1 /ueryresults'

8' %epeat withotherdimensions'

9 2a1e a /uerywith aminimum oftwo dimensionsand a measure'

:' Chec1proection with"lice ; Dice'

Testing (easure Objects at elect "evel


103/275

1&( Business Object XI R3 Designer

=$/U. B> !ountry,country

=$/U. B> !ountry,country8

$eion,$eion?#ame

Testing (easure Objects at elect "evel

Testing (easure Objects at )roject


104/275

1&) Business Object XI R3 Designer

"evel

An Aggregation )roblem


105/275

1&, Business Object XI R3 Designer

An Aggregation )roblem

/he ;rou$ y clause grou$s each distinct dimension attribute and

$roduces a single measure value for that grou$6 If you are not carefulwhen creating a Buery with dimensions and measures this can result

in misleading information6



106/275

1&- Business Object XI R3 Designer


9 measure always has an S#L aggregate function in

the Select statement

9 $ro"ection function can be associated with ameasure to ensure local aggregation in the microcube

0?tensive testing of measure ob"ects is reBuired


107/275

Universe Design XI

Module %: >esolving Loo$s in a Universe



108/275

1&% Business Object XI R3 Designer


Define what a Loo$ is

*e able to resolve recursive table structure loops

*e able to use "hortcut oins and 1now when to use

them as an alternative for resolving loops

Identify when in the design process you resolve loops

Use Designer tools to resolve loops using Aliases andContexts

Detect and recogni


109/275


What is a loo'4

9 loo$ e?ists when the "oins between tables form a continuous $ath

.o7 to !eal 7ith loo's


110/275


.o7 to !eal 7ith loo's

ne of two routines can be used to resolve most loop

situations in the universe structure window'

Alias Detection%outine

ContextDetection

%outine

'''and'''

2ust be done prior tousing detection

routines and donecorrectly' therwise,routines mayrecommend incorrectsolution'

"et Cardinality2anually for All =oins

/ar!inalit# Detection


111/275


/ar!inalit# Detection

Cardinality not set. "et Cardinalities.

Do this manually.

What is an Alias 4


112/275


What is an Alias 4

9n 9lias is an e?act du$licate of the original table

with a new name6 /he data in the table is e?actly thesame6

/he 9lias is used only to resolve the loo$ in the

structure of the universe6 /here is no im$act on theschema of the database 0asy to define

0asy to maintain

0asy to use

When to Alias


113/275


When to Alias

9 loo$ with a single

loo*u$ table shouldbe resolved by an

alias

A loo1up table can be

identi&ed by itscardinality

6 6

6

6

6

+ +

+

+

+

A loo1up table onlyhas the >one? end of

oins attached to itAlias needed here

.o7 to Alias


114/275


o o as

Designer routines

detect loops andcandidates foraliases

*rea1 the loop by

creating an alias ofthe loo1up table foreach side of the loop

"ome designers li1e

to create an aliasfor both sides of theloop'

Do not remove theoriginal table

Detecting an! /reating Aliases


115/275


g g

Use the Alias Detection routine

2anually insert an alias

Use the 6oop Detection routine

+o create an alias table to brea1 a loop, you can.

Using automatic loo' !etection


116/275


g '


117/275


g

Clic1 the Detect Aliases button

+he routine lists

candidate Aliastables

@ou can rename

the Alias tables ifre/uired

Inserting an Alias (anuall#


118/275


g #

"elect the table and clic1 the Insert Alias button

$ame the Alias table and clic1 K

+hen reset the oins manually

/hoosing 7hich Alias (etho! to Use


119/275


g

Method 9dvantages Disadvantages

Detect Loo$s


120/275


g g

@ou can list all aliases in a universe via the +ools

6ist of AliasesB' Drop down menu option'

@ou can also rename an alias via this panel'

Aliases 3 Ti!#ing U' "oose En!s


121/275


# g '

A single obect /uery specifying either the Country of

Client, "howroom or 2a1er will include all countries(Client, "howroom and Car 2a1er countries)'

+o avoid this you can force a oin to the subse/uenttable (client, showroom or ma1er) and thereby forcethe /uery to restrict it ?s output to the relevantcountries for that obect'

@orcing A!!itional 1oins


122/275


g 1

@ou can restrict the data that is returned for an obect

by specifying additional tables in the obect properties'

@ou do this in the+ables box

+he restriction is createdfrom the oins between

the tables

"elect the relevanttable.

Only when this is done for each object relating to a multi-lookup table will they return the correct results if used in asingle object query

Using Aliases in a (ulti tar situation4


123/275


g

$ormali


124/275


If you try to resolve the loop using Aliases.

there is still a loopAll candidates for

Aliases



125/275


and you get duplication of obects



126/275


+he eEective result is two universes.

"alesUniverse

%entalsUniverse

2esolving "oo's using /ontexts


127/275


Customers

"ales "al6ines

6oans 6oans6ines

Country

+here are two possible routesthrough the structure.

"aleF2odel context

%entalF2odel context

A context is merely a collection of A66 the oins on asingle route'Context name G table name on a route with only Hmanycardinality'

2esolving "oo's using /ontexts


128/275


Rental_Model context

Sale_Model context

!ach contextrepresents what may

be inferred in asingle "!6!C+statement'Any /uery whichinfers some "56code exclusive to

one context andsome exclusive tothe other will infertwo separate"!6!C+ statements

A context is

detected for eachroute on which thereis a table with ustHmany cardinality'

Detecting an! /reating /ontexts


129/275


HDetect Contexts detects andproposes a list of contexts to create

6oop Detection routine. suggestscandidates for both aliases and contexts

HInsert Contexts inserts a contextmanually

Dis'la# the contexts 3 ie7 "ist (o!e


130/275

1(& Business Object XI R3 Designer

E!iting /ontexts


131/275

1(1 Business Object XI R3 Designer

Double clic1 the context in the 6ist 2ode window

+he context name

+he highlighted oinsare included in thecontext

+he descriptionappears in the Usermodule Jelp panel

"oo' Detection routine : the !ra7bac&


132/275


-hen you use 6oop Detection and detect a number of

loops.

+he routine does not oEer the Alias candidates &rst,

so you may have to update the Contexts after youhave added the Alias tables

6oop 3 of 3

e9uence for resolving loo's


133/275

1(( Business Object XI R3 Designer

3' "et cardinality on all oins (best to do this manually)

4' Use Detect Aliasesto detect candidates for aliases

7' Insert all re/uired alias tables and oins

8' Use Detect Contextsto detect candidates for contexts

9' Create the re/uired contexts

:' +est in the User module

hortcut 1oins


134/275

1() Business Object XI R3 Designer

If a /uery includes

Client and Country but$+ %egion, the%egion oins are stillneeded in the "56'

*ut oining Country toClient directly createsa loop

IneEecientL

hortcut 1oins : the solution


135/275

1(, Business Object XI R3 Designer

!dit the oin to create a "hortcut oin.

+his is not a 6oopL

*e aware of existing Contexts when you add the oin."hortcut oins are not automatically added

2ecursive table structures


136/275

1(- Business Object XI R3 Designer

+hese occur when a table acts as a loo1up for itself

!ach !mployee has a 2anager, who is also an !mployee

*ut adding a "elf =oincreates a single table

loop where thecardinality is un1nown

+hese loops must beresolved manually

2ecursive table structures : thesolution


137/275

1(. Business Object XI R3 Designer

solution Create an Alias of the loo1up table

2anually set the cardinality

+est the results in the user module

Test the structure of a universe


138/275

1(% Business Object XI R3 Designer

Chec1 the syntax

+est in the User 2odule



139/275


4hat a Loo$ is

Jow and when to resolve a loop using aliases andcontexts

+he se/uence for resolving loops

Jow to apply shortcut oins

Jow to resolve a selfoin


140/275

Universe Design XI

Module :


141/275

1)1 Business Object XI R3 Designer

Understand the $ur$ose of using conte?ts in auniverse

>ecogni8e and be able to resolve ecogni8e and be able to resolve +an /ra$s

What are /ontexts


142/275


9 conte?t is sim$ly a list of "oins denoting a $ath

between tables6


143/275

1)( Business Object XI R3 Designer

9lternative routes do 7!/ only e?ist in loo$ scenarios6

Loo$* Routes + * onte-ts

onte-t .

onte-t *

+or*

onte-t .

onte-t *

* Routes + * onte-ts

.o7 /ontexts are Detecte!


144/275

1)) Business Object XI R3 Designer

9 se$arate conte?t is identified for each table with

only the manyG end of "oins attached:

/he "oins in a conte?t are identified by wor*ing bac*

from the table with only the manyG end of "oins

attached E manyEone manyEone6

I!entif#ing ho7 man# /ontexts arere9uire!


145/275

1), Business Object XI R3 Designer

9 ou can arrange your universe structure so that all "oins are flowing

from the manyG ends at the left to the oneG ends at the right6

6umber ofcontexts

re9uire! -

I!entif#ing the joins that ma&e u' a/ontext


146/275

1)- Business Object XI R3 Designer

/he forward flowing "oins form the Sale conte?t 7o "oins flowing

bac* from one tomany are included

Wh# A''l# /ontexts


147/275

1). Business Object XI R3 Designer

/o resolve +an /ra$s

/o avoid


148/275

1)% Business Object XI R3 Designer

+or a


149/275


Multi$le instances of a single dimension in results

a Buery

with

ob"ects

from each

of the

manyGtables

te' - te' +

Deny Multi$le S#L Statements for each measure

te'

many

to one

to

manyG

/hasm Tra' )roof 3 E5ect


150/275

1,& Business Object XI R3 Designer

Test +

Test -

Test

/hasm Tra' )roof 3 %"


151/275

1,1 Business Object XI R3 Designer

Test +

Test -

Test

The problem on test 9 arises because the processin of a sinle

SELE!T statement produces a sinle virtual loical table toapply areation,

/hasm Tra' )roof 3 %" "ogical Table


152/275

1,2 Business Object XI R3 Designer

Test Test +

@here you have a many-one-manyrelationship for tables in the $/% clause

the resultin loical table produces somethin a(in to a !artesian .roduct,

/nly then is areation applied, This is the reason for the chasm effect,

/hasm Tra' 3 olution


153/275

1,( Business Object XI R3 Designer

=ow can we avoid the chasm tra$

y inferring two se$arate S0L0


154/275

1,) Business Object XI R3 Designer

1 9lter the S#L $arameters for the Universe

2 Use


155/275

1,, Business Object XI R3 Designer


156/275

1,- Business Object XI R3 Designer

1A I7E9


157/275

1,. Business Object XI R3 Designer

9$$ly a conte?t to each leg of the


158/275

1,% Business Object XI R3 Designer

4ith the conte?ts in $lace both measure ob"ect

Bueries and dimension ob"ect Bueries dis$laycorrectly:


159/275


+or a +an /ra$ to occur there must be:

J

/hen a "uer& is run which uses objectsand

the in!erred #$% includes tables and


160/275

1-& Business Object XI R3 Designer

+or a +an /ra$ to occur there must be:

te' +

one to

many tomanyG

a Buery

with a

measure

ob"ect from

the Sale Hanother

from the

SaleNModel

table

te' -

Multi$le SaleNModel rows related to a single Sale row

/lassic @an Tra' )roof 3 E5ect


161/275

1-1 Business Object XI R3 Designer

Test +

Test -

/lassic @an Tra' )roof 3 %"


162/275

1-2 Business Object XI R3 Designer

Test +

Test -

The problem on test 2 arises because theprocessin of a sinle SELE!T statement

produces a sinle virtual loical table to

apply areation,

/lassic @an Tra' )roof 3 %" "ogicalTable

Test + Test -


163/275

1-( Business Object XI R3 Designer

@here you have a one-many-manyrelationship for tables in the $/% clausethe resultin loical table produces somethin a(in to a !artesian .roduct,

/nly then is areation applied, This is the reason for the fan effect,

Test + Test -

/lassic @an Tra' 3 olution


164/275

1-) Business Object XI R3 Designer

=ow can we avoid the fan tra$

y inferring two se$arate S0L0


165/275

1-, Business Object XI R3 Designer

1 9lter the S#L $arameters for the Universe

2 Use a combination of 9liases and


166/275

1-- Business Object XI R3 Designer


167/275

1-. Business Object XI R3 Designer

1A I7E9


168/275

1-% Business Object XI R3 Designer

(A Set


169/275


9lias H


170/275

1.& Business Object XI R3 Designer

7ow a Buery involving a measure and

another ob"ect from a subseBuent table inthe table $ath of a universe structure56

556results in 2 S0L0


171/275

1.1 Business Object XI R3 Designer

J

9

estrictions


e able to a$$ly restrictions to ob"ects


175/275

1., Business Object XI R3 Designer

Know when it is a$$ro$riate to use each of these

techniBues

e able to a$$ly restrictions to ob"ects

e able to create condition ob"ects

e able to a$$ly restrictions to tables

e able to restrict ob"ects using additional "oins


176/275

Universe Design XI

Module 11: Using O +unctions

.o7 The /ourse is Organi8e!3 Da# -

% > l i L i U i


177/275

1.. Business Object XI R3 Designer

%6 >esolving Loo$s in a Universe

6 >estrictions

1&6 Using O +unctions

116 Lists of Falues

126 =ierarchies



178/275

1.% Business Object XI R3 Designer

Know what O +unctions are available

7ote: O9ggregate9ware is covered later in the course

e able to a$$ly them

Know what O +unctions do

The F @unctions

/he O +unctions available are:


179/275


/he O +unctions available are:

/hese +unctions are a$$lied

in the Select and 4here bo?es

of ob"ects

/hey are used to $rovide

fle?ible methods of s$ecifying

S#L

F)rom't Orom$t is $laced in an ob"ect as $art of the Select or 4here


180/275

1%& Business Object XI R3 Designer

$ro$erties

4hen a Buery is run that includes the ob"ect the O$rom$t of the ob"ect

forces a $rom$t bo? to a$$ear

F)rom't #ntax

SHOWROOM SHOWROOM NAME = @PROMPT


181/275

1%1 Business Object XI R3 Designer

SHOWROOM.SHOWROOM_NAME = @PROMPT

Free or constrained (to value in o!".. #onstrained

$Enter S%o&roo' Na'e)T%e *ro'*t++++++++++++.

$A),ata T-*e (A) N or ,"..+++++++.

$S%o&roo'S%o&roo')o! Pointer..+++++++++++..

Or %ardcoded list / 0$A)$1)$#2

Mono)Mono or 'ulti (o! selection"+++..

(

"

O*erator de*endent on o*erand

Felect OSelect function acts as a $ointer to the Select bo? of another ob"ect:


182/275

1%2 Business Object XI R3 Designer

OSelect @


183/275

1%( Business Object XI R3 Designer


184/275

1%) Business Object XI R3 Designer

the


185/275

1%, Business Object XI R3 Designer

a te?t file to define UserEs$ecific conditions in an ob"ect:

#/1usinessO34ects1uso34.e5e 6vars 1ovars.t5t

#O7NTR8 = 9APAN

Fariable : 7ith )ersonal @iles3Dra7bac&s >eBuires locali8ed administration of the te?t file by the


186/275

1%- Business Object XI R3 Designer

eBu es oca ed ad st at o o t e te t e by t e

Designer ' Su$ervisor

/he command string must be changed on every

User Gs < to include the Evars Pte?tfile6t?tQ argument

Security can be a $roblem as a te?t file on a < is

o$en to local amendment


187/275

1%. Business Object XI R3 Designer

usiness!b"ects variables to define UserEs$ecific

conditions in an ob"ect:

1O7SER

1OPASS

W%ere clause/E'*lo-ees.E'*lo-ee_Na'e = @!aria3le($1O7SER"

Restricts data returned to t%at relatin: to t%e 7sers lo:in na'e

Fcri't

9llows use of a variable declared in a F9 scri$t


188/275

1%% Business Object XI R3 Designer

$

/he scri$t smotors G runs the country selection $rocess



189/275


4hat O functions are available

4hat each O functions does

=ow to a$$ly O functions to enhance the fle?ibility of

a universe

.o7 Data is 2estricte!

/he 4here clause in an S#L statement restricts the


190/275


/he 4here clause in an S#L statement restricts the

number of rows returned in the result set:

W.E2E;;; join !e0nitions ;;;

W.E2E;;; join !e0nitions ;;;A6D /ountr#GUnite!


191/275


4here clause in different ways:Designers: Users:

/here clause in objects9reating a

condition object9

=sing a condition

object9

#el!>Restricting ?oins9

)dditional ?oin

In!ormation9

De!ining a condition9

@iltering a report9

2estricting Objects

9dding a restriction to an ob"ect allows you to give a


192/275


9dding a restriction to an ob"ect allows you to give a

more $recise definition:

2estricting Objects3 the Dra7bac&s

ou have to add a new ob"ect for each se$arate


193/275


Multi$le ob"ects $revent you from building logical

default hierarchies6

" $

restriction6

/he restrictions are not obvious to the end user6

If a combination of similarly restricted ob"ects isincluded in a Buery no results are $roduced because

the conditions conflict:

The User ex'ects !ata for both @rench an!$erman clients> but gets no results> becauseno client is both @rench an! $erman

@orexam'le3

2estricting Objects3 A!vantages

/he one advantage of a$$lying restrictions to ob"ects


194/275


g $$ y g "

is that the User is automatically forced to a$$ly therestriction E no choice6

!n balance it is better to avoid a$$lying restrictions to

an ob"ect unless this is absolutely necessary6

/his assists with ease of use6

2estricting Objects : a Wor&aroun! If you a$$ly restrictions to ob"ects for Sales >evenue

1% d 1


195/275


1% and 1:

/hese drawbac*s a$$ly: multi$le ob"ects conflicting

restrictions6

2estricting Objects : a Wor&aroun! Use conditional Select clauses rather than restrictions

b" t


196/275


on ob"ects:

Multi$le ob"ects but no conflicting restrictions

/on!ition Objects

Useful for com$le? conditions and for freBuently used


197/275


Useful for com$le? conditions and for freBuently used

conditions

etter than a$$lying restrictions to !b"ects because

the User can choose to add the condition

7o multi$le ob"ects


198/275


"

Insert a


199/275


switch between 2 or more domains you can a$$ly a

restriction to the table using a Self >estricting 3oin

The A!vantage of using Table2estrictions /he restriction is a$$lied whenever the table is inferred


200/275

2&& Business Object XI R3 Designer

in the S#L irres$ective of where in the S#L statementthe table is inferred6

+or e?am$le if the table only a$$ears in the +>!M

clause the restriction still a$$lies in the 4=0>0

clause6

(ulti )ur'ose "oo&u' Tables


201/275


9 Buery 4hich countries do our clients come fromG

may also include countries that are Showroom

countries or


202/275


by s$ecifying additional tables in the ob"ect $ro$erties6 ou do this in the

/ables bo?

/he restriction is created

from the "oins between

the tables

Select the relevant

table:

When to Use each 2estriction (etho!

9$$ly >estrictions to !b"ects when you need to force


203/275

2&( Business Object XI R3 Designer

a restriction which is not automatically inferredwhenever the table is included in the S#L6

Use


204/275

2&) Business Object XI R3 Designer

restrictions on ob"ects

=ow to use $redefined


205/275

Universe Design XI

Module 12: List of Falues

What You Will Be Able To Do 9ssociate or remove a List of Falues @LoFA for an

b" t


206/275

2&- Business Object XI R3 Designer

ase a LoF on a $ersonal file

ob"ect


207/275

2&. Business Object XI R3 Designer

9 LoF is used on the o$erand side of a condition in

the Buery $anel of the User module

/his is only available if set by the designer

columns to which the ob"ect refers

.o7 !o "ists of alues 7or&4

9 designer can create a LoF which is based on:


208/275

2&% Business Object XI R3 Designer

9 designer can create a LoF which is based on:

9 Buery of the target database

9 constant set of values held in a file

In both cases the result is stored locally in a file on

the User Gs


209/275


y default

9ssociate a List

and 9llow Users to

edit are chec*ed:

It is im$ortant to

unchec* this bo?

for ob"ects thatdonGt need a List

/ontrolling .o7 "ists are 2efreshe!

7ormally the first time a LoF is used in a User login


210/275


session the system fires a Buery at the targetdatabase6

/he results of this Buery are used to $o$ulate the list

and are stored in the 6lov file6

/hereafter the 6lov file from this Buery is used each

time the List is reBuired6

/ontrolling .o7 "ists are 2efreshe!


211/275


7ot normally used E

unchec* this bo?


212/275


condition to the LoF

ou can sim$lify the $rocess of choosing a value for

Users by creating a hierarchy for the LoF

ou can su$$ly a $ersonal data file containing the

values for the list instead of using the results of the

Buery

A''l#ing a /on!ition to a "ist of alues


213/275


9$$ly the condition in the #uery

anel:

/reating a .ierarch# for a "ist of alues


214/275


lace the hierarchy ob"ects @whichmust be sortedA to the right of the

LoF ob"ect in the #uery anel:

/reating a .ierarch# for a "ist of alues /he resulting =ierarchical Fiew of the LoF ma*es it

easier to select the reBuired value:


215/275


easier to select the reBuired value:


216/275


Select the ob"ect:

Select ersonal Data:

Basing a "o on a )ersonal @ile


217/275


S$ecify the file that contains the values for the list

and clic* !K


=ow to associate or remove a LoF for an ob"ect


218/275



219/275

Universe Design XI

Module 1(: =ierarchies


!rgani8e Default =ierarchies for o$timum usability


220/275


/est =ierarchies in the User module


221/275


U,,

#orth South

Liverpool %anchester #e&castle London Southampton Bristol

Level in +ierarchy Data $eturned

9 Default =ierarchy is the hierarchy based on the

order of the !b"ects within the


222/275


"

Default +ierarchies arerepresented in the User

module by the order in &hichDimension /b5ects areorani'ed in the !lasses and/b5ects bo- of the Query.anel

The


223/275


Dimension !b"ects are organi8ed from the mostgeneral to the most s$ecific within the


224/275


Top Level

Level C

Level 2

Level 9

9 Measure can be analy8ed at each level

9


225/275


Default +ierarchies

!ustom +ierarchy

/reating /ustom .ierarchies


226/275


9dd !b"ects from Default =ierarchies to build a new


227/275


7o Default =ierarchies are shown

The E5ect of /ustom on Default.ierarchies Selected Default =ierarchies can be added to the


228/275


Wh# Is Time A 'ecial /ase4


229/275


Sale Date26*CC*1

%onth >ear

Quarter

Day

/reating Time .ierarchies


230/275

2(& Business Object XI R3 Designer

9utomatic /ime =ierarchies

Using Database +unctions

/able ased /ime =ierarchies


=ow to organi8e Default =ierarchies for o$timum


231/275


=ow to organi8e Default =ierarchies for o$timum

usability

=ow to create


232/275

Universe Design XI

Module 1): 9ggregate 9wareness


Understand the reasons for using 9ggregate


233/275

2(( Business Object XI R3 Designer

9wareness

Know when to a$$ly 9ggregate 9wareness

e able to a$$ly 9ggregate 9wareness

What is Aggregate A7areness

Some databases have Summary /ableswhich contain


234/275

2() Business Object XI R3 Designer

figures aggregated to a high level6

/hese are used to s$eed u$ Bueries which contain

statistics @for e?am$le >evenueA re$orted at for

instance year rather than event level6

9ggregate 9wareness is the usiness!b"ects

$rocess by which these higher level aggregates are

incor$orated into a universe6

ummar# Tables


235/275

2(, Business Object XI R3 Designer

/he other columns relateto ob"ects that reBuire

O9ggregate9ware

definitions

+oreign Key columns

are used for the "oins

7ote that Summary /ables without +oreign Keys donot need "oins E they can be free floating tables6

.o7 ummar# Tables are use! in %" 9ggregates of a normali8ed database are based on event ' fact level

data6Sale SaleNModel Model


236/275

2(- Business Object XI R3 Designer

22- rows 2(( rows (( rows

Sales >evenue R sum@S9L0NM!D0L6S9L0N#/ M!D0L6M!D0LN>I


237/275

2(. Business Object XI R3 Designer

set "oins and cardinality

2 Set the conte?ts

( >edefine ob"ects using O9ggregate9ware

) Define incom$atible ob"ects using 9ggregate

7avigation

te' +3 Inserting a ummar# Table C etting1oins


238/275

2(% Business Object XI R3 Designer

9dd the Summary /able to the structure

Set the "oins and the

cardinality

te' -3 Detecting /ontexts


239/275


Set the conte?ts /he 9nnualN+iguresconte?t

te' 3 2e!e0ning Objects

0dit the ob"ects affected by the Summary /able6


240/275

2)& Business Object XI R3 Designer

O9ggregate9ware Synta?: O9ggregate9ware@Definition1Definition25Definition7A

+rom the most to the least 9ggregated

/he last definition must be valid for all the Bueries

te' 3 Incom'atible Objects

9ggregate aware ob"ects can only be com$atible with ob"ects derived

from tables in the same conte?t as the summary table


241/275


Incom$atible ob"ects are s$ecified using 9ggregate 7avigation

te' 3 Aggregate 6avigation

/he 9ggregate 7avigation bo? is o$ened from the

/ools menu


242/275


Select the Summary

/able:


243/275

2)( Business Object XI R3 Designer

>un Bueries using the aggregated measures from the

Summary /able6

Use both com$atible ob"ects and incom$atibleob"ects in different Bueries to ma*e sure all levels of

9ggregate 9wareness are o$erating correctly6

Aggregate A7areness as )referential/o!ing /he aggregate awareness functionality in

usiness!b"ects can be viewed sim$ly as a method


244/275

2)) Business Object XI R3 Designer

of s$ecifying $referential or conditional coding6

4hen viewed from this $ers$ective you can begin to

see the true $otential of aggregate awareness

functionality within the Designer module6

9ggregate awareness functionality can be used for

$ur$oses other than ta*ing into account summary

tables to im$rove the efficiency of a universe6

Using Agg; A7areness to resolve a @anTra'


245/275

2), Business Object XI R3 Designer

+an tra$s are generally resolved using the alias and

conte?t method e?$lored in the


246/275

2)- Business Object XI R3 Designer

/he 0fficiency Issue

/hilst this standard !an tarp

solution resolves the !an trapissue should objects A and are

used in the same "uer&, i! a "uer&

involves onl& objects Jandno

!an trap e-ists and &et table 9will

still be rocessed twice once as

=sing the standard method o!resolving a !an trap we would

have to alias table 9, create a

join !rom the alias 9nto table

9and set cardinalities, set

conte-ts and 9nC edit objectso that it re!ers to columns

in the alias 9nrather then

table 92J

9

9n

* An

J

9

structure onl& involves two tables,instead o! three2

2ecommen!e! olution

1A


247/275

2). Business Object XI R3 Designer

J

9

9n2A


248/275

2)% Business Object XI R3 Designer

9s the designer you must ma*e usiness!b"ects

aware of the correct level of aggregation to use6

It is im$ortant that you follow the $rocedure in the

correct seBuence:1 9dd the S/ set "oins and cardinalities62 Set the conte?ts6( 9$$ly O9ggregate9ware to affected ob"ects6) Set 9ggregate 7avigation6

9ggregate awareness functionality can also be usedto resolve issues other than that for which it was

originally intended6

U i D i XI


249/275

Universe Design XI

Module 1,: Documenting Distributing H

Maintaining a Universe


i t i f ti b t th i


250/275

2,& op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

rint information about the universe

Understand the Universe Distribution rocess

e able to e?$ort a universe to the >e$ository

Know how changes to the target database affect a

universe

Know how changes to ob"ects will affect e?isting end

user re$orts

Select the /ools !$tions menu then clic* on the rint

tab to select what to $rint

Documenting a Universe


251/275

2,1 op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Select the +ile rint menu to $rint

.hase 9

Universe Design /#cle


252/275

2,2 op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

/there are two ty$es of distribution: small and large scale

.hase 6

.hase

.hase

.hase

.hase C"2

Small Scale Distribution

mall cale Universe Distribution

S d i 0 M il User E5or

t


253/275

2,( op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Send 6unv via 0EMail


254/275

2,) op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

ile serverAccess controlledBy net&or( security

Business /b5ectsUniverse

%otors2(,unv7Shared !onnection;

S:FDesinerS:FTest

Business /b5ects

Universe

%otors2(,unv7.ersonal!onnection;

ave for All Users

-, /reate(i!!le7are Driver

/reate(i!!le7are

Driver

Enter'rise Distribution *ecure!,

Business /b5ects

U i

ull !lient

@ebi server


255/275

2,, op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Business/b5ectsrepositoryE-port

%otors2(,unv7Secured !onnection;

Business /b5ects

Universe

Supervisor in controlUser based security

allocated to user roups

las created *incremented

%otors2(,unv

Universe Domain #ame

%otors2(,unv

Universe Domain #ame

Universe

,unv flas

chec(ed&hen used

he Designer e-ports a universe to the universe domain and allocates

universe access to one o! the groups o! users he or she belongs to

Ex'orting a Universe


256/275

2,- op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

he !lags attached to the universe are incremental2 his guarantees the user

will use the most recent version o! the universe

DesignerDesigner

RepositoryRepository $niverse Do&ain

Docu&ent Do&ain

Securit! Do&ain

@ull /lient %uer# )rocess

Universe Designer

C usiness!b"ectsCusiness!b"ects , &CLocData


257/275

2,. op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

>e$ository

Database

6unv6unv

6unv

S#L

6re$

5Cusiness!b"ects Cusiness !b"ects ,6&CUniverse CPUniverseDomain 7ameQ

+ull


258/275

2,% op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

>e$ository

Database

6unv6unv

=//

S#L

6html

6html

/hin


259/275

2, op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

/ables deleted changed or renamed in database Users reBuest new classes or ob"ects

+ip. Do not distribute new versions ofuniverses too fre/uentlyL

$ote. @our primary concern when you

introduce a new version of a universeshould be what eEect it will have onexisting end user reports

/hanges to the Target Database

/he im$lications of modifying the underlying


260/275

2-& op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Minimal Im$act:

)dding new columns )dding new tables

;reater Im$act:

RenamingLmoving database hanging e-isting column

and table names Deleting tables and columns

/he im$lications of modifying the underlyingdatabase for usiness!b"ects universes varies in

severity:

Detecting /hanges to the Universe

efresh Structure


261/275

2-1 op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF


262/275

2-2 op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Minimal Im$act:

Rede!ining Object #$%' Renaming an Object' op&ing to di!!erent lass' ;oving in same lass or to a di!!erent lass' )dding new Objects

;reaterIm$act:

Deleting an e-istingObject

' Deleting and then recreating an object with e-actl& the same

de!inition

Universe:

/he wor*flow is:

A!!ing 6e7 Tables to an ExistingUniverse

A tables to the universe structure

* ) i i li i


263/275

2-( op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Delete e(isting conte(ts

Detect aliases

Detect conte(ts

"reate new ob)ects

Set up hierarchies

*nsert )oins an set carinalities


=ow to $rint information about a universe


264/275

2-) op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

=ow to $rint information about a universe

Understand the Universe Distribution rocess

=ow to e?$ort a universe to the >e$ository

=ow changes to the target database affect a universe

=ow changes to ob"ects will affect e?isting end user

re$orts

Universe Design XI


265/275

Universe Design XI

Module 1-: Lin*ing Universes


Know when it might be a$$ro$riate to consider lin*ing

one universe to another


266/275

2-- op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

one universe to another e able to lin* universes

e able to include universes

"in&ing Universes

4ithin a universe @A it is $ossible to dynamically lin* to another

universe @9A6


267/275

2-. op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Universe A

Universe B

Universe

A

/his has the effect of ma*ing it a$$ear as though the classes

ob"ects and structure of universe 9 are $art of universe 6=owever they are "ust a loo*u$ @signified by the fact they are

greyed outA to universe 9 and can not be edited in universe 6

Wh# "in& Universes 3 The


268/275

2-% op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

are effectively coding the same ob"ects several times over6 y

lin*ing you could avoid this6

ernel A

Derived B Derived !

Universe

A

Universe

A

.ol!s coreobjects

E!it objectsstructure in


269/275

2- op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Lin*ing only lin*s in classes ob"ects and structure from one

universe to another6 It does not lin* conte?ts6 /he conte?ts of

the derived universe will have to be altered to accommodate thelin*ed tables "oins6

/he lin*ed structure will have to be "oined to the native structure

of the derived universe to avoid


270/275

2.& op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF


271/275

2.1 op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

/he lin*ed universe structure and ob"ects cannot be edited in the

derived universe

/he lin*ed universe should be treated as though they were newtables inserted in the derived universe6 /he same $rocedure

should be a$$lied @i6e6insert new "oins and edit conte?tsA6

Wh# "in& Universes 3 Inclu!e */o'#, 9nother $ossible reason for lin*ing universes is that you wish to

co$y all the classes ob"ects and structure from one universe to

another6 ou could do this by first lin*ing from universe to 9

and then use the Include function to sever the lin* thus ma*ing


272/275

2.2 op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

and then use the Include function to sever the lin* thus ma*ing

the classes ob"ects and structure of universe 9 $art of universe

6 In effect this is a way of Buic*ly co$ying everything in one

universe to another

Universe B

Universe AUniverseA

"I6


273/275

2.( op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF


Designers must be aware of changes to the


274/275

2.) op&right *EEF Business Objects #) > )ll Rights Reserved Issue *3, )ugust *EEF

Designers must be aware of changes to theunderlying databases and the im$lications these have

for their universes

Lin*ing universes can ma*e maintenance easier

/here are several different a$$roaches to lin*inguniverses

ou can also include universes

% ti 4


275/275

%uestions 4

bo xi designer rc

Documents