xi3 universe builder guide en

BusinessObjects Universe BuilderGuide

BusinessObjects Universe Builder Guide

© 2008 Business Objects. All rights reserved. Business Objects owns the followingU.S. patents, which may cover products that are offered and licensed by Business

Copyright

Objects: 5,555,403; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objectslogo, BusinessObjects, Business Objects Crystal Vision, Business Process OnDemand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight,the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Letthere be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, WebIntelligence, Workmail and Xcelsius are trademarks or registered trademarks inthe United States and/or other countries of Business Objects and/or affiliatedcompanies. All other namesmentioned herein may be trademarks of their respectiveowners.

Business Objects products in this release may contain redistributions of softwarelicensed from third-party contributors. Some of these individual components may

Third-partyContributors

also be available under alternative licenses. A partial listing of third-partycontributors that have requested or permitted acknowledgments, as well as requirednotices, can be found at: http://www.businessobjects.com/thirdparty

2008-03-05

ContentsIntroduction 5Chapter 1

Overview of creating universes from metadata sources..............................6What is Universe Builder?...........................................................................6Universe Builder and Designer....................................................................6When do you use Universe Builder instead of Designer?...........................7

Universe Builder basics 9Chapter 2

Starting Universe Builder...........................................................................10

Building universes from XML metadata sources 11Chapter 3

Overview of how you create a universe from XML metadata....................12XML metadata to universe component mapping.......................................13Selecting a XML data source.....................................................................13Creating a universe from a XML data source............................................14

Universe and connection options for a universe built from a XMLsource...................................................................................................15

Viewing the trace log.................................................................................17Setting trace log options............................................................................17

Updating XML metadata source universes 19Chapter 4

Updating a universe from a XML metadata source...................................20

Exporting a universe to a XML file format 23Chapter 5

Overview of exporting universes to XML file formats................................24Universe pre-requirements for export to DB2 Cube Views........................24

BusinessObjects Universe Builder Guide 3

Exporting a universe to DB2 Cube Views formats.....................................25How to identify non-matching universe metadata......................................26Mapping specific SQL expressions...........................................................28How universe structures are mapped to DB2 Cube Views metadata........30

Universe to cube model........................................................................30Class to dimension...............................................................................31Fact table to Fact..................................................................................31Measure to measure............................................................................32Dimension and detail object to attribute...............................................33Dimension and detail relationship to attribute relationship...................33Default hierarchy to hierarchy..............................................................34Custom hierarchy to hierarchy.............................................................34Join to join............................................................................................34

Building universes from Oracle Analytic Services 37Chapter 6

Overview of how you create a universe from Oracle Analytic Services.....38How is a universe generated from a OLAP cube?....................................38Analyzing the relational view.....................................................................39What are the shortcut joins in the universe used for?...............................40How are Oracle OLAP structures mapped to universe components?.......42How to create a Oracle OLAP universe.....................................................48

Creating a view and generating a universe..........................................49Create a view only................................................................................51Creating Oracle OLAP universe from an existing view........................52

Get More Help 53Appendix A

Index 57

4 BusinessObjects Universe Builder Guide

Contents

Introduction

1

Overview of creating universes frommetadata sources

BusinessObjects XI Release 3 is installed with two products that you canuse to create universes frommetadata sources and Oracle Analytic Services:

DescriptionProduct

From Designer, you can create universes automatically frommetadata sources by selecting File > Metadata Exchange.A universe creation wizard allows you to connect to ametadata source, then generate a universe. This process isdescribed in the Designer Online Help and in the Designer’sGuide.

Designer

Stand alone product installed with BusinessObjects XI Re-lease 3 that allows you to connect to a metadata source,select objects to include in a universe, and then generatethe universe in Designer. This product is described in thisguide.

Universe Builder

What is Universe Builder?Universe Builder is Business Objects software that allows you to createuniverses from XML metadata sources and Oracle Analytic Services.

Once you start Universe Builder, you connect to a metadata source, thenusing a universe creation wizard, you mapmetadata structures to equivalentclasses, objects, dimensions, and details used in a standard BusinessObjectsuniverse. You then generate the universe.

Universe Builder and DesignerYou can create universes from metadata sources with both Universe Builderand Designer.


Introduction1 Overview of creating universes from metadata sources

Universe Builder is a stand alone product that provides an independent userinterface for universe creation from metadata sources.

Designer is used for the universe generation at the end of the creationprocess.

The universe creation mechanism for each supported metadata source is asoftware plugin to Designer. There is a metadata source plugin for eachsupported metadata source.

The metadata plugins can be updated by Business Objects. If the plugin fora metadata source is updated, then you can install the updated plugin anduse the new capabilities from Universe Builder, but the updated plugin is notavailable from Designer.

When do you use Universe Builderinstead of Designer?

Given that you can use either Designer or Universe Builder to create auniverse from metadata source, why use Universe Builder and when do youuse it?

Universe Builder is an independent product. You can update the metadataplugins used to generate universes when newer versions are available fromBusiness Objects.

Designer can not be updated with new or updated metadata exchangeplugins. The metadata source support is fixed at the level of the installedversion.

You use either Designer or Universe Builder based on the following:

• You use Designer to create a universe from ametadata source supportedat the time of this release.

• You use Universe Builder to create a universe from a metadata sourceplugin that has been updated, or to use a plugin for a newly supportedmetadata source.


1IntroductionWhen do you use Universe Builder instead of Designer?


Introduction1 When do you use Universe Builder instead of Designer?

Universe Builder basics

2

Starting Universe BuilderYou start Universe Builder from the task bar by clicking the Universe Buildericon in the group of installed Business Objects products for this release. Youare prompted to log into the CMS before Designer starts.

