Designer BO Training

7/31/2019 Designer BO Training

1/108

5/17/12 confidential 11

Business Objects

Designer XI


2/108


Objectives

Designer Interface

Simple Universe Creation

Loops & Contexts


3/108


Module ?

Graphical environment to create aUniverse

Semantic Layer

Create and Maintain universes.


4/108


Section A

Simple Universe and Object

Creation


5/108


What is a Universe ?

Semantic Layer

Information in the Universe file

Universe structure

Classes and Objects


6/108


What is a Universe ?

Sales

Finance

StockCorporateDatabase /

DW

Universe (Semantic Layer)

CreatestheUniverseforUsers

DesignerUser User


7/108


Universe Design process

CorporateDatabase /

DW

4. Implementation3. Design

2. User Requirements

5. Maintenance

1. Data Analysis


8/108


Section A.1

Core Universe Parameters


9/108


e ore ou ar

Detailed plan of the informationrequirements

A schema diagram of the relationaldatabase

Understanding of the database

Reporting requirement


10/108


Design

There are two ways to initiateUniverse Design:

Create a new Universe from scratch: File - New Commands:

OR


11/108


For a simple Universe.

Universe name and Database connection

Selecting Classes and Objects

Measure Objects

Generate the Universe

Steps involved in Universe Design


12/108


Integrity check detects :

Invalid syntax

Loops

Isolated tables

Isolated joins

Loops within contexts

Missing or incorrect cardinalities

Steps involved in Universe Design


13/108


e es gner n ow

List Mode

QuickDesignWizard

Universe

Parameters

StructureWindow

Objects andClassesWindow


14/108


Dialogue Box

A Universe has three coreparameters

Three CoreParameters


15/108


e onnec on o eDatabase

n the middle-ware throughwhich it is defined:

n the name and type of theconnection;

n the location of the database:

u A Universe connection composed of:

Secured

Shared

Personal


16/108


vance onnec v ySettings

Advanced Connectivity settings:

You can maximize

the query responsetime by equating tothe array fetch sizeof the SourceDatabase


17/108


rea n a n verse -Step 0

Enter the name, description, add theconnection.

Test theconnection


18/108



Opt the strategy to follow.


19/108



Controls.

Managesthe server,CPU,networkresources.

a ng a n erse


20/108


av ng a n verse

Methods to save a Universe file:


21/108


Section A.2

Adding Tables

e n verse ruc ure


22/108


e n verse ruc ureWindow

Map the Universe to the databasestructure

Universe StructureWindow

ng a es


23/108


ng a es

Click on +sign to viewfields in

Tables

Click and drag Tables in tothe Structure Window


24/108


Section A.3

Joins in UniverseStructures

a o o ns ac eve


25/108


a o o ns ac evein SQL?

SELECT Customer.Last_Name, Orders.Date,Orders.Amount

FROM Customer, Orders

Cartesian Product:

JoinWHERE Customer.Cust_ID=Orders.Cust_ID

Restricted Result Set:

n qu o n


26/108


n qu o n

n u er o n


27/108


n u er o n

WHERE

Customer.Cust_ID=Orders.Cust_ID

Equi Join

Restricted Result Set:

SELECT Customer.Last_Name, Orders.Date, Orders.Amount

FROM Customer, Orders

WHERE

Customer.Cust_ID*=Orders.Cust_ID(+)

Outer Join

Outer Join Result Set:

e a o n


28/108


e a o n

SELECT Age Group.Age_Group, Customer.Last_Name

FROM Age Group, Customer

Cartesian Product

WHERE Customer.Age Between Age_Group.Age_Min And

Age_Group.Age_Max Theta Join Result Set:

Theta Join


29/108


Section A.4

Creating Dimension and DetailObjects

mens on e a


30/108


mens on e aRelationship

Objects retrieve factual informationabout entities:

Detail Objects

e.g Address, Phone Number

Dimension Objects

e.g Name

Entity = Person


31/108


Window

One Class per Object

Group of Objects


32/108


Object


33/108


Properties

Object Qualification

List of Values


34/108


Object

Click and Drag the fieldin to the Classes and Objects

Window

Re-qualify it as a Detail Object

es ng ec s


35/108


es ng ec s

Important to test a Universe at eachstage

Production cycle of Universedevelopment

Modify Universe

Save UniverseTest Universe


36/108


Section A.5

MeasureObjects

Obj ?


37/108


Object?

Statistical information

How much was earned...

...by a Sales Person? ...by a Product?

1996

...in a Financial Year?

re a e unc ons an


38/108


re a e unc ons anGroup by

Rule of SQL:

Aggregate function accompanied byGroup By

SELECT

City.city,sum(Invoice_Line.days * Invoice_Line.nb_guests * Service.price)

