# Module 8

Resolving Loops in a Universe

1

What You Will Be Able To Do 
Define what a Loop is  Detect and recognize loops in a universe  Use Designer tools to resolve loops using Aliases and Contexts 

Identify when in the design process you resolve loops  Be able to use Shortcut joins and know when to use them as an alternative for resolving loops 

Be able to resolve recursive table structure loops

2

What is a Loop? 
A loop is a set of joins that defines a closed path through a set of tables in a schema. Loops occur when joins form multiple paths between lookup tables. Why loops in a universe schema and not in the database? In a database, multiple paths between tables may be valid and implemented to meet specific user requirements. When each path is included individually in a query it returns a distinct set of results. However, the schema that you design in Designer often needs to allow queries that include more than one path, which a relational database may not be designed to handle, so the information returned can be incorrect. The rows that are returned are an intersection of the results for each path, so fewer rows are returned than expected. It is also often difficult to determine the problem when you examine the results. 

3

What is a loop?  A loop exists when the joins between tables form a continuous path 4 .

. The following order must be observed: Cardinality Detection Routine: Alias Detection Routine ...and.. Context Detection Routine MUST BE FIRST! 5 .How to deal with loops Three automated routines can be used to resolve most loop situations in the universe structure window.

Cardinality Detection  Cardinality not set: Click Detect Cardinalities:  Cardinality can also be set manually: 6 .

There is no impact on the schema of the database  Easy to define  Easy to maintain  Easy to use 7 .What is an Alias ?  An Alias is an exact duplicate of the original table with a new name.  The Alias is used only to resolve the loop in the structure of the universe. The data in the table is exactly the same.

When to Alias  A loop with a single lookup table should be resolved by an alias N N 1  A lookup table can be identified by its cardinality N 1 N 1 1 1 N  A lookup table only has the µone¶ end of joins attached to it Alias needed here 8 .

How to Alias  Designer routines detect loops and candidates for aliases  Break the loop by creating an alias of the lookup table for each side of the loop  Some DBs require a separate alias for both sides of the loop Do not remove the original table 9 .

Detecting and Creating Aliases  To create an alias table to break a loop. you can:  Use the Loop Detection routine  Use the Alias Detection routine  Manually insert an alias 10 .

Using automatic loop detection  Click the Detect Loops button  The routine checks the structure for loops  The Loop Detection window identifies each loop  The window suggests candidate contexts or aliases 11 .

Using Detect Aliases Routine  Click the Detect Aliases button  The routine lists candidate Alias tables  You can rename the Alias tables if required 12 .

Inserting an Alias Manually  Select the table and click the Insert Alias button  Name the Alias table and click OK  Then reset the joins manually 13 .

Defining contexts . 

Contexts are a collection of joins which provide a valid query path to generate SQL.  The most common use of contexts is to separate two query paths, so that one query returns data for one fact table, and the other query returns data for another fact table. You use contexts to direct join paths in a schema which contains multiple fact tables. Aliases are not appropriate in such schema.

14

Resolving Loops using Contexts

Sales

Sal Lines

Country

Customers

Loans There are two possible routes to link Clients with Models:

Loans Lines

 Working with rentals  Working with sales

15

Resolving Loops using Contexts

Rental context

Sale context

16

Detecting and Creating Contexts  Loop Detection routine: suggests candidates for both aliases and contexts  ³Detect Contexts´ detects and proposes a list of contexts to create  ³Insert Contexts´ inserts a context manually 17 .

Display the contexts : View List Mode 18 .

Editing Contexts  Double click the context in the List Mode window  The context name  The highlighted joins are included in the context 19 .

Test in the User module 20 . Use Detect Aliases to detect candidates for aliases 3. Detect and set cardinality on all joins 2. Use Detect Contexts to detect candidates for contexts 5. Insert all required alias tables and joins 4. Create the required contexts 6.Sequence for resolving loops 1.

 Ineffecient!  But joining Country to Client directly creates a loop 21 . the Region joins are still needed in the SQL.Shortcut Joins  If a query includes Client and Country but NOT Region.

the solution  Edit the join to create a Shortcut join:  This is not a Loop! 22 .Shortcut Joins .

Test the structure of a universe  Check the syntax  Test in the User Module 23 .

What You Have Learned  What a Loop is  How and when to resolve a loop using aliases and contexts  The sequence for resolving loops  How to apply shortcut joins 24 .