Once you start Universe Builder, the Universe Builder pane appears. All themetadata sources supported in this BusinessObjects release are listed asicons in the Bridges column to the left of the Universe Builder pane.

Each metadata source also appears as a tab in the central part of the pane.

You can activate a metadata source by clicking either its icon to the left, orclicking its tab.

1. Select Universe Builder from the BusinessObjects group of products inthe Start menu.The login box for the CMS appears.

2. Type the following information. This information is normally provided foryou by the BusinessObjects administrator.

DescriptionLogin information

Name of the CMS server.System

Your repository user name.User Name

Your repository password.Password

Your security levelAuthentication

3. Click the OK button.The Universe Builder pane appears.


Universe Builder basics2 Starting Universe Builder

Building universes fromXML metadata sources

3

Overview of how you create a universefrom XML metadata

You can create or update a universe from XML files conforming to thefollowing data source standards:

• Common Warehouse Model (CWM Relational 1.0• Common Warehouse Model OLAP (CWM OLAP)• Oracle Warehouse Builder (Oracle WB)• Data Integrator• IBM DB2 Data Warehouse Center (IBM DB2 DWC)• IBM DB2 Cube Views

You can also export a universe to a IBM DB2 Cube View XML format file.

You create a universe by following a metadata source wizard, that allowsyou to connect to a target XML file. You can then select the cube associatedwith the XML metadata source. You then start a creation wizard that allowsyou to select cube tables to include in the universe. You select a connection,set creation options and generate the universe.

The universe creation process is the same for all XML metadata sources.

The universe creation process for a Oracle Analytical Workspaces datasourceis different. Once you have selected your connection, a universe creationpanel specific to Oracle Analytic Workspaces appears. You create a viewon the database, then create a universe from the view. This is described inthe chapter Building universes from Oracle Analytic Services.

Once you have created the universe from ametadata source, you can modifyany of the universe components as for any other universe.

You save and export the universe to the Central Management System (CMS).Once exported to the CMS, the universe is then available to Web Intelligenceusers to create queries and reports.


Building universes from XML metadata sources3 Overview of how you create a universe from XML metadata

XML metadata to universe componentmapping

The following table shows the BusinessObjects structures that are mappedfrom information in the XML file:

Universe structureXML information

UniverseDatabase

Class, tableTable or view

Class nameTable business name

Object, columnColumn

Object nameColumn business name

Object typeColumn SQL data type

Class/object descriptionTable/column description

Join expressionForeign key-Primary key relation-ship (PKTable.PKColmn=FK-Table.FKColumn)

Selecting a XML data sourceYou select a metadata source (an XML file) to create or update a universefrom the Universe Builder panel.

1. Start Universe Builder.The Universe Builder panel appears.

2. Click the icon or tab for your metadata source.For example to create a universe from a CWM relational 1.0 metadatasource, you can click either the icon to the left of the Universe Builderpanel or the tab at the top of the Universe Builder panel.


3Building universes from XML metadata sourcesXML metadata to universe component mapping

3. Do one of the following:• Select File > Metadata Sources• Click the Metadata Sources button.The connection wizard starts.

4. Click Next.The XML file selection page appears.

5. Do one of the following:• Type a file path.• Click the Browse button and select a XML source file. This is the file

that you want to use to generate the universe.

6. Click Finish.The XML file and associated database name appear in the UniverseBuilder pane.

Example:

Creating a universe from a XML datasource

Once you have selected a metadata source, you use a universe creationwizard to take you through the steps to select the metadata elements thatyou want to be mapped to the universe, and finally the generation of theuniverse.

1. Start Universe Builder and select a metadata source.2. Click the source database icon under the XML metadata source name in

the Universe Builder panel.3. Do one of the following:

• Select File > Create Universe• Click the Create Universe button.The Universe Builder wizard starts.

4. Click Next.The universe elements page appears. The available database tables andcolumns are listed in the left pane.


Building universes from XML metadata sources3 Creating a universe from a XML data source

5. Select one or more tables and columns and click the right arrow topopulate the right pane. The tables and columns in the right pane arethose that appear in the generated universe. You can use the arrowbuttons to add and remove tables from the universe pane as necessary

6. Click Next.A connection and universe properties page appears. It lists theconnections available to Designer.

7. Click a connection in the connections list. This is the connection to thedata source that the universe uses to retrieve data. Do the following onthe connection and universe properties page:• Type a universe name.• Select or clear options check boxes.• Click the Advanced button to set trace log file and XML source file

options.• Click Next.The universe generation summary page appears. It lists a summary ofthe options that you have selected during the wizard.

8. Click Finish.The generated universe appears in the universe and structure panes ofDesigner.

Related Topics• Selecting a XML data source on page 13• Universe and connection options for a universe built from a XML sourceon page 15

Universe and connection options for a universe builtfrom a XML source

You have the following options on the connection and universe build pageof the metadata universe builder wizard:


3Building universes from XML metadata sourcesCreating a universe from a XML data source

DescriptionUniverse optionsWizardpage

Listed connections are connections availableto Designer. This is the connection to the tar-get RDBMS.

Select a connec-tion

Build uni-verse set-tings

The name of the universe that will be generat-ed.Universe name

When selected, the universe is saved on cre-ation.

Save universe au-tomatically

When selected, if a universe with the samename exists, and Save universe automaticallyis selected, the new universe replaces theexisting universe.

Replace existinguniverse

Path to the trace folder. This is the folder thatholds the log files when universes are gener-ated. You can browse to and select a folder.

General tab:Traces

Advancedsettings

Path to the default folder that stores the XMLfiles used to create universes. You canbrowse to and select a folder.

File locations tab:Default XMLSource File Folder

Path to the default folder that stores the pa-rameter files. These are files created when auniverse is created. These files store and ref-erence the selected metadata so that it canbe reused for creating or updating other uni-verses. The parameter file does not store theselected metadata. it is a filter that directs thebridge to the selected metadata through theoriginal XML file. You can browse to and se-lect a folder

File locations tab:Parameter File


Building universes from XML metadata sources3 Creating a universe from a XML data source

Viewing the trace log

•

Example:

Setting trace log optionsThe Universe Builder creates a log file that contains trace information forview and universe creation. The log file is generated in the default folder<INSTALL DIR>\Log Files. You can change the default target folder. Youcan set the following trace options:

DescriptionOptionTab

Path to the trace folder. This is thefolder that holds the log files whenuniverses are generated. You canbrowse to and select a folder.

TracesGeneral

Path to the default folder that storesthe XML files used to create univers-es. You can browse to and select afolder.

Default XML SourceFile FolderFile locations


3Building universes from XML metadata sourcesViewing the trace log

DescriptionOptionTab

Path to the default folder that storesthe parameter files. These are filescreated when a universe is created.These files store and reference theselected metadata so that it can bereused for creating or updating otheruniverses. The parameter file doesnot store the selected metadata. it isa filter that directs the bridge to theselected metadata through the origi-nal XML file.

Parameter File

1. Select View > Options or click the Options button.The Options page appears.

2. Set options as required.3. Click OK.


Building universes from XML metadata sources3 Setting trace log options

Updating XML metadatasource universes

4

Updating a universe from a XMLmetadata source

You select a metadata source that has been updated. This is the metadatasource that has been used to create a universe. The source has beenupdated, and now you want to update the universe with the samemodification. A universe update wizard takes you through the steps neededto update the universe.

1. Start Universe Builder and select a metadata source. See the sectionSelecting a XML metadata source for information on doing this.

2. Click the source database icon under the XML metadata source name inthe Universe Builder panel

3. Do one of the following:• Select File > Update Universe.• Click the Update Universe button.The Universe update wizard starts.

4. Click Next.The universe file page appears.

5. Click the Browse button and select a universe. This is the universe thatyou want to update from the selected XML metadata source. Click Next.The universe elements page appears. The available database tables andcolumns are listed in the left pane. Tables that have been added ormodified are indicated with a red check mark

6. Select one or more tables and columns and click the right arrow topopulate the right pane with the tables that have been modified. Thetables and columns in the right pane are those that appear in thegenerated universe. You can use the arrow buttons to add and removetables from the universe pane as necessary.

7. Click Next.The elements to update page appears.

8. Click the Advanced button.The Options box appears.

9. Click the Properties tab and select radio buttons to keep or replaceBusiness Name, Mapping Expression, Object Type, and Lineageproperties.


Updating XML metadata source universes4 Updating a universe from a XML metadata source

10. Click the Description tab and select radio buttons to keep, concatenate,or replace Business and Technical descriptions.

11. Click the File Location and General tabs to change parameter file paths,then click Next.The universe generation summary page appears. It lists a summary ofthe options that you have selected during the wizard.

12. Click Finish.The updated universe appears in the universe and structure panes ofDesigner.


4Updating XML metadata source universesUpdating a universe from a XML metadata source


Updating XML metadata source universes4 Updating a universe from a XML metadata source

Exporting a universe to aXML file format

5

Overview of exporting universes to XMLfile formats

You can export a universe to IBM DB2 cube View XML format file.

The universe definition is exported to a XML file that complies with IBM DB2Cube Views XML format. This file can then be loaded in IBM DB2 CubeViews using the API or OLAP Center tool. IBM DB2 Cube Views reads themetadata from the XML file, and recommends the appropriate AutomaticSummary Table (AST) for future query optimization.

Universe pre-requirements for export toDB2 Cube Views

The following list describes the universe pre-requisites necessary for asuccessful universe export to the XML file:

RestrictionsUniverse ele-ment affected

• Each universe is exported to a Cube Model.• A universe must match a single snowflake schema with

a single fact table.• The universe must contain at least one measure.• Links between universes are not supported.• Contexts are not taken into account, and not exported.• Custom hierarchies: the levels of a custom hierarchy

must be grouped in the same class.

Universe level re-strictions


Exporting a universe to a XML file format5 Overview of exporting universes to XML file formats

RestrictionsUniverse ele-ment affected

• @Select function is the only supported @function. Allother @functions are not mapped in the export.

• Conditions in the Where field of an object definition arenot exported. Note: Conditions are not supported in DB2Cube Views objects, as they are not used for optimiza-tion.

• Multi-parameter aggregation functions are not exported.• Each class must contain objects that are built on the

same dimension tables.• All the objects (attributes in IBMDB2CV) that are refer-

enced by the same dimension in IBMDB2CV, must begrouped in the same class in the universe. Any othermeasure in other classes are automatically added to theFact object in IBMDB2CV.

Classes and ob-jects

If the left or right column of a join does not match an objectin the universe, then an attribute for this column is automat-ically created and added to the dimension (or fact) thatcontains the column table.

Joins

Exporting a universe to DB2 CubeViewsformats

You export a BusinessObjects universe to a IBM DB2 Cube Views XML fileas follows:

1. Start Universe Builder and click the IBMDB2CubeViews icon or tab.2. Do one of the following:

• Select File > Export Universe.• Click The Export Universe button.The export wizard starts.

3. Click Next.A universe source file page appears.

4. Browse to and select a universe file, then click Next.


5Exporting a universe to a XML file formatExporting a universe to DB2 Cube Views formats

An OLAP information page appears.

5. Do the following:• Enter a name for the fact table, or you can accept the fact table name

by default.• Enter a name for the schema.• Click Next.The metadata is loaded. A page appears showing the structures that willbe exported.

6. Click Next.7. Type a name for the XML file and click Next.

A summary page appears.

8. Verify that the export information is correct, then click Finish.The XML file is created in the universes folder of your user profile, forexample, C:\Documents and Settings\<username>\ApplicationData\Business Objects\Business Objects <version>\Universes.

How to identify non-matching universemetadata

This section describes how objects in a universe that do not have amulti-dimensional match in IBMDB2Cube Views are identified and processedduring the export of a universe definition to an XML file.

A universe is based on relational metadata that does not havemulti-dimensional design constraints. All the objects in a universe do notnecessarily match equivalent IBM DB2 Cube Views objects, and do notrespect IBM DB2 Cube Views multi-dimensional rules.

To correctly match relational structures, Universe Builder must run certainautomatic detection processes to identify and define the required andappropriate metadata for IBM DB2 Cube Views. The affectedmulti-dimensional objects are described below.


Exporting a universe to a XML file format5 How to identify non-matching universe metadata

DescriptionNon-matchinguniversemetada-ta

The IBM DB2 Cube Views Fact object is automatically builtfrom the set of measures found in the universe.Fact

Tables that are not identified as Facts are assumed to bedimension tables. A IBM DB2 Cube Views dimensionobject is deduced directly from a BusinessObjects class.

All the objects within a class determine the attributes ofthe IBM DB2 Cube Views dimension. The tables inferredby BusinessObjects objects within the class, are detectedby parsing the object’s Select field.

Dimensions

Attributes are not directly deduced from the columns of tablesin the universe. Candidate attributes are detected and iden-tified from the following information:• BusinessObjects objects within a class.• BusinessObjects objects referenced in Select field of

other BusinessObjects objects by the@Select statement.• Columns involved in a join.

Attributes

The detail-dimension relationship in a universe is translatedto an attribute relationship of type Functional Dependencyin IBM DB2 Cube Views.

Attribute relation-ships

Joins and their properties are directly read from universestructure.Joins

All classes are searched for measure objects. If a measureis not built on the same fact table, then it is ignored.Measures


5Exporting a universe to a XML file formatHow to identify non-matching universe metadata

DescriptionNon-matchinguniversemetada-ta

A hierarchy in DB2 Cube Views is linked to a dimensionobject and all its levels are members of this same dimension.This is not the case in a universe, where a custom hierarchycan contain levels coming from different Business Objectsclasses. Hierarchies are treated as follows:• If a universe uses only default hierarchies, then the hier-

archies for export to IBM DB2 Cube Views are deducedfrom the objects, using the object order within each class.

• If the universe has custom hierarchies, then they areexported without any modification.

Hierarchies

Mapping specific SQL expressionsCertain SQL expressions are mapped in particular ways by the exportprocess. The following cases of SQL expressions are described in detail:

• SELECT expression for a measure on page 28

• @AggregateAware function on page 29

• Complex join expressions on page 29

• Theta joins on page 29

• Shortcut joins on page 29

SELECT expression for a measure

The BusinessObjects UMB gets the following information from the SELECTof a measure:

• Detect tables and columns involved in a measure and map them tosqlExpression:column

• Identify the aggregation function

• Determine the formula expression and map it to sqlExpression:template.


Exporting a universe to a XML file format5 Mapping specific SQL expressions

@AggregateAware function

When an object contains the @AggregateAware function, only the lastparameter of the @AggregateAware function is taken into account. This isthe expression that contains the lowest level of aggregation used by thefunction. For example:

A @AggregateAware expression for a measure expression in the universeis as follows:@Aggregate_Aware(sum(AggregatedTable1.Sales_revenue),sum(AggregatedTable2.Sales_revenue),sum(Fact_Table.Amount_sold))

The expression that is mapped to IBM DB2 Cube Views is:sum(Fact_Table.Amount_sold))