FROMCity,Invoice_Line,Service,Customer,Sales

WHERE

( City.city_id=Customer.city_id )AND ( Customer.cust_id=Sales.cust_id )AND ( Invoice_Line.inv_id=Sales.inv_id )AND ( Invoice_Line.service_id=Service.service_id )

GROUP BYCity.city

Aggregatefunctions

Group By clause

contains anyunaggregatedfields usedin the Selectclause

eman c ynam sm


39/108


eman c ynam sm

Context of use

GROUP BYFormat(Sales.invoice_date,

'yyyy')

Question:What is the Total Revenue for each Year?

Inferred level of aggregation......changes with the GROUP BY.

Question:What is the Total Revenue for each Customer?

GROUP BYCustomer.last_name + ',

'+Customer.first_name

GROUP BYCustomer.last_name + ', '+Customer.first_name,Format(Sales.invoice_date, 'yyyy')

Question:What is the Total Yearly Revenue for each Customer?

Obj t


40/108


Object

Define them in a separate Classdue to their semantically dynamicnature.

NOTE: the Aggregate function in the Measuresdefinition will cause the appropriate GROUP BYclause to be generated by the inference engine.

e ro ec on unc on


41/108


e ro ec on unc onand LOV

The Projection Function controls thebehaviour of the Measure in theReporting interface:

DisassociateMeasures

with LOVs

Check the Qualification is set appropriately

Set the function

to control thebehavior ofthe Object inthe reportinginterface

Obj t


42/108


Objects

Measure Objects need a morerigorous testing procedure thanDimension Objects:

GROUP BYCity.city

GROUP BYCity.city,Customer.last_name + ', '+Customer.first_name

GROUP BY

Customer.last_name + ', '+Customer.first_name

mens ons mus e


43/108


mens ons mus eUnique!!!

Dimension Objects must be definedin a way that will guarantee theuniqueness of the data they return:

NOTE: The inclusion of the unique IDguarantees the results will be displayedaccurately in the reporting interface.


44/108


Section B

Designing UniverseStructures

to conform to SQLrequirements

and resolve Loops


45/108


Section B.1

What is a Loopand

how is it resolved inBusinessObjects?

a s a oop


46/108


a s a oop

A loop is caused by a circular set ofjoins which defines a closed path

through a set of Tables:

SELECT , FROM All Tables in LoopWHERE All Joins in Loop...

ow o ea w oops


47/108


ow o ea w oops

Three Automated routines can beused to resolve 99% of loopsituations within the Universe

structure window.The following order must be observed:

MUST BE FIRST!!!

Cardinality Detection

Routine:

Any subsequent order.

Alias DetectionRoutine

Context DetectionRoutine

...and...


48/108


Section B.2

Using Aliases to Resolve aLoop?

a s an as


49/108


a s an as

An Alias is a temporary name assignedto a Table, within an SQL Statement.

It can be used to resolve structural issuesin a database:

WHERE

AND

Resort.Country_ID =Country.Country_ID

AND

Customer.Country_ID =Country.Country_ID

AND

...

WHERE

AND

WHERE

ANDResort.Country_ID=Resort_Country.Country_ID

ANDCustomer.Country_ID=Customer_Country.Country_ID

AND...

s n u oma c as


50/108


s n u oma c asDetection

The process of Alias detection isautomated by BusinessObjects:ORmanuallyinsert joins

ORinsertcardinalities

1

1

1

11

1

1

1

1

TABLETREE

Aliasneeded

here

11

TheSolution

e n n ec s rom


51/108


e n n ec s romAliases

It is essential, when Aliases are usedin the Universe Structure Window,that Objects are defined from the

approriate Alias:Pointers

to:


52/108


Section B.3

Other uses of Aliasesthat require manual

Resolution

ecurs ve a e ruc ures:


53/108


ecurs ve a e ruc ures:Pigs Ears

A recursive Table structure occurswhen a Table acts as a lookup foritself:

n Automatically:n Manually:

u e oma n oo u s: e


54/108


u e oma n oo u s: eProblem

MDLs are a major problem for

Designers:

Sample Data:

Absences

MultipleDomainLookup

SampleResult

SetIncorrectSolution

u oma n oo u s: e


55/108


u oma n oo u s: eResolution

There is a manual solution for MDLs:

u an u er o ns: ases


56/108


u an u er o ns: asesallow both

It is possible to give the User thechoice of using an Equi Join or anOuter join in their queries.


57/108


Section B.4

Using Contexts to ResolveLoops

a a ase ruc ure: on ex


58/108


a a ase ruc ure: on exSituations

Certain database structures willrequire the definition of contexts inUniverse structures:

FACT(sales)

Customer

Time

Product

Vendor

