BusinessObjects Universe Builder Guide

BusinessObjects Universe Builder Guide

Copyright

© 2008 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business 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 Objects logo, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, 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, Let there be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty 2008-03-05

Third-party Contributors

Contents
Chapter 1 Introduction 5 Overview of creating universes from metadata sources..............................6 What is Universe Builder?...........................................................................6 Universe Builder and Designer....................................................................6 When do you use Universe Builder instead of Designer?...........................7 Chapter 2 Universe Builder basics 9

Starting Universe Builder...........................................................................10 Chapter 3 Building universes from XML metadata sources 11

Overview of how you create a universe from XML metadata....................12 XML metadata to universe component mapping.......................................13 Selecting a XML data source.....................................................................13 Creating a universe from a XML data source............................................14 Universe and connection options for a universe built from a XML source...................................................................................................15 Viewing the trace log.................................................................................17 Setting trace log options............................................................................17 Chapter 4 Updating XML metadata source universes 19

Updating a universe from a XML metadata source...................................20 Chapter 5 Exporting a universe to a XML file format 23

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

BusinessObjects Universe Builder Guide

3

Contents

Exporting a universe to DB2 Cube Views formats.....................................25 How to identify non-matching universe metadata......................................26 Mapping specific SQL expressions...........................................................28 How universe structures are mapped to DB2 Cube Views metadata........30 Universe to cube model........................................................................30 Class to dimension...............................................................................31 Fact table to Fact..................................................................................31 Measure to measure............................................................................32 Dimension and detail object to attribute...............................................33 Dimension and detail relationship to attribute relationship...................33 Default hierarchy to hierarchy..............................................................34 Custom hierarchy to hierarchy.............................................................34 Join to join............................................................................................34 Chapter 6 Building universes from Oracle Analytic Services 37

Overview of how you create a universe from Oracle Analytic Services.....38 How is a universe generated from a OLAP cube?....................................38 Analyzing the relational view.....................................................................39 What are the shortcut joins in the universe used for?...............................40 How are Oracle OLAP structures mapped to universe components?.......42 How to create a Oracle OLAP universe.....................................................48 Creating a view and generating a universe..........................................49 Create a view only................................................................................51 Creating Oracle OLAP universe from an existing view........................52 Appendix A Get More Help 53

Index

57

4

BusinessObjects Universe Builder Guide

Introduction

1

and then generate the universe in Designer. dimensions. A universe creation wizard allows you to connect to a metadata source. This product is described in this guide. Universe Builder select objects to include in a universe. then generate a universe. You then generate the universe. you map metadata structures to equivalent classes. objects. Once you start Universe Builder. and details used in a standard BusinessObjects universe. then using a universe creation wizard. Designer Stand alone product installed with BusinessObjects XI Release 3 that allows you to connect to a metadata source. Universe Builder and Designer You can create universes from metadata sources with both Universe Builder and Designer. you connect to a metadata source.1 Introduction Overview of creating universes from metadata sources Overview of creating universes from metadata sources BusinessObjects XI Release 3 is installed with two products that you can use to create universes from metadata sources and Oracle Analytic Services: Product Description From Designer. you can create universes automatically from metadata sources by selecting File > Metadata Exchange. 6 BusinessObjects Universe Builder Guide . What is Universe Builder? Universe Builder is Business Objects software that allows you to create universes from XML metadata sources and Oracle Analytic Services. This process is described in the Designer Online Help and in the Designer’s Guide.

The universe creation mechanism for each supported metadata source is a software plugin to Designer. Designer is used for the universe generation at the end of the creation process. You use Universe Builder to create a universe from a metadata source plugin that has been updated. The metadata plugins can be updated by Business Objects. If the plugin for a metadata source is updated. You can update the metadata plugins used to generate universes when newer versions are available from Business Objects. BusinessObjects Universe Builder Guide 7 .Introduction When do you use Universe Builder instead of Designer? 1 Universe Builder is a stand alone product that provides an independent user interface for universe creation from metadata sources. The metadata source support is fixed at the level of the installed version. There is a metadata source plugin for each supported metadata source. but the updated plugin is not available from Designer. why use Universe Builder and when do you use it? Universe Builder is an independent product. then you can install the updated plugin and use the new capabilities from Universe Builder. or to use a plugin for a newly supported metadata source. Designer can not be updated with new or updated metadata exchange plugins. You use either Designer or Universe Builder based on the following: • • You use Designer to create a universe from a metadata source supported at the time of this release. When do you use Universe Builder instead of Designer? Given that you can use either Designer or Universe Builder to create a universe from metadata source.

1 Introduction When do you use Universe Builder instead of Designer? 8 BusinessObjects Universe Builder Guide .

Universe Builder basics 2 .

2. Login information System User Name Password Authentication Description Name of the CMS server. Your repository password. or clicking its tab. The login box for the CMS appears. Your security level 3. The Universe Builder pane appears. Once you start Universe Builder. This information is normally provided for you by the BusinessObjects administrator. 10 BusinessObjects Universe Builder Guide . Each metadata source also appears as a tab in the central part of the pane. the Universe Builder pane appears. Click the OK button. Type the following information. Select Universe Builder from the BusinessObjects group of products in the Start menu. Your repository user name.2 Universe Builder basics Starting Universe Builder Starting Universe Builder You start Universe Builder from the task bar by clicking the Universe Builder icon in the group of installed Business Objects products for this release. 1. All the metadata sources supported in this BusinessObjects release are listed as icons in the Bridges column to the left of the Universe Builder pane. You can activate a metadata source by clicking either its icon to the left. You are prompted to log into the CMS before Designer starts.