Complex join expressions

The expression of a complex join in a universe can consist of expressionsof type:LeftTable.Column=RightTable.Column

In a complex join, these type of expressions can be linked together with theAND operator. The BusinessObjects UMB maps each expression in thecomplex join to an attribute pair of IBM DB2 Cube Views within the samejoin.

Theta joins

A theta join is split into two IBM DB2 Cube Views joins, where the operatorBETWEEN is replaced by operators <= and >=. For example:

A join in a universe has this expression:Customer.age between Age_group.age_min and Age_group.age_max

This join will be split into two joins with the following expressions:Join1: Customer.age >= Age_group.age_minJoin2: Customer.age <= Age_group.age_max

Shortcut joins

Not exported to IBM DB2 Cube Views. Shortcut joins in a universe representan alternate path to improve performance of queries by not taking into account


5Exporting a universe to a XML file formatMapping specific SQL expressions

intermediate tables. As shortcut joins create loops within a cube model, theyare not exported.

How universe structures are mapped toDB2 Cube Views metadata

The following universe structures are mapped to corresponding IBM DB2Cube Views structures. Each section provides detailed descriptions forstructures that are mapped from a universe to IBM DB2 Cube Views whena universe is exported to a XML file.

• Universe to cube model on page 30• Class to dimension on page 31• Fact table to Fact on page 31• Measure to measure on page 32• Dimension and detail object to attribute on page 33• Dimension and detail relationship to attribute relationship on page 33• Default hierarchy to hierarchy on page 34• Custom hierarchy to hierarchy on page 34• Join to join on page 34