1

1

1

1

SingleStar

Schema

FACT

Dimension orLookup Table

1

1 1

1

Country

Brand

1

1

NormalisedDimensions

SnowflakeSchema

FACT(reservations)

1

1

Multiple StarSchemas

WARNING:Loop!!!

on ex s ua ons:


59/108


on ex s ua ons:Errors in SQL

A loop caused by multiple fact tableswill result in incorrect results beingreturned from the generated SQL

FROMAll Tables in LoopWHERE.All Joins in Loop

ow us ness ec s


60/108


ow us ness ec sdetects Contexts

Contexts are automatically detectedthrough the table tree algorithm:

OR insertcardinality

DetectContexts

1

1

1

1

1

1

Accept suggestions

SalesContext

ReservationsContext

Sales Fact: Reservation Fact:

e ncom a e uery: u


61/108


e ncom a e uery: uPath SQL

Contexts are important whenhandling what may be termedIncompatible Queries:

WHERE andFROM clausedefined from:

Invoice_Line

Context

TwoSelectsJoinedon the

Client

Reservation_Line

Context

m uous uer es:


62/108


m uous uer es:Naming Contexts

It is important to name Contextsappropriately to limit the impact ofthe Ambiguous Query:

A Name andDescription

help them to makethe right decisionfortheir question

Users create Ambiguous Queriesand are asked in whichContext are they asking the question

ases n a u ar


63/108


ases n a u arsituation?

Normalised dimensions are notamenable to loop resolutions throughAliases:

Candidates

forAliases

Still a LoopAll Candidates

for Aliases

Duplicationof Objects: Duplicationof Objects:

SalesUniverse

ReservationsUniverse

Effective Result: Two Universes


64/108


Section B.5

Other Uses ofContexts:

Chasm Traps

e asm rap


65/108


e asm rap

The Chasm trap appears in the followingsituation:

SELECT Sales_Person.sales_personCount(Abscences.ABSSTART),

Sum(Salaries.SALARY_VALUE)FROM WHERE GROUP BY Sales_Person.sales_person

1. SELECT

Sales_Person.sales_person,Abscences.ABSSTART,

Salaries.SALARY_VALU

E

Sales Person Start Date Salary Value

2.GROUP BY

Sales_Person.sales_person3. Applies Aggregatefunctions

Count() Sum()

4. Generates incorrectresults

Sales Person No. Abscences Total Salary

e us ness ec s


66/108


e us ness ec sResolution

BusinessObjects resolves the Chasm

Trap through Contexts and MultipathSQL


67/108


Section B.6

The FanTrap:

e an rap


68/108


e a ap

The fan trap occurs in the followingsituation:

SELECT Customer.last_nameCount(Sales.Inv_id),Sum(Invoice_Lines.

days)FROM WHERE GROUP BY Customer.last_name


69/108


Section C

Hierarchies in Universe

Design


70/108


Section C.1

What is aHierarchy?

a s a erarc y


71/108


y

U.K.

North South

Liverpool Manchester Newcastle London Southampton Bristol

Level in Hierarchy: Entities Returned:

Hierarchy


72/108


Hierarchy

NOTE: As each level is divided in to its components at the level belowa more atomized view of any statistical information can be found.

More DetailedLess Detailed

ow o e resen aHi h


73/108


Hierarchy

Dimension Objects represent theentity levels in a hierarchy:

Measures can be analysed at each entity

level Top Level

Level 1

Level 2

Level 3

Multidimensional Analysis


74/108


Multidimensional Analysis

Drill is the central mechanismthrough which multidimensionalanalysis can be conducted:

Drill Down


75/108


Section C.2

A Simple DefaultHierarchy?

Hierarchy?


76/108


Hierarchy?

A Default Hierarchy is visuallyrepresented to the User in theClasses and Objects Window:

Default Hierarchies arerepresented by the wayObjects are laid out inthe Classes and ObjectsWindow of the QueryPanel

ow o rea e a e auHi h


77/108


Hierarchy

Dragging and Dropping fields fromthe Structure Window and existingobjects from the Classes and Objects

Window are the simplest ways tobuild a default hierarchy:

Hierarchy


78/108


Hierarchy

Create a Scoped Query to test out aDefault hierarchys operation:

from the base Dimension Object


79/108


Section C.3

A Special Case:Time

Case?


80/108


Case?

Time is a special case because eachof its levels can come from a singlefield in the underlying database:

01/01/1997

Invoice Date:

Year

Quarter

Month

Day

and dependant ondefinition...

our ays o rea e meHierarchies


81/108


yHierarchies

There are four ways to develop aTime hierarchy in BusinessObjects:n Automatically: n Using standard functions:

n Altering the database: n Defining a Custom function:

Hierarchies