Building universes from XML metadata sources 3 .

Once you have created the universe from a metadata source. You then start a creation wizard that allows you to select cube tables to include in the universe. The universe creation process is the same for all XML metadata sources.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 select a connection. Once you have selected your connection. set creation options and generate the universe. You save and export the universe to the Central Management System (CMS). You create a view on the database. the universe is then available to Web Intelligence users to create queries and reports. The universe creation process for a Oracle Analytical Workspaces datasource is different. Once exported to the CMS. 12 BusinessObjects Universe Builder Guide . then create a universe from the view. that allows you to connect to a target XML file. You create a universe by following a metadata source wizard. This is described in the chapter Building universes from Oracle Analytic Services. a universe creation panel specific to Oracle Analytic Workspaces appears. You can then select the cube associated with the XML metadata source.3 Building universes from XML metadata sources Overview of how you create a universe from XML metadata Overview of how you create a universe from XML metadata You can create or update a universe from XML files conforming to the following data source standards: • • • • • • Common Warehouse Model (CWM Relational 1. you can modify any of the universe components as for any other universe.

Click the icon or tab for your metadata source.PKColmn=FKTable. The Universe Builder panel appears.Building universes from XML metadata sources XML metadata to universe component mapping 3 XML metadata to universe component mapping The following table shows the BusinessObjects structures that are mapped from information in the XML file: XML information Database Table or view Table business name Column Column business name Column SQL data type Table/column description Foreign key-Primary key relationship (PKTable. BusinessObjects Universe Builder Guide 13 . 2. you can click either the icon to the left of the Universe Builder panel or the tab at the top of the Universe Builder panel.FKColumn) Universe structure Universe Class. column Object name Object type Class/object description Join expression Selecting a XML data source You select a metadata source (an XML file) to create or update a universe from the Universe Builder panel. Start Universe Builder. For example to create a universe from a CWM relational 1.0 metadata source. 1. table Class name Object.

and finally the generation of the universe. This is the file that you want to use to generate the universe. 4. Example: Creating a universe from a XML data source Once you have selected a metadata source. Click Next. The universe elements page appears. you use a universe creation wizard to take you through the steps to select the metadata elements that you want to be mapped to the universe. The XML file selection page appears. • Click the Browse button and select a XML source file. The connection wizard starts. Click the source database icon under the XML metadata source name in the Universe Builder panel. Click Finish. Do one of the following: • Select File > Metadata Sources • Click the Metadata Sources button. The XML file and associated database name appear in the Universe Builder pane. 1. 2. 6. The Universe Builder wizard starts. 3. The available database tables and columns are listed in the left pane. 5.3 Building universes from XML metadata sources Creating a universe from a XML data source 3. Start Universe Builder and select a metadata source. 4. Do one of the following: • Type a file path. Do one of the following: • Select File > Create Universe • Click the Create Universe button. 14 BusinessObjects Universe Builder Guide . Click Next.

Select one or more tables and columns and click the right arrow to populate the right pane. Do the following on the connection and universe properties page: • Type a universe name. • Click the Advanced button to set trace log file and XML source file options. • Select or clear options check boxes. Related Topics • • Selecting a XML data source on page 13 Universe and connection options for a universe built from a XML source on page 15 Universe and connection options for a universe built from a XML source You have the following options on the connection and universe build page of the metadata universe builder wizard: BusinessObjects Universe Builder Guide 15 . The generated universe appears in the universe and structure panes of Designer. You can use the arrow buttons to add and remove tables from the universe pane as necessary 6. 7.Building universes from XML metadata sources Creating a universe from a XML data source 3 5. It lists a summary of the options that you have selected during the wizard. The tables and columns in the right pane are those that appear in the generated universe. Click a connection in the connections list. A connection and universe properties page appears. The universe generation summary page appears. • Click Next. 8. Click Finish. Click Next. It lists the connections available to Designer. This is the connection to the data source that the universe uses to retrieve data.

3 Building universes from XML metadata sources Creating a universe from a XML data source Wizard page Universe options Description Listed connections are connections available to Designer. Path to the trace folder. You can Source File Folder browse to and select a folder. Advanced settings Path to the default folder that stores the parameter files. and Save universe automatically is selected. Select a connection Universe name Build universe settings Save universe au. the universe is saved on cretomatically ation. These are files created when a universe is created. When selected. it is a filter that directs the bridge to the selected metadata through the original XML file. This is the connection to the target RDBMS. the new universe replaces the existing universe. Replace existing universe General tab: Traces File locations tab: Path to the default folder that stores the XML Default XML files used to create universes. You can browse to and select a folder.When selected. if a universe with the same name exists. The parameter file does not store the selected metadata. The name of the universe that will be generated. These files store and reference the selected metadata so that it can File locations tab: be reused for creating or updating other uniParameter File verses. This is the folder that holds the log files when universes are generated. You can browse to and select a folder 16 BusinessObjects Universe Builder Guide .

You can set the following trace options: Tab Option Description Path to the trace folder.Building universes from XML metadata sources Viewing the trace log 3 Viewing the trace log • Example: Setting trace log options The Universe Builder creates a log file that contains trace information for view and universe creation. General Traces File locations Default XML Source File Folder BusinessObjects Universe Builder Guide 17 . You can change the default target folder. This is the folder that holds the log files when universes are generated. You can browse to and select a folder. Path to the default folder that stores the XML files used to create universes. You can browse to and select a folder. The log file is generated in the default folder <INSTALL DIR>\Log Files.

Select View > Options or click the Options button.3 Building universes from XML metadata sources Setting trace log options Tab Option Description Path to the default folder that stores the parameter files. Set options as required. Parameter File 1. 3. These files store and reference the selected metadata so that it can be reused for creating or updating other universes. 18 BusinessObjects Universe Builder Guide . it is a filter that directs the bridge to the selected metadata through the original XML file. The Options page appears. 2. These are files created when a universe is created. The parameter file does not store the selected metadata. Click OK.

Updating XML metadata source universes 4 .

2.4 Updating XML metadata source universes Updating a universe from a XML metadata source Updating a universe from a XML metadata source You select a metadata source that has been updated. The available database tables and columns are listed in the left pane. This is the metadata source that has been used to create a universe. Click Next. This is the universe that you want to update from the selected XML metadata source. The Options box appears. The tables and columns in the right pane are those that appear in the generated universe. 9. and Lineage properties. 1. The elements to update page appears. • Click the Update Universe button. Click the source database icon under the XML metadata source name in the Universe Builder panel 3. 20 BusinessObjects Universe Builder Guide . Do one of the following: • Select File > Update Universe. The universe file page appears. The Universe update wizard starts. Click Next. You can use the arrow buttons to add and remove tables from the universe pane as necessary. and now you want to update the universe with the same modification. The source has been updated. 7. See the section Selecting a XML metadata source for information on doing this. Tables that have been added or modified are indicated with a red check mark 6. Mapping Expression. Click the Browse button and select a universe. 5. Object Type. A universe update wizard takes you through the steps needed to update the universe. The universe elements page appears. Start Universe Builder and select a metadata source. Click Next. Select one or more tables and columns and click the right arrow to populate the right pane with the tables that have been modified. Click the Properties tab and select radio buttons to keep or replace Business Name. Click the Advanced button. 8. 4.

12. then click Next. Click Finish. Click the File Location and General tabs to change parameter file paths. concatenate. Click the Description tab and select radio buttons to keep.Updating XML metadata source universes Updating a universe from a XML metadata source 4 10. BusinessObjects Universe Builder Guide 21 . The updated universe appears in the universe and structure panes of Designer. 11. It lists a summary of the options that you have selected during the wizard. The universe generation summary page appears. or replace Business and Technical descriptions.

4 Updating XML metadata source universes Updating a universe from a XML metadata source 22 BusinessObjects Universe Builder Guide .

Exporting a universe to a XML file format 5 .

The universe definition is exported to a XML file that complies with IBM DB2 Cube Views XML format. The universe must contain at least one measure. 24 BusinessObjects Universe Builder Guide .• • strictions • • Each universe is exported to a Cube Model. IBM DB2 Cube Views reads the metadata from the XML file. Universe pre-requirements for export to DB2 Cube Views The following list describes the universe pre-requisites necessary for a successful universe export to the XML file: Universe element affected Restrictions • • Universe level re. and recommends the appropriate Automatic Summary Table (AST) for future query optimization. Links between universes are not supported. and not exported. A universe must match a single snowflake schema with a single fact table. Custom hierarchies: the levels of a custom hierarchy must be grouped in the same class. Contexts are not taken into account. This file can then be loaded in IBM DB2 Cube Views using the API or OLAP Center tool.5 Exporting a universe to a XML file format Overview of exporting universes to XML file formats Overview of exporting universes to XML file formats You can export a universe to IBM DB2 cube View XML format file.

Any other measure in other classes are automatically added to the Fact object in IBMDB2CV. Click Next. Exporting a universe to DB2 Cube Views formats You export a BusinessObjects universe to a IBM DB2 Cube Views XML file as follows: 1. Do one of the following: • Select File > Export Universe. Browse to and select a universe file. then an attribute for this column is automatically created and added to the dimension (or fact) that contains the column table. Note: Conditions are not supported in DB2 Cube Views objects. 4. 3. Each class must contain objects that are built on the same dimension tables. • Click The Export Universe button. All the objects (attributes in IBMDB2CV) that are referenced by the same dimension in IBMDB2CV.Exporting a universe to a XML file format Exporting a universe to DB2 Cube Views formats 5 Universe element affected Restrictions • • @Select function is the only supported @function. as they are not used for optimization. A universe source file page appears. All other @functions are not mapped in the export. 2. Conditions in the Where field of an object definition are not exported. BusinessObjects Universe Builder Guide 25 . must be grouped in the same class in the universe. then click Next. Classes and objects • • • Joins If the left or right column of a join does not match an object in the universe. Multi-parameter aggregation functions are not exported. Start Universe Builder and click the IBMDB2CubeViews icon or tab. The export wizard starts.

A page appears showing the structures that will be exported. Do the following: • Enter a name for the fact table. A summary page appears. and do not respect IBM DB2 Cube Views multi-dimensional rules.5 Exporting a universe to a XML file format How to identify non-matching universe metadata An OLAP information page appears. The metadata is loaded. 5. or you can accept the fact table name by default. 26 BusinessObjects Universe Builder Guide . Verify that the export information is correct. 8. • Click Next. A universe is based on relational metadata that does not have multi-dimensional design constraints. • Enter a name for the schema. Type a name for the XML file and click Next. The XML file is created in the universes folder of your user profile. 7. C:\Documents and Settings\<username>\Application Data\Business Objects\Business Objects <version>\Universes. To correctly match relational structures. then click Finish. 6. How to identify non-matching universe metadata This section describes how objects in a universe that do not have a multi-dimensional match in IBM DB2 Cube Views are identified and processed during the export of a universe definition to an XML file. All the objects in a universe do not necessarily match equivalent IBM DB2 Cube Views objects. Universe Builder must run certain automatic detection processes to identify and define the required and appropriate metadata for IBM DB2 Cube Views. for example. Click Next. The affected multi-dimensional objects are described below.

Attributes are not directly deduced from the columns of tables in the universe. A IBM DB2 Cube Views dimension object is deduced directly from a BusinessObjects class. • BusinessObjects objects referenced in Select field of other BusinessObjects objects by the @Select statement. Measures BusinessObjects Universe Builder Guide 27 . • Columns involved in a join.Description ta Fact The IBM DB2 Cube Views Fact object is automatically built from the set of measures found in the universe. The tables inferred by BusinessObjects objects within the class. then it is ignored. Dimensions All the objects within a class determine the attributes of the IBM DB2 Cube Views dimension. If a measure is not built on the same fact table. Tables that are not identified as Facts are assumed to be dimension tables. Attributes The detail-dimension relationship in a universe is translated Attribute relationto an attribute relationship of type Functional Dependency ships in IBM DB2 Cube Views. All classes are searched for measure objects. Candidate attributes are detected and identified from the following information: • BusinessObjects objects within a class. are detected by parsing the object’s Select field. Joins Joins and their properties are directly read from universe structure.Exporting a universe to a XML file format How to identify non-matching universe metadata 5 Non-matching universe metada.

where a custom hierarchy can contain levels coming from different Business Objects classes. • If the universe has custom hierarchies. This is not the case in a universe.5 Exporting a universe to a XML file format Mapping specific SQL expressions Non-matching universe metada.Description ta A hierarchy in DB2 Cube Views is linked to a dimension object and all its levels are members of this same dimension. 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 SELECT of a measure: • • • Detect tables and columns involved in a measure and map them to sqlExpression:column Identify the aggregation function Determine the formula expression and map it to sqlExpression:template. then the hierarchies for export to IBM DB2 Cube Views are deduced from the objects. then they are exported without any modification. using the object order within each class. 28 BusinessObjects Universe Builder Guide . Hierarchies Mapping specific SQL expressions Certain SQL expressions are mapped in particular ways by the export process. Hierarchies are treated as follows: • If a universe uses only default hierarchies.

Column In a complex join.Exporting a universe to a XML file format Mapping specific SQL expressions 5 @AggregateAware function When an object contains the @AggregateAware function.age between Age_group.age >= Age_group.age_max Shortcut joins Not exported to IBM DB2 Cube Views.age <= Age_group. For example: A @AggregateAware expression for a measure expression in the universe is as follows: @Aggregate_Aware( sum(AggregatedTable1. sum(AggregatedTable2. This is the expression that contains the lowest level of aggregation used by the function. Theta joins A theta join is split into two IBM DB2 Cube Views joins. For example: A join in a universe has this expression: Customer.Amount_sold)) The expression that is mapped to IBM DB2 Cube Views is: sum(Fact_Table. only the last parameter of the @AggregateAware function is taken into account.Column=RightTable. where the operator BETWEEN is replaced by operators <= and >=.age_min Join2: Customer. The BusinessObjects UMB maps each expression in the complex join to an attribute pair of IBM DB2 Cube Views within the same join.age_min and Age_group.Amount_sold)) Complex join expressions The expression of a complex join in a universe can consist of expressions of type: LeftTable.Sales_revenue).Sales_revenue). sum(Fact_Table. these type of expressions can be linked together with the AND operator. Shortcut joins in a universe represent an alternate path to improve performance of queries by not taking into account BusinessObjects Universe Builder Guide 29 .age_max This join will be split into two joins with the following expressions: Join1: Customer.

5 Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata intermediate tables. they are not exported. As shortcut joins create loops within a cube model. • • • • • • • • • 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: Universe property Short name (file name) Universe name (long name) Description Fact table List of classes Cube property Cube file name Business name. By default the name is the universe short name (<universe short name>) Comments name factsRef dimensionRef 30 BusinessObjects Universe Builder Guide . Each section provides detailed descriptions for structures that are mapped from a universe to IBM DB2 Cube Views when a universe is exported to a XML file. How universe structures are mapped to DB2 Cube Views metadata The following universe structures are mapped to corresponding IBM DB2 Cube Views structures.

Dimension property Name and Business name Comments attributeRef joinRef If hierarchy is a custom hierarchy. Joins between dimension tables inferred by the class. 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. The hierarchies are put in the herarchyRef property. BusinessObjects Universe Builder Guide 31 .Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata 5 Universe property List of joins involving the fact table. Cube property joinRef Class to dimension The following table describes the mapping for a class to a dimension: Class property Name Description List of dimension and detail objects. then the dimension is modified to get all hierarchy levels in the same dimension as required by IBM DB2 Cube Views.

5 Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata Fact table property Fact property Fact table name You enter this name manually in the Name and Business name Facts box in the Export universe panel. Table description List of all measures in the universe Comments measureRef List of columns and objects referenced attributeRef in measures Measure to measure The following table describes the mapping of measure to a measure: Measure properties Name Description Measure properties Name and Business name Comments Columns and objects inferred by Select sqlExpression column statements. You can also accept the default name Facts_<universe name>. Select statement formula Aggregation function sqlExpression template aggregation function 32 BusinessObjects Universe Builder Guide .

Concat Name and Business name character is “_” Dimension Detail Left attribute Right attribute BusinessObjects Universe Builder Guide 33 .Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata 5 Dimension and detail object to attribute The following table describes the mapping of dimension and details to attributes: Dimension and detail objects Name Description Columns and objects referenced in Select statements Select statement formula Attributes Name and Business name Comments sqlExpression column sqlExpression template Dimension and detail relationship to attribute relationship The following table describes the mapping of Dimension/detail relationships to attribute relationships: Dimension/detail relationship Attribute relationship Dimension name + detail name.

Detail objects must not AttributeRef be part of the hierarchy.5 Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata Default hierarchy to hierarchy The following table describes the mapping of default hierarchies to hierarchies: Default hierarchy Name Hierarchy Names and Business name List of objects. Custom hierarchy to hierarchy The following table describes the mapping of a custom hierarchy to hierarchy: Custom hierarchy Hierarchy Name List of objects Name and Business name attributeRef Join to join The following table describes the mapping of joins to joins: 34 BusinessObjects Universe Builder Guide .

Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata 5 Join Join Left table name + right table name. Name and Business name Concat character is "_" Left column Right column Complex expression: For each simple expression the left and right columns are identified. Left attribute Right attribute BusinessObjects Universe Builder Guide 35 . Each simple expression maps to an attribute pair.

5 Exporting a universe to a XML file format How universe structures are mapped to DB2 Cube Views metadata 36 BusinessObjects Universe Builder Guide .

Building universes from Oracle Analytic Services 6 .

The Oracle OLAP Universe Builder wizard starts. it is automatically set up for SQL access to Oracle Analytic Workspaces. Add aliases to represent the dimension levels and hierarchies Joins the relational view to the dimension tables with regular joins and shortcut joins. The cubes available to the connection appear. You select a connection. The expressions of the joins are specific to this solution. Defines object expressions using the AggregateAware function to handle the Aggregation Navigation • • 38 BusinessObjects Universe Builder Guide . Creates a subclass for each hierarchy if a dimension has more than one hierarchy. and set view and universe creation options. Define aggregate navigation to resolve object incompatibility that results from the multi-hierarchy dimensions. 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 a universe generated from a OLAP cube? When you create a universe with the Oracle OLAP Universe Builder. Creates a class of objects for each Cube dimension and an object for each level of the dimension. Multi-hierarchy dimensions are supported in the view definition and in the universe.6 Building universes from Oracle Analytic Services Overview of how you create a universe from Oracle Analytic Services Overview of how you create a universe from Oracle Analytic Services You create a Oracle OLAP universe by clicking the Oracle OLAP icon or tab and selecting File > Metadata sources. 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. You select a cube.

Here is an example of limit_map parameter: DIMENSION GLOBAL_AW2.TEST!FK_CUSTOMER_FAMILYREL USING GLOB AL_AW2.FK_CUS TOMER_MARKET_SEGMENT.TEST!FK_TIME_FAMILYREL USING GLOB AL_AW2.FK_TIME_MONTH FROM GLOBAL_AW2.TEST!FK_CUSTOMER_INHIER LEVELREL null.TEST!FK_CUSTOMER_FAMILYREL USING GLOB AL_AW2.Building universes from Oracle Analytic Services Analyzing the relational view 6 • • Transforms objects that map real dimension members (Identifiers) to Details of objects that represent the member descriptions.TEST!FK_TIME_LEVELLIST LABEL GLOBAL_AW2.TEST!FK_CUSTOMER WITH HIERARCHY GLOBAL_AW2.TEST!FK_TIME_LEVELLIST LEVELREL FK_TIME_YEAR_DESC.TEST!FK_TIME_FAMILYREL USING GLOB AL_AW2.FK_CUSTOMER_SHIP_TO FROM GLOBAL_AW2.TEST!FK_TIME_LEVELREL DIMENSION GLOBAL_AW2.FK_CUSTOMER_TOTAL_MARKET.''.TEST!FK_CUSTOMER_LEVELLIST LEVELREL null.TEST!FK_CUSTOMER_PARENTREL (FK_CUSTOMER_HI ERLIST \''SHIPMENTS\'') INHIERARCHY GLOBAL_AW2.TEST DURATION session'.FK_CUS TOMER_MARKET_SEGMENT_D01.TEST!FK_TIME_LONG_DESCRIPTION ATTRIBUTE FK_TIME_LEVEL FROM GLOBAL_AW2.null.TEST!FK_CUSTOMER_LONG_DESCRIPTION HIERARCHY GLOBAL_AW2.FK_TIME_MONTH_DESC FROM GLOBAL_AW2.''.FK_CUSTOMER_TOTAL_MARKET_DESC.TEST!FK_TIME WITH HIERARCHY GLOBAL_AW2. FK_CUSTOMER_ACCOUNT.TEST!FK_CUSTOMER_INHIER BusinessObjects Universe Builder Guide 39 .null.null.TEST!FK_TIME_PARENTREL (FK_TIME_HIERLIST \''CALENDAR\'') LEVELREL FK_TIME_YEAR.FK_TIME_QUARTER_DE SC.TEST!FK_CUSTOMER_LEVELLIST LABEL GLOBAL_AW2.TEST!FK_CUSTOMER_PARENTREL (FK_CUSTOMER_HI ERLIST \''MARKET_SEGMENT\'') INHIERARCHY GLOBAL_AW2.null.'&LIM IT_MAP' LIMIT_MAP is a variable that stores the text of the limit_map parameter of OLAP_TABLE. The generated script has the following form: CREATE VIEW BOBJ_FK_UNITS_CUBE_VIEW AS SELECT * FROM TA BLE(OLAP_TABLE('GLOBAL_AW2.FK_CUSTOMER_SHIP_TO_DESC FROM GLOBAL_AW2. Creates measure objects Analyzing the relational view BusinessObjects Oracle OLAP Universe Builder generates views that call the OLAP_TABLE function to map the view columns to the hierarchies of the dimensions and measures of the Cube. FK_CUSTOMER_ACCOUNT_DESC. This text is generated by Oracle OLAP Universe Builder.FK_TIME_QUARTER.

FK_CUSTOMER_WAREHOUSE.null.null. based on the following schema: 40 BusinessObjects Universe Builder Guide .FK_CUSTOMER_ALL_CUSTOMERS.TEST!FK_CUSTOMER_FAMILYREL USING GLOB AL_AW2.6 Building universes from Oracle Analytic Services What are the shortcut joins in the universe used for? LEVELREL null. FK_CUSTOMER_REGION.null.FK_CUSTOMER_WAREHOUSE_DESC. For example. FK_CUSTOMER_REGION_DESC.FK_CUSTOMER_ALL_CUSTOMERS_DESC.TEST!FK_CUSTOMER_LONG_DESCRIPTION ATTRIBUTE FK_CUSTOMER_LEVEL FROM GLOBAL_AW2.TEST!FK_CUS TOMER_LEVELREL MEASURE FK_UNITS_CUBE_UNITS AS NUMBER FROM GLOB AL_AW2.TEST!FK_UNITS_CUBE_UNITS ROW2CELL OLAP_CALC What are the shortcut joins in the universe used for? Shortcut joins ensure that BusinessObjects generates SQL for each object combination rather than for each object.TEST!FK_CUSTOMER_FAMILYREL USING GLOB AL_AW2.TEST!FK_CUSTOMER_LEVELLIST LABEL GLOBAL_AW2.TEST!FK_CUSTOMER_LEVELLIST LEVELREL null.null FROM GLOBAL_AW2. BusinessObjects uses shortcut joins when it can omit tables from a query and take a 'shortcut' between two tables that are not directly linked in a hierarchy.null FROM GLOBAL_AW2.null.

as shown below: The join expression must include the expression that will restrict the rows returned from OLAPCUBE.time_level = 'MONTH' BusinessObjects Universe Builder Guide 41 .time_level = 'QTR' The full list of shortcut join expressions for the example time hierarchy is as follows: Joined tables Expression MONTH.Building universes from Oracle Analytic Services What are the shortcut joins in the universe used for? 6 if a shortcut join is defined between the QUARTER and OLAPCUBE tables. OLAPCUBE /* MONTH. The full join expression is therefore: /* QUARTER. BusinessObjects does not need to join through the MONTH table to retrieve revenue by quarter. this is OLAPCUBE. in the case of QUARTER.DUMMY */ OLAPCUBE. the expression must also reference the MONTH table.time_level = 'QTR'.DUMMY */ OLAPCUBE. Each table in the time hierarchy (except the lowest-level table) must be joined to OLAPCUBE. which should appear inside comments (because it plays no part in the actual join expression that you are interested in generating).time_level by a shortcut join. To ensure that Designer allows the join.

time_level = 'QTR' /* YEAR. 42 BusinessObjects Universe Builder Guide . the Oracle OLAP Universe Builder adds and configures universe objects as follows: View Oracle OLAP Universe Builder inserts the relational view as a table in the universe as well as the oracle table sys. OLAPCUBE /* QUARTER. MONTH.time_level = 'YEAR' /* TIME_ALL.dual is created for each level of the hierarchy. For example: if we have a dimension TIME with 4 levels (ALL. OLAPCUBE TIME_ALL.DUMMY */ OLAPCUBE. QUARTER) then create 4 aliases ALL. YEAR. a derived table is inserted with the definition of the view (select part with OLAP_TABLE function). OLAPCUBE How are Oracle OLAP structures mapped to universe components? To obtain and set up the expected universe. MONTH. YEAR.dual. The name of the alias is the level name.6 Building universes from Oracle Analytic Services How are Oracle OLAP structures mapped to universe components? Joined tables Expression QUARTER.DUMMY */ OLAPCUBE.time_level = 'ALL' YEAR.DUMMY */ OLAPCUBE. If you choose to use a derived table. Hierarchy tables For each hierarchy that is represented in the relational view. an alias of sys. QUARTER.

as many aliases are created as hierarchies. Month) All_Time and Month are shared by both hierarchies so we'll have two aliases for 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. See the section Multi-Hierarchy special case: (Multi-Hierarchy dimensions support) on page 46 for more information. For example: Dimension time has two hierarchies: H1 (All_Time. Year. This means that for shared levels. The join expression is: /* Alias1. then a different set of tables is created for each hierarchy even if some hierarchies share a same level.DUMMY=Alias2. The naming of such aliases is a concatenation of the level name and the hierarchy name.Building universes from Oracle Analytic Services How are Oracle OLAP structures mapped to universe components? 6 Multi-hierarchy tables Note: Multi-Hierarchy is a special case. Month) and H2 (All_Time.DUMMY */ 1=1 BusinessObjects Universe Builder Guide 43 . If a dimension has more than one hierarchy. Quarter.