Universe to cube model

The following describes mapping for a universe to cube model:

Cube propertyUniverse property

Cube file nameShort name (file name)

Business name. By default the name is the uni-verse short name (<universe short name>)Universe name (long name)

CommentsDescription

name factsRefFact table

dimensionRefList of classes


Exporting a universe to a XML file format5 How universe structures are mapped to DB2 Cube Views metadata

Cube propertyUniverse property

joinRefList of joins involving thefact table.

Class to dimension

The following table describes the mapping for a class to a dimension:

Dimension propertyClass property

Name and Business nameName

CommentsDescription

attributeRefList of dimension and detail objects.

joinRefJoins between dimension tables in-ferred by the class.

If hierarchy is a custom hierarchy, thenthe dimension is modified to get all hi-erarchy levels in the same dimensionas required by IBM DB2 Cube Views.The hierarchies are put in the herar-chyRef property.

Hierarchy

Related Topics• Measure to measure on page 32

Fact table to Fact

The following table describes the mapping for a fact table to a Fact.


5Exporting a universe to a XML file formatHow universe structures are mapped to DB2 Cube Views metadata

Fact propertyFact table property

Name and Business name

Fact table name

You enter this name manually in theFacts box in the Export universepanel. You can also accept the de-fault name Facts_<universe name>.