Module 9 Lists of Values 25 .

Resolving Loops in a Universe 9.How The Course is Organized: Day 2 8. Hierarchies 26 . Lists of Values 10.

What You Will Be Able To Do  Associate or remove a List of Values (LoV) for an object  Control how LoVs are refreshed  Modify a LoV using a condition  Modify a LoV by creating a hierarchy  Base a LoV on a personal file 27 .

What is a List of Values?  A list of the distinct values from the column or columns to which the object refers  A LoV is used on the operand side of a condition in the query panel of the User module  This is only available if set by the designer 28 .

How do Lists of Values work?  A designer can create a LoV which is based on:  A query of the target database  A constant set of values held in a file  In both cases. the result is stored locally in a file on the User ¶s PC. 29 .

Creating a List of Values 
A LoV is created within the Properties tab of an object 

By default, Associate a List and Allow Users to edit are checked: 

It is important to uncheck this box for objects that don¶t need a List

30

Controlling How Lists are Refreshed 
Normally, the first time a LoV is used in a User login session, the system fires a query at the target database. 

The results of this query are used to populate the list, and are stored in the .lov file. 

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

31

Controlling How Lists are Refreshed 

Not normally used - uncheck this box 

Check this box for frequently changing lists 

Check this box for lists that never change

32

Modifying the Content of a List of Values  You can limit the values returned by applying a condition to the LoV  You can simplify the process of choosing a value for Users by creating a hierarchy for the LoV  You can supply a personal data file containing the values for the list. instead of using the results of the query 33 .

Applying a Condition to a List of Values  Click Edit in the Properties box:  Apply the condition in the Query Panel: 34 .

Creating a Hierarchy for a List of Values  Click Edit in the Properties box:  Place the hierarchy objects (which must be sorted) to the right of the LoV object in the Query Panel: 35 .

Creating a Hierarchy for a List of Values  The resulting Hierarchical View of the LoV makes it easier to select the required value:  Country:  Town:  Showroom: 36 .

Lists of Values from the Menu bar:  Select the object:  Select Personal Data: 37 .Basing a LoV on a Personal File  Select Tools.

Basing a LoV on a Personal File  Click OK to acknowledge the message:  Specify the file that contains the values for the list and click OK 38 .

What You Have Learned  How to associate or remove a LoV for an object  Controlling how LoVs are refreshed  How to modify a LoV using a condition  How to modify a LoV by creating a hierarchy  How to base a LoV on a personal file 39 .

Module 10 Hierarchies 40 .

What You Will Be Able To Do  Organize Default Hierarchies for optimum usability  Create Custom Hierarchies  Test hierarchies in the User module 41 .

K. North South Liverpool Manchester Newcastle London Southampton Bristol 42 .What Is a Hierarchy? Level in Hierarchy Data Returned U.

What Is a Default Hierarchy?  A Default Hierarchy is the hierarchy based on the order of the Objects within the Class Default Hierarchies are represented in the User module by the order in which Dimension Objects are organized in the Classes and Objects box of the Query Panel 43 .

The Key to Creating Default Hierarchies  The designer must ensure. that Dimension Objects are organized from the most general to the most specific within the Class 44 . wherever possible.

How are Hierarchies used in Analysis?  Dimension Objects represent the levels in a hierarchy: Top Level Level 1 Level 2 Level 3  A Measure can be analysed at each level 45 .

What Is A Custom Hierarchy?  A Custom Hierarchy combines Objects from Default Hierarchies to build a Custom Analysis Path Custom Hierarchy Default Hierarchies 46 .