DUMMY=Year.DUMMY */ MYVIEW.6 Building universes from Oracle Analytic Services How are Oracle OLAP structures mapped to universe components? where Alias1 represents a level and Alias2 represents its direct upper level in the hierarchy. Examples: MYVIEW is the view that represents the OLAP cube.Name archy dimensions support) on page 46 below. MYVIEW /* MONTH. MYVIEW /* QUARTER. Dimension name 44 BusinessObjects Universe Builder Guide .DUMMY */ VIEW.time_level = 'MONTH' QUARTER. MYVIEW /* TIME_ALL.DUMMY */ MYVIEW. MONTH Joined tables expression MONTH. Class and object properties are mapped as follows: Mapped from OLAP item.time_level = 'QTR' YEAR.DUMMY */ MYVIEW. levelColumn is the column representing the level within the view and level_value is the value of that column that matches the level name. the level values are: ALL. MYVIEW /* YEAR.DUMMY */ MYVIEW. QTR.time_level = 'ALL' Classes and Objects The Bridge must create a class for each OLAP dimension and an object for each level.levelColumn = 'level_value' Where Alias is the alias name. Universe item Property Class See also Multi-Hierarchy special case: (Multi-Hier.DUMMY */ 1=1 • Each table is joined to the view using a shortcut join type except for the lowest level where the join is regular. Example: /* Quarter. YEAR. the column that contains the levels is time_level...time_level = 'YEAR' TIME_ALL. The join expression defines a value to filter the rows returned from the view and is of the type: /* Alias.

Additional tables to ensure the use of appropriate joins: • Table of current view • • Dimension Name Select Tables View Highest level table for all dimensions Detail (optional) Dimension object created from the Description field that is related to the Parent dimension ID field. for example MYVIEW. The object YEAR is a detail of object YEAR_DESC. Current level name identified by the field name in the view.Building universes from Oracle Analytic Services How are Oracle OLAP structures mapped to universe components? 6 Universe item Property Mapped from OLAP item.YEAR.field is YEAR. Name Measure name in cube. For example. ID Note: All other proper. Descripties are the same as for tion field it YEAR_DEdimension above. View field.. SC. Measure BusinessObjects Universe Builder Guide 45 . Objects Levels and attributes..

Select (no drill through) View field. all the high level aliases. Multi-Hierarchy special case: (Multi-Hierarchy dimensions support) To support Multi-hierarchy dimensions of an Analytical Warehouse. the aggregate function is added to the Select expression.SALES Additional tables to ensure the use of appropriate joins: • View • Tables Highest level table for all dimensions Aggregation function None.. For example: • 46 BusinessObjects Universe Builder Guide . The naming of subclasses is a concatenation of the dimension name and the hierarchy name.. except the aliases of the current hierarchy. For each object corresponding to a level within a hierarchy.6 Building universes from Oracle Analytic Services How are Oracle OLAP structures mapped to universe components? Universe item Property Mapped from OLAP item. It references as comments. A class is created for the dimension and a subclass for each hierarchy. the following actions are carried out in the universe: • • A set of tables is created for each hierarchy as described in the section Multi-hierarchy tables on page 43. for example MYVIEW.

the table Year_H1 (from Hierarchy H1) is incompatible with objects from H2 hierarchy: And the table Year_H2 (from Hierarchy H2) is incompatible with objects from H1 hierarchy: BusinessObjects Universe Builder Guide 47 . This prevents the end user from using in a report objects representing levels that belong to different hierarchies.Building universes from Oracle Analytic Services How are Oracle OLAP structures mapped to universe components? 6 • Aggregate Navigation is set to make the objects of a subclass (Hierarchy) incompatible with the tables corresponding to another hierarchy. For example.

and Creating Oracle OLAP universe from generate a universe directly from this an existing view on page 52 view. 48 BusinessObjects Universe Builder Guide . You can create a view and save the view if you do not want to create a universe. and then select which structures are mapped to create the universe. Create a view only on page 51 You select an existing view.6 Building universes from Oracle Analytic Services How to create a Oracle OLAP universe How to create a Oracle OLAP universe You can create universes and views as using the following creation methods: Universe creation option Description Creating a view and generating a universe on page 49 You create a view. The view is available in a view list and can be used to create a universe at any time.

4. 9. 3. The Analytic Workspaces (AW) available in the connection are displayed. Click the Create View and generate Universe radio button. enter user name and password. Do this as follows: • Double click a data type or length value. • Select a data type from the drop down list box. 8. The Oracle OLAP Connection Wizard Welcome page appears. Edit hierarchy values if necessary. Expand a AW node to display the cubes available to the AW. Click the Cubes node. modify the data type and length values. BusinessObjects Universe Builder Guide 49 . Select a connection. then right click a cube and select Create Universe from the context menu. The Universe Builder Panel appears displaying the Analytic Workspace Cube cubes available to the connection 5. 6. These are described in the section How to create a Oracle OLAP universe on page 48. The wizard login page appears. Click the Oracle OLAP icon or tab. • Click Next. This page lists the hierarchy levels with data types and values. If required. then click Next. A status box appears showing the metadata loading status. A box showing data type and data length information appears. and generate a new universe. 7.Building universes from Oracle Analytic Services How to create a Oracle OLAP universe 6 Creating a view and generating a universe You generate an Oracle OLAP universe by first defining a view using Analytic Workspace Cube metadata. Three options are available. The Universe Builder wizard appears. The Hierarchy level page appears. and then click Finish. The View and universe options page appears. 2. Select File > Metadata Sources. Click Next. then you set universe creation options. 1. then click Next.

A derived table is a virtual table that exists only in the universe that references database structures.6 Building universes from Oracle Analytic Services How to create a Oracle OLAP universe 10. Use derived tables 50 BusinessObjects Universe Builder Guide . Type a name for the view. The View properties and universe options are as follows: Options Description View Name Name for the view. It is not created in the database. This is useful when the user does not have CREATE VIEW rights. Create Columns for Identifiers When selected existing Type and Replace existing database objects View structures are replaced in the database. You can edit this field. an extra column of type Raw(32) is created in the view Create Column for OLAP_EXPRESto enable the use of OLAP_EXSION PRESSION function in the universe. or if you do not want to accumulate views in the database. When selected. columns representing the dimension members (identifiers) are created. but is built by using a derived table to reference the cube structures. When selected the universe is not built from a view physically created in the database. When selected. and select view and universe options.

The SQL verification page appears. BusinessObjects Universe Builder Guide 51 . Verify the universe information. you select the Create View only radio button. The view is created in the target database. 11. You can connect to this view at any time to create a universe. 13. 12. Once you have create the view. When selected. Designer starts and opens to the newly generated universe. Verify the SQL for the view and click Next. and click Finish. To create a view only. Click Next. See the section Creating Oracle OLAP universe from an existing view on page 52for the procedure on using a view to create a universe. follow the same procedure in the section Creating a view and generating a universe on page 49Creating a view and generating a universe on page 49 but at the start of the Oracle OLAP Universe Builder wizard. you can then select the view at a later time and generate a universe. The universe information summary page appears. Create a view only You can create a view using Analytic Workspace Cube metadata. object IDs are transformed into detail objects in the generated universe. The saved view appears in a list of views.Building universes from Oracle Analytic Services How to create a Oracle OLAP universe 6 Options Description Transform object IDs to details Only active when the Create columns for identifiers option for views is selected.

Designer starts and opens to the newly generated universe. The Oracle OLAP Connection Wizard Welcome page appears. modify a column name or hierarchy level. 5.6 Building universes from Oracle Analytic Services How to create a Oracle OLAP universe Creating Oracle OLAP universe from an existing view You can generate a universe from an existing view. 2. • Select or type a name as appropriate. 12. Select File > Metadata Sources. 10. 11. It lists dimension. The Analytic Workspaces (AW) available in the connection are displayed. The Universe Builder wizard appears. Click Finish. 6. measures. A list of available views defined on the cube appears. Click the Generate Universe from View radio button. Click a view name in the list and click Next. 4. Expand a AW node to display the cubes available to the AW. 1. Right click a cube and select Create Universe from the context menu. A status box shows the progress of metadata being loaded from the selected cube. If required. Click Next. You select a view from the list and generate a universe. Click Next. 3. The Universe Builder Panel appears displaying the Analytic Workspace Cube cubes available to the connection. 9. The Universe Creation page appears. Select a connection and enter user name and password. Do this as follows: • Double click a column name or level value. and hierarchy levels defined in the view that can be used to create a universe. Click the Oracle OLAP icon or tab. 52 BusinessObjects Universe Builder Guide . The wizard login page appears. How to create a Oracle OLAP universe on page 48 for a description of each option. 8. Click Finish. Existing views appear in a list. 7. Three options are available. Click the Cubes node.

Get More Help A .

businessobjects. The library is updated regularly with new content as it becomes available. and download PDF versions. or contact us at: http://www. do full-text searches.businessobjects. in connectivities.com/services/training 54 BusinessObjects Universe Builder Guide . customized embedding technology. database design tools.com/support/ Looking for the best deployment solution for your company? Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project. and support forums. we can offer a training package to suit your learning needs and preferred learning style.com/documentation/product_guides/ Additional developer resources http://devlibrary.com/services/consulting/ Looking for training options? From traditional classroom learning to targeted e-learning seminars.com Online customer support The Business Objects Customer Support web site contains information about Customer Support programs and services.businessobjects. The online documentation library has the most up-to-date version of the Business Objects product documentation. read guides on line. It also has links to a wide range of technical information including knowledgebase articles. http://support. Expertise is available in relational and multidimensional databases. and more. downloads. Find more information on the Business Objects Education web site: http://www. contact your local sales office.businessobjects.businessobjects.A Get More Help Online documentation library Business Objects offers a full documentation set covering all products and their deployment. http://www. You can browse the library contents. For more information.

businessobjects.com/support/.Get More Help A Send us your feedback Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line. please contact our Customer Support experts. For information about Customer Support visit: http://www. BusinessObjects Universe Builder Guide 55 .com Note: If your issue concerns a Business Objects product and not the documentation.com. visit: http://www. and we will do our best to ensure that your suggestion is included in the next release of our documentation: mailto:documentation@businessobjects. Business Objects product information For information about the full range of Business Objects products.businessobjects.

A Get More Help 56 BusinessObjects Universe Builder Guide .

Index C classes and objects in Oracle Analytic Workspaces universe 42 O Oracle Analytic Workspaces class and object mapping 42 dimension joins 42 hierarchy tables 42 multi-hierarchy tables 42 use of shortcut joins in universe 40 view 42 D dimension joins use in Oracle Analytic Workspaces universe 42 S H hierarchy tables use in Oracle Analytic Workspaces universe 42 shortcut join use in Oracle Analytic Workspaces universe 40 V M multi-hierarchy tables use in Oracle Analytic Workspaces universe 42 view use in Oracle Analytic Workspaces universe 42 BusinessObjects Universe Builder Guide 57 .

Index 58 BusinessObjects Universe Builder Guide .

Sign up to vote on this title
UsefulNot useful