CommentsTable description

measureRefList of all measures in the universe

attributeRefList of columns and objects referencedin measures

Measure to measure

The following table describes the mapping of measure to a measure:

Measure propertiesMeasure properties


CommentsDescription

sqlExpression columnColumns and objects inferred by Selectstatements.

sqlExpression templateSelect statement formula

aggregation functionAggregation function



Dimension and detail object to attribute

The following table describes the mapping of dimension and details toattributes:

AttributesDimension and detail objects


CommentsDescription

sqlExpression columnColumns and objects referenced inSelect statements

sqlExpression templateSelect statement formula

Dimension and detail relationship to attributerelationship

The following table describes the mapping of Dimension/detail relationshipsto attribute relationships:

Attribute relationshipDimension/detail relationship

Name and Business nameDimension name + detail name. Concatcharacter is “_”

Left attributeDimension

Right attributeDetail



Default hierarchy to hierarchy

The following table describes the mapping of default hierarchies tohierarchies:

HierarchyDefault hierarchy

Names and Business nameName

AttributeRefList of objects. Detail objects must notbe part of the hierarchy.

Custom hierarchy to hierarchy

The following table describes the mapping of a custom hierarchy to hierarchy:

HierarchyCustom hierarchy


attributeRefList of objects

Join to join

The following table describes the mapping of joins to joins:



JoinJoin

Name and Business nameLeft table name + right table name.

Concat character is "_"

Left attributeLeft column

Right attributeRight column

Each simple expression maps to anattribute pair.

Complex expression:

For each simple expression the leftand right columns are identified.



Building universes fromOracle Analytic Services

6

Overview of how you create a universefrom Oracle Analytic Services

You create a Oracle OLAP universe by clicking the Oracle OLAP icon or taband selecting File > Metadata sources. The Oracle OLAP Universe Builderwizard starts. You select a connection. The cubes available to the connectionappear. You select a cube, and set view and universe creation options.

Related Topics• How is a universe generated from a OLAP cube? on page 38• How to create a Oracle OLAP universe on page 48

How is auniverse generated fromaOLAPcube?

When you create a universe with the Oracle OLAP Universe Builder, it isautomatically set up for SQL access to Oracle Analytic Workspaces.BusinessObjects Oracle OLAP Universe Builder performs the following maintasks:

• Inserts the relational fact view in the universe as a real view or as DerivedTable.

• Add aliases to represent the dimension levels and hierarchies

• Joins the relational view to the dimension tables with regular joins andshortcut joins. The expressions of the joins are specific to this solution.

• Creates a class of objects for each Cube dimension and an object foreach level of the dimension.

• Creates a subclass for each hierarchy if a dimension has more than onehierarchy. Multi-hierarchy dimensions are supported in the view definitionand in the universe.

• Define aggregate navigation to resolve object incompatibility that resultsfrom the multi-hierarchy dimensions.

• Defines object expressions using the AggregateAware function to handlethe Aggregation Navigation


Building universes from Oracle Analytic Services6 Overview of how you create a universe from Oracle Analytic Services

• Transforms objects that map real dimension members (Identifiers) toDetails of objects that represent the member descriptions.

• Creates measure objects