Hierarchies)  Add Objects from Default Hierarchies to build a new Custom Hierarchy 47 .Creating Custom Hierarchies (or Tools.

The Effect of Custom on Default Hierarchies  User module Scope of Analysis after a Custom Hierarchy has been created:  No Default Hierarchies are shown 48 .

The Effect of Custom on Default Hierarchies  Selected Default Hierarchies can be added to the Custom Hierarchies in Designer module 49 .

What You Have Learned  How to organize Default Hierarchies for optimum usability  How to create Date objects and Automatic Time Hierarchies  How to create Custom Hierarchies  How to test hierarchies in the User module 50 .

Module 11 Documenting and Distributing a Universe 51 .

What You Will Be Able To Do  Print information about the universe  Print the universe schema  Know the advantages and disadvantages of the two different ways that universes are distributed to end users  Distribute a universe in Workgroup mode  Distribute a universe in Enterprise mode 52 .

Print menu to print 53 .Documenting a Universe  Select the Tools. Options menu then click on the Print tab to select what to print  Select the File.

Universe Design Cycle Phase 3 Phase 1-2 Phase 5 Phase 4 Phase 7 Phase 6  Different phases require different types of universe distribution 54 .

Distributing Universes  There are two methods distributing universes File System BusinessObjects Repository 55 .

unv (Shared Connection) 56 .Workgroup Mode S:\Test Access controlled By network security File server S:\Designer Business Objects Universe Motors.

unv Motors.Enterprise Mode Business Objects Revision number checked when used Universe Universe Domain Name Motors.unv BusinessObjects repository Revision number incremented Export Business Objects Universe Universe Domain Name Motors2k.unv Supervisor in control User based security allocated to user groups (Secured Connection) 57 .

This number guarantees the user will use the more recent version of the universe Repository Universe Domain Document Domain Security Domain Designer 58 .Exporting a Universe  The Designer exports a universe to the universe domain and allocates universe access to one of the groups of users he or she belongs to  The revision number of the universe is incremental.

Module 12 Universe Maintenance 59 .

What You Will Be Able To Do       Know when a new version of a universe may be required Be able to identify changes to the target database of a universe Know how version changes will affect existing end user reports Be able to copy and past objects between universes Be able to link universes and appreciate the different strategies required Be able to include universes 60 .

changed or renamed in database  Users request new classes or objects Note: Your primary concern when you introduce a new version of a universe should be what effect it will have on existing end user reports Tip: Do not distribute new versions of universes too frequently! 61 .Reasons for Universe Maintenance  New tables added to database  Tables deleted.

Changes to the Target Database  The implications of modifying the underlying database for BusinessObjects universes varies in severity:    No Impact: Adding new columns Adding new tables    Severe Impact: Renaming/moving database Changing existing column and table names  Deleting tables and columns 62 .

Detecting Changes to the Universe  Choose View. Refresh Structure  Changed tables are highlighted in the Structure  A message on the screen indicates that tables have been deleted 63 .

The Effect of Changing Objects  Changes to existing Objects in a Universe can have an impact on existing Documents created from the Universe:     No Impact:   Impact: Redefining Object SQL Copying to different Class Moving in same Class or to a different Class  Adding new Objects Deleting an existing Object  Deleting and then recreating an object with exactly the same definition Renaming an Object 64 .

Adding New Tables to an Existing Universe  The workflow is: Add tables to the universe structure Insert joins and set cardinalities Delete existing contexts Detect aliases Detect contexts Create new objects Set up hierarchies 65 .

Linking Universes  Linking can mean reduced maintenance but there are limitations Universe A Universe A Universe B 66 .

The Derived Universe  The linked universe structure and objects cannot be edited in the derived universe  The linked universe should be treated as though they were new tables inserted in the derived universe. The same procedure should be applied 68 .

Including Universes  Including a Universe COPIES structure and objects to the derived universe: Universe A Everything from Universe A Universe A Universe B 69 .

Included Universes  Included universes become part of the new universe 70 .

What You Have Learned  Designers must be aware of changes to the underlying databases and the implications these have for their universes  Linking universes can make maintenance easier  There are several different approaches to linking universes  You can also include universes 71 .

Module 13 Aggregate Awareness 72 .

What You Will Be Able To Do  Understand the reasons for using Aggregate Awareness  Know when to apply Aggregate Awareness  Be able to apply Aggregate Awareness 73 .

 These are used to speed up queries which contain statistics (for example. for instance. year rather than event level. Revenue) reported at.What is Aggregate Awareness  Some databases have Summary Tables which contain figures aggregated to a high level.  Aggregate Awareness is the BusinessObjects process by which these higher level aggregates are incorporated into a universe. 74 .

75 .Summary Tables  Check the columns in the Summary Table:  Foreign Key columns are used for the joins  The other columns relate to objects that require @AggregateAware definitions  Note that Summary Tables without Foreign Keys do not need joins .they can be free floating tables.

SALE_QTY * MODEL.MODEL_PRICE * ((100 .How Summary Tables are used in SQL  Aggregates of a normalized database are based on event / fact level data.SALE.SALE_SALE_DISCOUNT) / 100))  Summary tables may be added to a database which hold data at a higher level of aggregate.ANNUAL_SALE_VALUE)  Making use of summary table data speeds up response times. 76 . Sale 226 rows Sale_Model 233 rows Model 33 rows Sales Revenue = sum(SALE_MODEL. Annual_Figures 26 rows Sales Revenue = sum(ANNUAL_FIGURES.

set joins and cardinality 2 Set the contexts 3 Redefine objects using @AggregateAware 4 Define incompatible objects using Aggregate Navigation 77 .Procedure for Applying Aggregate Awareness 1 Insert the Summary Table(s) in the universe structure.

Step 1: Inserting a Summary Table & Setting Joins  Set the joins and the cardinality  Add the Summary Table to the structure 78 .

Step 2: Detecting Contexts  The Annual_Figures context  Set the contexts 79 .

 @AggregateAware Syntax:  @AggregateAware(Definition1.Definition2.DefinitionN) From the most to the least Aggregated  The last definition must be valid for all the queries 80 .«.Step 3: Redefining Objects  Edit the objects affected by the Summary Table.

Step 4: Incompatible Objects  Aggregate aware objects can only be compatible with objects derived from tables in the same context as the summary table  Incompatible objects are specified using Aggregate Navigation 81 .

not all  incompatible objects may be detected Select the Summary Table: automatically.  Individual objects are checked to define  them as incompatible: checked: Incompatible objects are  Click Detect Incompatibility: 82 .Step 4: Aggregate Navigation  The Aggregate Navigation box is opened from the Tools menu  You must check carefully .

you must always test the results in the User module.Testing Aggregate Awareness  As with any universe element.  Use both compatible objects and incompatible objects in different queries to make sure all levels of Aggregate Awareness are operating correctly. 83 .  Run queries using the aggregated measures from the Summary Table.

Module 14 Generating OLAP Universes 84 .

 The universe is created automatically from a selected connection to a OLAP data source using an OLAP query flattening driver that is installed as an add in to Designer XI.Overview Of OLAP Universes  A OLAP universe is a Business Objects universe that has been generated from a OLAP cube or query. 85 .

The universe creation process is automatic once you have selected the connection. and details. The universe structure appears in the Universe pane. OLAP structures are mapped directly to classes. Once exported to the CMS. measures. dimensions. There is no table schema in the Structure pane. the universe is then available to Web Intelligence users to create queries and reports. You save and export the universe to the Central Management System (CMS).What OLAP data sources can be used to create a universe? You can use Designer to create OLAP universes from the following OLAP data sources: 1) BW SAP 2) 3) Microsoft Analysis Services Essbase You create a OLAP universe by selecting a OLAP connection to a QueryCube or InfoCube. 86 .