82/108


Hierarchies

Automatic Time hierarchies are finefor testing and quick design work:

In the Classesand Objectswindow...

es ner e ne meHierarchies


83/108


Hierarchies

Using functions to manipulate thedata returned by a Date Objectimproves presentation in Reports:

Copy theObject tosave time

Edit the duplicate Objects definition

Periods


84/108


e ods

Altering the database table structure

gives the Designer the flexibility toprovide their own definition of periods:

Calendar Year: 1/1/94 - 31/12/94Financial Year: 6/4/94 - 5/4/95

Calendar Quarter 1: 1/1/94 -31/3/94

Financial Quarter 1: 6/4/94 -5/7/94

Calendar Year: Financial Year:


85/108


Section C.4

Designer Defined CustomHierarchies

and Hierarchy Maintenance

Hierarchy?


86/108


y

A Custom Hierarchy combineselements from default (or pure)hierarchies in to a single path of

analysis:

Default Hierarchy: Custom Hierarchy:

Hierarchy


87/108


y

Custom Hierarchies can be defined inthe Hierarchies Editor:

us om or e auHierarchies?


88/108


Hierarchies?

There are three options whendefining a hierarchy strategy:

Only Default

Only Custom

Both

n ngo ng rocess


89/108


The hierarchies made available in aUniverse must change to meet userrequirements:Ive

designedthis new

hierarchyfor you...

But I needthis hierarchy

you fool!!!

Designer Updates Universe User requests new hierarchy

mens ona s an nHierarchies


90/108


Hierarchies

If a Analysts persistently meetDimensional Rifts it is a clearindication that a Custom hierarchy is

needed:

} DimensionalRift

No linking metadata in Universe

Link Hierarchy:


91/108


Section D

Distributing and MaintainingUniverses


92/108


Section D.1

Documenting aUniverse

Universe


93/108


Documenting a Universe will savetime in the future and make it easierto envisage it in its entirety:

?

Documentation


94/108


Printing out documentation for aUniverse is a simple process:n What? n How?


95/108


Section D.2

Deploying aUniverse

Universe


96/108


The Universe development cycle hasseveral distinct phases:

Phase 1-2

Phase 3

Phase 4

Phase 5

Phase 6

Phase 7

s r u ng n verses


97/108


There are two major mechanisms fordistributing Universe files:

File System

Central Management Server (CMS)

repository

or group o e


98/108


The File System allows unsecuredUniverses to be distributed:

n erpr se o e


99/108


The BusinessObjects CentralManagement Server (CMS) repositoryallows the Universe to be distributed

and secured:

CentralManagementServer (CMS)

repository

Central Management Server


100/108


(CMS) repository Universe is made available to Web

Intelligence users and otherdesigners by exporting a universe to

the CMS repository. When a universe is exported, the

universe is:

Moved to the selected universe folder onthe repository file system and

Created in the Central Management

System (CMS).


101/108


Section D.3

Maintaining aUniverse

o y n e n er y nDatabase


102/108


Database

The implications of modifying theunderlying database forBusinessObjects Universes varies in

severity:

n No Impact:

Adding new Fields Adding new Tables

n Severe Impact:

Renaming/Moving Database Changing existing Field names Changing existing Table names Deleting Tables

ew a es n an x s nUniverse


103/108


Universe Certain Procedures must be followed

when new Tables are added to anexisting Universe structure:

Add new Tables

Check if it is a Multi Domain Lookup(Aliases)

Insert Joins and Cardinalities

Objects


104/108


Changes to existing Objects in aUniverse have two types of impacton existing Documents created from

the Universe:

n No Impact:

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

a different Class

Adding new Objects

n Impact:

Deleting and existing Object Deleting and recreating the

Object with exactly the sameDefinition

ng ew ec s


105/108


There are three main ways to addnew Objects to an existing Universe:1. Create from scratch: 2. Copy from another Universe:

3. Include User Defined Objects:

o u e ummary


106/108


Universe Design is cyclical:

Phase 1-2

Phase 3

Phase 4

Phase 5

Phase 6

Phase 7

unc ons ava a e


107/108


DESIGNER provides a number of

functions for the SQL definition ofobjects. By using these functions, youmake the definition of objects dynamic

as well as database-independent.Referred to as @ functions, thesefunctions are as follows:

@Aggregate_Aware @Prompt : allows creation of an interactive object.

@Select : reusability of a Select statement of an existingobject

Thank you for your time


108/108

Our promise

With utmost respect to Human Values, wepromise to serve our customers with

Integrity, through Innovative, Value for

Money solutions, by Applying Thought, day

after day

Date post:	05-Apr-2018
Category:	Documents
Upload:	pavan-mysore
View:	220 times
Download:	0 times