Analyzing the relational viewBusinessObjects Oracle OLAP Universe Builder generates views that callthe OLAP_TABLE function to map the view columns to the hierarchies ofthe dimensions and measures of the Cube. The generated script has thefollowing form:CREATE VIEW BOBJ_FK_UNITS_CUBE_VIEW AS SELECT * FROM TABLE(OLAP_TABLE('GLOBAL_AW2.TEST DURATION session','','','&LIMIT_MAP'

LIMIT_MAP is a variable that stores the text of the limit_map parameter ofOLAP_TABLE. This text is generated by Oracle OLAP Universe Builder.Here is an example of limit_map parameter:DIMENSION GLOBAL_AW2.TEST!FK_TIME WITHHIERARCHY GLOBAL_AW2.TEST!FK_TIME_PARENTREL (FK_TIME_HIERLIST\''CALENDAR\'')LEVELREL FK_TIME_YEAR,FK_TIME_QUARTER,FK_TIME_MONTHFROM GLOBAL_AW2.TEST!FK_TIME_FAMILYREL USING GLOB

AL_AW2.TEST!FK_TIME_LEVELLISTLEVELREL FK_TIME_YEAR_DESC,FK_TIME_QUARTER_DE

SC,FK_TIME_MONTH_DESCFROM GLOBAL_AW2.TEST!FK_TIME_FAMILYREL USING GLOB

AL_AW2.TEST!FK_TIME_LEVELLISTLABEL GLOBAL_AW2.TEST!FK_TIME_LONG_DESCRIPTION

ATTRIBUTE FK_TIME_LEVEL FROM GLOBAL_AW2.TEST!FK_TIME_LEVELRELDIMENSION GLOBAL_AW2.TEST!FK_CUSTOMER WITHHIERARCHY GLOBAL_AW2.TEST!FK_CUSTOMER_PARENTREL (FK_CUSTOMER_HIERLIST \''MARKET_SEGMENT\'')INHIERARCHY GLOBAL_AW2.TEST!FK_CUSTOMER_INHIERLEVELREL null,null,null,FK_CUSTOMER_TOTAL_MARKET,FK_CUS

TOMER_MARKET_SEGMENT,FK_CUSTOMER_ACCOUNT,FK_CUSTOMER_SHIP_TOFROM GLOBAL_AW2.TEST!FK_CUSTOMER_FAMILYREL USING GLOB

AL_AW2.TEST!FK_CUSTOMER_LEVELLISTLEVELREL null,null,null,FK_CUSTOMER_TOTAL_MARKET_DESC,FK_CUS

TOMER_MARKET_SEGMENT_D01,FK_CUSTOMER_ACCOUNT_DESC,FK_CUSTOMER_SHIP_TO_DESCFROM GLOBAL_AW2.TEST!FK_CUSTOMER_FAMILYREL USING GLOB

AL_AW2.TEST!FK_CUSTOMER_LEVELLISTLABEL GLOBAL_AW2.TEST!FK_CUSTOMER_LONG_DESCRIPTION

HIERARCHY GLOBAL_AW2.TEST!FK_CUSTOMER_PARENTREL (FK_CUSTOMER_HIERLIST \''SHIPMENTS\'')INHIERARCHY GLOBAL_AW2.TEST!FK_CUSTOMER_INHIER


6Building universes from Oracle Analytic ServicesAnalyzing the relational view

LEVELREL null,null,null,FK_CUSTOMER_ALL_CUSTOMERS,FK_CUSTOMER_REGION,FK_CUSTOMER_WAREHOUSE,nullFROM GLOBAL_AW2.TEST!FK_CUSTOMER_FAMILYREL USING GLOB

AL_AW2.TEST!FK_CUSTOMER_LEVELLISTLEVELREL null,null,null,FK_CUSTOMER_ALL_CUSTOMERS_DESC,

FK_CUSTOMER_REGION_DESC,FK_CUSTOMER_WAREHOUSE_DESC,nullFROM GLOBAL_AW2.TEST!FK_CUSTOMER_FAMILYREL USING GLOB

AL_AW2.TEST!FK_CUSTOMER_LEVELLISTLABEL GLOBAL_AW2.TEST!FK_CUSTOMER_LONG_DESCRIPTIONATTRIBUTE FK_CUSTOMER_LEVEL FROM GLOBAL_AW2.TEST!FK_CUSTOMER_LEVELRELMEASURE FK_UNITS_CUBE_UNITS AS NUMBER FROM GLOBAL_AW2.TEST!FK_UNITS_CUBE_UNITSROW2CELL OLAP_CALC

What are the shortcut joins in theuniverse used for?

Shortcut joins ensure that BusinessObjects generates SQL for each objectcombination rather than for each object.

BusinessObjects uses shortcut joins when it can omit tables from a queryand take a 'shortcut' between two tables that are not directly linked in ahierarchy. For example, based on the following schema:


Building universes from Oracle Analytic Services6 What are the shortcut joins in the universe used for?

if a shortcut join is defined between the QUARTER and OLAPCUBE tables,BusinessObjects does not need to join through the MONTH table to retrieverevenue by quarter.

Each table in the time hierarchy (except the lowest-level table) must be joinedto OLAPCUBE.time_level by a shortcut join, as shown below:

The join expression must include the expression that will restrict the rowsreturned from OLAPCUBE; in the case of QUARTER, this isOLAPCUBE.time_level = 'QTR'. To ensure that Designer allows the join, theexpression must also reference the MONTH table, which should appearinside comments (because it plays no part in the actual join expression thatyou are interested in generating). The full join expression is therefore:/* QUARTER.DUMMY */ OLAPCUBE.time_level = 'QTR'

The full list of shortcut join expressions for the example time hierarchy is asfollows:

ExpressionJoined tables

/* MONTH.DUMMY */OLAPCUBE.time_level = 'MONTH'MONTH, OLAPCUBE


6Building universes from Oracle Analytic ServicesWhat are the shortcut joins in the universe used for?

ExpressionJoined tables

/* QUARTER.DUMMY */OLAPCUBE.time_level = 'QTR'QUARTER, OLAPCUBE

/* YEAR.DUMMY */OLAPCUBE.time_level = 'YEAR'YEAR, OLAPCUBE

/* TIME_ALL.DUMMY */OLAPCUBE.time_level = 'ALL'TIME_ALL, OLAPCUBE

HowareOracleOLAP structuresmappedto universe components?

To obtain and set up the expected universe, the Oracle OLAP UniverseBuilder adds and configures universe objects as follows:

View

Oracle OLAP Universe Builder inserts the relational view as a table in theuniverse as well as the oracle table sys.dual. If you choose to use a derivedtable, a derived table is inserted with the definition of the view (select partwith OLAP_TABLE function).

Hierarchy tables

For each hierarchy that is represented in the relational view, an alias ofsys.dual is created for each level of the hierarchy. The name of the alias isthe level name. For example: if we have a dimension TIME with 4 levels(ALL, YEAR,MONTH,QUARTER) then create 4 aliases ALL, YEAR,MONTH,QUARTER.


Building universes from Oracle Analytic Services6 How are Oracle OLAP structures mapped to universe components?

Multi-hierarchy tables

Note: Multi-Hierarchy is a special case. See the section Multi-Hierarchyspecial case: (Multi-Hierarchy dimensions support) on page 46 for moreinformation.

If a dimension has more than one hierarchy, then a different set of tables iscreated for each hierarchy even if some hierarchies share a same level. Thismeans that for shared levels, as many aliases are created as hierarchies.The naming of such aliases is a concatenation of the level name and thehierarchy name. For example:

Dimension time has two hierarchies: H1 (All_Time, Year, Month) and H2(All_Time, Quarter, Month)

All_Time and Month are shared by both hierarchies so we'll have two aliasesfor All_Time: All_Time _H1 and All_Time_H2

And two aliases for Month: Month _H1 and Month _H2

Dimension joins• Each table representing a level is joined to its direct lower level in the

same hierarchy. The join expression is:

/* Alias1.DUMMY=Alias2.DUMMY */ 1=1


6Building universes from Oracle Analytic ServicesHow are Oracle OLAP structures mapped to universe components?

where Alias1 represents a level and Alias2 represents its direct upperlevel in the hierarchy. Example:

/* Quarter.DUMMY=Year.DUMMY */ 1=1

• Each table is joined to the view using a shortcut join type except for thelowest level where the join is regular. The join expression defines a valueto filter the rows returned from the view and is of the type:

/* Alias.DUMMY */

VIEW.levelColumn = 'level_value'

Where Alias is the alias name, levelColumn is the column representingthe level within the view and level_value is the value of that column thatmatches the level name.

Examples: MYVIEW is the view that represents the OLAP cube, the columnthat contains the levels is time_level, the level values are: ALL, YEAR, QTR,MONTH

Joined tables expressionMONTH, MYVIEW /* MONTH.DUMMY */ MYVIEW.time_level = 'MONTH'QUARTER, MYVIEW /* QUARTER.DUMMY */ MYVIEW.time_level = 'QTR'

YEAR, MYVIEW /* YEAR.DUMMY */ MYVIEW.time_level = 'YEAR'TIME_ALL, MYVIEW /* TIME_ALL.DUMMY */ MYVIEW.time_level ='ALL'

Classes and Objects

The Bridge must create a class for each OLAP dimension and an object foreach level. Class and object properties are mapped as follows:

Mapped from OLAPitem...PropertyUniverse item

Dimension nameName

Class

See alsoMulti-Hierarchyspecial case: (Multi-Hier-archy dimensions sup-port) on page 46 below.




Levels and attributes.Objects

Current level nameidentified by the fieldname in the view.

NameDimension

View field, for exampleMYVIEW.YEAR.Select

Additional tables to en-sure the use of appropri-ate joins:• Table of current view

• View

• Highest level tablefor all dimensions

Tables

Dimension object creat-ed from the Descriptionfield that is related to theID field. For example, IDfield is YEAR, Descrip-tion field it YEAR_DE-SC. The object YEAR isa detail of objectYEAR_DESC.

Parent dimension

Note: All other proper-ties are the same as fordimension above.

Detail (optional)

Measure name in cube.NameMeasure




View field, for exampleMYVIEW.SALESSelect (no drill through)

Additional tables to en-sure the use of appropri-ate joins:• View

• Highest level tablefor all dimensions

Tables

None.Aggregation function

Multi-Hierarchy special case: (Multi-Hierarchy dimensions support)

To support Multi-hierarchy dimensions of an Analytical Warehouse, thefollowing actions are carried out in the universe:

• A set of tables is created for each hierarchy as described in the sectionMulti-hierarchy tables on page 43.

• A class is created for the dimension and a subclass for each hierarchy.The naming of subclasses is a concatenation of the dimension name andthe hierarchy name.

• For each object corresponding to a level within a hierarchy, the aggregatefunction is added to the Select expression. It references as comments,all the high level aliases, except the aliases of the current hierarchy. Forexample:



• Aggregate Navigation is set to make the objects of a subclass (Hierarchy)incompatible with the tables corresponding to another hierarchy. Thisprevents the end user from using in a report objects representing levelsthat belong to different hierarchies.

For example, the table Year_H1 (from Hierarchy H1) is incompatible withobjects from H2 hierarchy:

And the table Year_H2 (from Hierarchy H2) is incompatible with objects fromH1 hierarchy:



How to create a Oracle OLAP universeYou can create universes and views as using the following creation methods:

DescriptionUniverse creation option

You create a view, and then selectwhich structures are mapped to cre-ate the universe.

Creating a view and generating auniverse on page 49

You can create a view and save theview if you do not want to create auniverse. The view is available in aview list and can be used to create auniverse at any time.

Create a view only on page 51

You select an existing view, andgenerate a universe directly from thisview.

Creating Oracle OLAP universe froman existing view on page 52


Building universes from Oracle Analytic Services6 How to create a Oracle OLAP universe

Creating a view and generating a universe

You generate an Oracle OLAP universe by first defining a view using AnalyticWorkspace Cube metadata, then you set universe creation options, andgenerate a new universe.

1. Click the Oracle OLAP icon or tab.2. Select File > Metadata Sources.

The Oracle OLAP Connection Wizard Welcome page appears.

3. Click Next.The wizard login page appears.

4. Select a connection, enter user name and password, and then click Finish.The Universe Builder Panel appears displaying the Analytic WorkspaceCube cubes available to the connection

5. Click the Cubes node.The Analytic Workspaces (AW) available in the connection are displayed.

6. Expand a AW node to display the cubes available to the AW, then rightclick a cube and select Create Universe from the context menu.The Universe Builder wizard appears. Three options are available. Theseare described in the section How to create a Oracle OLAP universe onpage 48.

7. Click the Create View and generate Universe radio button, then clickNext.A status box appears showing themetadata loading status. A box showingdata type and data length information appears.

8. If required, modify the data type and length values. Do this as follows:• Double click a data type or length value.• Select a data type from the drop down list box.• Click Next.The Hierarchy level page appears. This page lists the hierarchy levelswith data types and values.

9. Edit hierarchy values if necessary, then click Next.The View and universe options page appears.


6Building universes from Oracle Analytic ServicesHow to create a Oracle OLAP universe

10. Type a name for the view, and select view and universe options. TheView properties and universe options are as follows:

DescriptionOptions

Name for the view. You can editthis field.View Name

When selected, an extra column oftype Raw(32) is created in the viewto enable the use of OLAP_EX-PRESSION function in the uni-verse.

CreateColumn forOLAP_EXPRES-SION

When selected, columns represent-ing the dimension members (identi-fiers) are created.

Create Columns for Identifiers

When selected existing Type andView structures are replaced in thedatabase.

Replace existing database objects

When selected the universe is notbuilt from a view physically createdin the database, but is built by usinga derived table to reference thecube structures. A derived table isa virtual table that exists only in theuniverse that references databasestructures. It is not created in thedatabase. This is useful when theuser does not have CREATE VIEWrights, or if you do not want to accu-mulate views in the database.

Use derived tables



DescriptionOptions

Only active when the Createcolumns for identifiers option forviews is selected. When selected,object IDs are transformed into de-tail objects in the generated uni-verse.

Transform object IDs to details

11. Click Next. The SQL verification page appears.12. Verify the SQL for the view and click Next. The universe information

summary page appears.13. Verify the universe information, and click Finish. Designer starts and

opens to the newly generated universe.

Create a view only

You can create a view using Analytic Workspace Cube metadata. The savedview appears in a list of views. Once you have create the view, you can thenselect the view at a later time and generate a universe. To create a viewonly, follow the same procedure in the sectionCreating a view and generatinga universe on page 49Creating a view and generating a universe on page49 but at the start of the Oracle OLAP Universe Builder wizard, you selectthe Create View only radio button.

The view is created in the target database. You can connect to this view atany time to create a universe. See the sectionCreating Oracle OLAP universefrom an existing view on page 52for the procedure on using a view to createa universe.


6Building universes from Oracle Analytic ServicesHow to create a Oracle OLAP universe

CreatingOracleOLAPuniverse fromanexisting view

You can generate a universe from an existing view. Existing views appearin a list. You select a view from the list and generate a universe.

1. Click the Oracle OLAP icon or tab.2. Select File > Metadata Sources.

The Oracle OLAP Connection Wizard Welcome page appears.

3. Click Next.The wizard login page appears.

4. Select a connection and enter user name and password.5. Click Finish.

The Universe Builder Panel appears displaying the Analytic WorkspaceCube cubes available to the connection.

6. Click the Cubes node.The Analytic Workspaces (AW) available in the connection are displayed.Expand a AW node to display the cubes available to the AW.

7. Right click a cube and select Create Universe from the context menu.The Universe Builder wizard appears. Three options are available. Howto create a Oracle OLAP universe on page 48 for a description of eachoption.

8. Click the Generate Universe from View radio button.9. Click Next.

A list of available views defined on the cube appears.

10. Click a view name in the list and click Next.A status box shows the progress of metadata being loaded from theselected cube. The Universe Creation page appears. It lists dimension,measures, and hierarchy levels defined in the view that can be used tocreate a universe.

11. If required, modify a column name or hierarchy level. Do this as follows:• Double click a column name or level value.• Select or type a name as appropriate.

12. Click Finish.Designer starts and opens to the newly generated universe.



Get More Help

A

Online documentation library

Business Objects offers a full documentation set covering all products andtheir deployment. The online documentation library has the most up-to-dateversion of the Business Objects product documentation. You can browsethe library contents, do full-text searches, read guides on line, and downloadPDF versions. The library is updated regularly with new content as it becomesavailable.

http://support.businessobjects.com/documentation/product_guides/

Additional developer resources

http://devlibrary.businessobjects.com

Online customer support

The Business Objects Customer Support web site contains information aboutCustomer Support programs and services. It also has links to a wide rangeof technical information including knowledgebase articles, downloads, andsupport forums.

http://www.businessobjects.com/support/

Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysisstage to the delivery of your deployment project. Expertise is available inrelational andmultidimensional databases, in connectivities, database designtools, customized embedding technology, and more.

For more information, contact your local sales office, or contact us at:

http://www.businessobjects.com/services/consulting/

Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we canoffer a training package to suit your learning needs and preferred learningstyle. Find more information on the Business Objects Education web site:

http://www.businessobjects.com/services/training


Get More HelpA

http://support.businessobjects.com/documentation/product_guides/

http://devlibrary.businessobjects.com


http://www.businessobjects.com/services/consulting/

http://www.businessobjects.com/services/training

Send us your feedback

Do you have a suggestion on how we can improve our documentation? Isthere something you particularly like or have found useful? Drop us a line,and we will do our best to ensure that your suggestion is included in the nextrelease of our documentation:

mailto:[email protected]

Note: If your issue concerns a Business Objects product and not thedocumentation, please contact our Customer Support experts. For informationabout Customer Support visit: http://www.businessobjects.com/support/.

Business Objects product information

For information about the full range of Business Objects products, visit:http://www.businessobjects.com.


AGet More Help

mailto:[email protected]


http://www.businessobjects.com


Get More HelpA

IndexCclasses and objects

in Oracle Analytic Workspaces universe 42

Ddimension joins

use in Oracle Analytic Workspaces universe42

Hhierarchy tables


Mmulti-hierarchy tables


OOracle Analytic Workspaces

class and object mapping 42dimension joins 42hierarchy tables 42multi-hierarchy tables 42use of shortcut joins in universe 40view 42

Sshortcut join


Vview




Index