87 . The universe is created automatically once the connection is selected. Create a new connection to a InfoCube or Query cube. Create a new universe by selecting the new connection to the OLAP data source. 3.Overview of the universe creation process  Universe creation stage : 1. 2. Save the new universe and export to the CMS.

 There are two ways to create a connection:  From the Connections list (Tools > Connections).Creating a OLAP connection You create a connection to a BW Cube or Query Cube. One connection must be created for each cube that you want to use to create a universe. The steps through the wizard are the same as documented below. This box appears when you select File > Parameters or click the new universe icon. Each connection maps the structures in the cube data source to a universe. 88 . and the New Connection Wizard appears. From the Parameters page.  From the Parameters dialog box. you click New.

The New Connection wizard appears. Click Add. All the connections available to the current Designer session are listed here. The node expands to the supported middleware. This is the target database for the connection. Start Designer. 2. If the Quick Designer Wizard appears. Click the data access driver. This is Business Objects data access driver for the OLAP middleware. Select Tools > Connections. click Cancel. Click Next. 3. Expand the node for your target OLAP data source. The Connections list appears. The OLAP data access driver appears. 4. The Database Middleware page appears. 5. The wizard guides you through the connection creation process. Expand the middleware node. It lists the database and middleware that correspond to your Data Access driver key. 6. Click Next.To create a OLAP connection 1. 89 .

2)Name 2)Connection name. For SAP BW.The Login Parameters page appears. You must use a secured connection to export the universe to the CMS. 3) Your database user name 3)User name 90 . This is the name that appears on the list of connection available to the universe. you have the following logon options:  Logon options 1)Type  Description 1)Security level for connection.

The Login Parameters  Logon options  Description Use Single Sign-on when viewing reports Password Server System Client Language The user name and password used to access the CMS are automatically used as database login parameters. Required SAP client number. Connection language. 91 . Required SAP login information. Your database Password Name or IP address of the BW server that contains the target cubes. For example EN for English.

92 . This shows all of the OLAP cubes available to the target server.After setting the Logon Preferences The Cube browser appears.

This lists connection parameters that you can set to manage the connection. Type or select Advanced options and click Next. You can accept the default settings when you create the connection and modify them at any time later. Select the target cube. The Custom page appears. There are no parameters listed on this page for OLAP connections.Then Expand cube nodes to display the cubes and query cubes available. This is the cube that you want to use to create a universe. Click Next. 93 . The Advanced page appears.

94 .The Connections list appears. The OLAP Connection is Created after pressing the Finish Button. The new connection appears in the list.

Once the connection is selected. 95 . select File > Parameters.Creating a OLAP universe You create a OLAP universe using one of two ways:  Creating a OLAP universe by selecting a connection. Creating a OLAP universe by selecting a connection : Click the New Universe icon. the universe is created automatically. The Parameters dialog box appears.  Creating a OLAP universe using the Quick Design Wizard. Or From an empty Designer session.

Creating a OLAP universe by selecting a connection : 96 .

Type a name and description for the universe. Select a connection from the Connections drop down list box. 97 . This connection must be a connection to a OLAP data source. Click Test to validate the connection. you can create a connection by clicking the New button. If you do not have a connection.

98 .The generated universe appears in the Universe pane. The universe generation can take while to complete depending on the size of the target cube.

 If you want to define a new connection to a OLAP cube. do the following:  Type a universe name.Creating a OLAP universe using the Quick Design Wizard From the Universe Parameters page. click New.  Select the OLAP cube connection from the database connection drop down list box. 99 . completed define universe parameters page is shown below. The New Connection wizard starts.

The final page of the wizard appears. Select the repository folder from the Folder drop down list. 100 . To save and export a OLAP universe 1. Saving and exporting a OLAP universe Once you have generated the OLAP universe. you import the universe. When you want to update the universe. The universe is exported to the CMS. It lists the number of class and objects that the universe contains. modify it. you export the universe to the Central Management System (CMS) to make the universe available to other designers or Web Intelligence users. 2. The generated universe appears in the Universe pane. Select File > Export. The Export universe box appears. then export the updated version.

Module 15 Creating universes from metadata sources 101 .

Creating universes from metadata sources Overview You can use Designer to create a universe from a metadata source. You can create universes from the following metadata sources:  XML metadata sources: Common Warehouse Model (CWM Relational 1. and is then available to Web Intelligence and Desktop Intelligence users to run queries and create reports.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  Oracle Analytic Workspaces (Oracle OLAP) 102 . Once the universe has been created it can be exported to the Central Management System (CMS) as any other universe.

This is the source XML file or database view that you use to build a universe. 103 .Selecting a Metadata Source  You can select a metadata source to create. A universe creation wizard takes you through steps to select a connection for the metadata source.  You have the following options available from the Metadata Exchange panel: 1)Create a universe from : You select a metadata source format from the drop down list. selecting the metadata components that you want to be mapped to the universe. and finally the generation of the universe. or update a universe from the Metadata Exchange panel (File > Metadata Exchange).

then save a universe in that format. A universe update wizard takes you through the steps needed to update the universe. 3)Export a universe to : You select a metadata format to which you can export a universe.2)Update a universe from : You select a metadata source that has been updated. The source has been updated. 104 . This is the metadata source That has been used to create a universe. and now you want to update the universe with the same modification. you can select the DB2CV XML standard. For example.

To select a metadata source option 1. Select File > Metadata Exchange. The Metadata Exchange panel appears. 105 .

A creation. If you want to update an existing universe. 106 .If you want to generate a new universe. select a metadata format from the Create a universe from drop down list box. select the target metadata format from the Export a universe to drop down list box. If you want to export a universe to a metadata format. select the metadata source that was used from the Update a universe from drop down list box. update. or export wizard starts.

The Metadata Exchange panel appears. The Universe Builder wizard starts. Click the Browse button and select a XML source file. The available database tables and columns are listed in the left pane. 107 . Click Next. Click the source database. 4. Click Next. Click Next. 2. 3.Creating a universe from a XML metadata source To generate a universe from a XML metadata source 1. This is the file that you want to use to generate the universe. The XML file source page appears. Select a metadata format from the Create a universe from drop down list box. The universe elements page appears. The Select database page appears.Click OK. Select File > Metadata Exchange.

A connection and universe properties page appears. It lists a summary of the options that you have selected during the wizard. Click Next. The generated universe appears in the universe and structure panes of Designer. This is the connection to the data source that the universe uses to retrieve data. Select or clear options check boxes. Click the Advanced button to set trace log file and XML source file options.Click a connection in the connections list. Click Next. 6. Click Finish. Type a universe name. The tables and columns in the right pane are those that appear in the generated universe. 108 .5. The universe generation summary page appears. You can use the arrow buttons to add and remove tables from the universe pane as necessary. Select one or more tables and columns and click the right arrow to populate the right pane. It lists the connections available to Designer.

Choosing connection and universe options You have the following options on the connection and universe build page of the metadata universe builder wizard: 109 .

Choosing connection and universe options 110 .

The universe file page appears. This is the universe that you want to update from the selected XML metadata source.Updating a universe Select a metadata format from the Update a universe from: The Universe Builder wizard starts.  Click a connection in the connections list. This is the connection to the data source that the universe uses to retrieve data. Click the Browse button and select a universe. This is the file that you want to use to update the universe. The updated universe appears in the universe and structure panes of Designer. 111 . The Browse button and select a XML source file. Select the source database.

Exporting the Universe can be done through the Metadata Exchange panel Universe pre-requisites for export Universe level restrictions Each universe is exported to a Cube Model.Exporting a universe to DB2CV You can export a universe to IBM DB2 cube View XML format file. and not exported. 112 . Contexts are not taken into account. 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. Custom hierarchies: the levels of a custom hierarchy must be grouped in the same class. The universe definition is exported to a XML file that complies with IBM DB2 Cube Views XML format.

All other @functions are not mapped in the export. as they are not used for optimization. 113 . Joins If the left or right column of a join does not match an object in the universe.  Each class must contain objects that are built on the same dimension tables. Note: Conditions are not supported in DB2 Cube Views objects.  Multi-parameter aggregation functions are not exported.Universe pre-requisites for export Classes and objects  @Select function is the only supported @function. then an attribute for this column is automatically created and added to the dimension (or fact) that contains the column table.  Conditions in the Where field of an object definition are not exported.

The following sections give detailed descriptions for structures that are mapped from a universe to IBM DB2 Cube Views when a universe is exported to a XML file. Universe to cube model The following describes mapping for a universe to cube model Measure to measure 114 .

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

Dimension and detail object to attribute

115

Fact table to Fact

Default hierarchy to hierarchy

Custom hierarchy to hierarchy

116

Join to join

117

Oracle OLAP Universe Builder wizard starts. You connect to the Oracle OLAP Universe Builder wizard from the Metadata Exchange panel (File > Metadata Exchange). Start Metadata Exchange and select Oracle OLAP from the Create a universe from drop down list.Creating Universe From Oracle Analytic Workspaces (Oracle OLAP) You use the Oracle OLAP Universe Builder wizard to guide you through the steps of universe creation. 118 .

Oracle OLAP Universe Builder wizard: 119 .

120 .Universe and view creation options You can create universes and views as follows: Oracle OLAP Universe Builder wizard Guides you to Create the required.

 Creates measure objects 121 . Multi-hierarchy dimensions are supported in the view definition and in the universe. BusinessObjects Oracle OLAP Universe Builder performs the following main tasks:  Inserts the relational fact view in the universe as a real view or as Derived Table.How is a universe generated from an OLAP cube? When you create a universe with the Oracle OLAP Universe Builder.  Add aliases to represent the dimension levels and hierarchies  Joins the relational view to the dimension tables with regular joins and shortcut joins.  Creates a subclass for each hierarchy if a dimension has more than one hierarchy.  Define aggregate navigation to resolve object incompatibility that results from the multi-hierarchy dimensions.  Creates a class of objects for each Cube dimension and an object for each level of the dimension. The expressions of the joins are specific to this solution. it is automatically set up for SQL access to Oracle Analytic Workspaces.  Defines object expressions using the AggregateAware function to handle the Aggregation Navigation  Transforms objects that map real dimension members (Identifiers) to Details of objects that represent the member descriptions.

Questions ? 122 .