using sap netweaver business intelligence in universe designer

Using SAP NetWeaver BusinessIntelligence in Universe Designer

BusinessObjects XI 3.1 Service Pack 2

© 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects andits logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid Mart™,

Copyright

SAP BusinessObjects Data Insight™, SAP BusinessObjects Desktop Intelligence™,SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist Security™,SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks orregistered trademarks of Business Objects, an SAP company and/or affiliatedcompanies in the United States and/or other countries. SAP® is a registeredtrademark of SAP AG in Germany and/or other countries. All other namesmentioned herein may be trademarks of their respective owners.

2009-07-08

ContentsUsing SAP NetWeaver BW in Universe Designer 7Chapter 1

Prerequisites to using SAP NetWeaver BW in Universe Designer 9Chapter 2

SAP NetWeaver Business Warehouse (BW) data sources 11Chapter 3

SAP NetWeaver Business Warehouse (BW) InfoCubes as data sources..12SAP NetWeaver BW Queries as data sources..........................................13SAP NetWeaver BW Queries as recommended data sources..................14SAP NetWeaver BW multilingual universes..............................................15

About OLAP universes 17Chapter 4

What is an OLAP universe?.......................................................................18Which OLAP data sources can be used to create a universe? ................19

SAP NetWeaver Business Warehouse (BW) data sources.................19MSAS features supported for OLAP universes....................................24Essbase features supported for OLAP universes................................25

Defining connections to OLAP data sources 27Chapter 5

About connections to OLAP data sources.................................................28To start the New Connection wizard in Designer.......................................29To select database middleware for an OLAP connection..........................29To define login parameters for SAP NetWeaver BW connections.............30Defining login parameters for MSAS connections ....................................32Defining login parameters for Essbase connections.................................33To select source cube or query for OLAP connections..............................34

Using SAP NetWeaver Business Intelligence in Universe Designer 3

To define configuration parameters for OLAP connections.......................35Defining custom parameters for Essbase connections.............................37

Customizing OLAP universes 39Chapter 6

Creating OLAP Universes with additional parameters..............................40Defining OLAP options for your OLAP universe........................................41Defining objects in OLAP universes..........................................................44Designer features supported for OLAP universes.....................................44Database delegated projection function....................................................45Setting delegated measures for OLAP universes......................................48Setting aggregate projection for a measure..............................................48Calculated measures in OLAP universes..................................................49

To create a calculated measure in an OLAP universe.........................51About MDX functions for cube queries......................................................51XML syntax for filter and WHERE statements...........................................53Predefined conditions in OLAP universes.................................................54

To manually create predefined conditions in an OLAP universe..........54XML Syntax for predefined filter options..............................................56

Optional prompts in OLAP universes........................................................57To improve performance of certain queries on SAP NetWeaver BWuniverses...................................................................................................57

OLAP universe lifecycle management 59Chapter 7

About OLAP universe lifecycle management............................................60Overview: relationship between universe object status and OLAP objectstatus ........................................................................................................61To refresh an OLAP universe.....................................................................65Regenerating Level 00 for OLAP universes..............................................68Renaming level L00 to ALL........................................................................68Replacing OLAP universe level prefixes...................................................69Synchronizing the universe and the OLAP cube.......................................69

4 Using SAP NetWeaver Business Intelligence in Universe Designer

Contents

How dimensions are managed in OLAP universe updates.......................70When a dimension is unchanged.........................................................70When a dimension is updated (name, description) .............................71When a dimension is deleted ..............................................................73When a dimension is moved ...............................................................74When a hierachy or characteristic is created ......................................75When a dimension is new ...................................................................76

How hierarchies or characteristics are managed in OLAP universe updates...................................................................................................................76

When a hierarchy or characteristic is unchanged................................77When a characteristic business name or description is updated ........78When a characteristic's active hierarchy is changed ...........................80When a characteristic display attribute is changed to a navigationattribute................................................................................................81When a characteristic navigation attribute is changed to a display attribute.............................................................................................................82When a hierarchy or characteristic is deleted .....................................83When a hierarchy or characteristic is moved ......................................85When a hierarchy or characteristic is new...........................................86

How levels are managed in OLAP universe updates ...............................86When a level is unchanged .................................................................87When the name or description of a level is updated ...........................87When a level is deleted .......................................................................89When a level is moved ........................................................................90When a level is new ............................................................................90

How SAP variables are managed in OLAP universe updates ..................91When an SAP variable is unchanged...................................................91When the name or description of an SAP variable is updated ............92When an SAP variable is deleted ........................................................93When an SAP variable is new .............................................................95

How key figures or measures are managed in OLAP universe updates ...96


Contents

When a key figure or measure is unchanged ......................................96When the name, description, or data type of a key figure or measure isupdated ...............................................................................................97When a key figure or measure is deleted ............................................99When a key figure or measure is moved ...........................................100When a key figure or measure is new ...............................................101

How SAP key dates are managed in OLAP universe updates ...............101When a SAP key date is unchanged .................................................101When a SAP key date is deleted........................................................102When a SAP key date is new.............................................................103

How the different OLAP cubes are mapped to universes 105Chapter 8

How SAP NetWeaver BW objects are mapped and used in a universe...106How characteristics are mapped and used........................................108How key figures are mapped and used..............................................109How hierarchies are mapped and used.............................................109How variables are supported in universes.........................................110

How Essbase cubes are mapped to universe components.....................117How MSAS cubes are mapped to universe components........................119

More Information 121Appendix A

Index 125


Contents

Using SAP NetWeaver BWin Universe Designer

1

This guide is intended to help you create and manage OLAP universes basedon SAP NetWeaver BW data sources. The universes can be used in WebIntelligence, Dashboard and Analytics, Live Office, and Query as a WebService.

An OLAP universe is a Business Objects universe that has been generatedfrom an OLAP cube or query. The universe is created automatically from aselected connection to an OLAP data source.

You generate and maintain an OLAP universe in the following way:

• To generate an OLAP universe, first select the SAP NetWeaver BW datasource.

• Define a connection to the data source using the New Connection wizard,and select the connection for a new universe.

Designer generates the universe automatically. OLAP structures aremapped directly to classes, measures, dimensions, details, and filters inthe universe. The universe structure appears in the Universe pane.

• You can save and export the OLAP universe to the CMS.

• You can modify any of the OLAP universe components.

• The Update OLAP Universe wizard allows you manage the lifecycle ofthe OLAP universe. The wizard automatically refreshes the universestructure with changes made in the OLAP data source. The wizard candifferentiate generated objects from objects added or modified manually,allowing you to preserve the manual changes made in Designer.

Note:This guide sometimes refers to other OLAP data sources, or OLAP datasources in general. In these cases, the information applies equally to SAPNetWeaver BI data sources.

Related Topics• Prerequisites to using SAP NetWeaver BW in Universe Designer on

page 23• SAP NetWeaver Business Warehouse (BW) data sources on page 19• Designer features supported for OLAP universes on page 44• About OLAP universe lifecycle management on page 60• How SAP NetWeaver BW objects are mapped and used in a universe

on page 106


Using SAP NetWeaver BW in Universe Designer1

Prerequisites to using SAPNetWeaver BW in UniverseDesigner

2

When creating a universe from an SAP NetWeaver BW data source, youcan enable SSO (Single Sign On) for view time. SSO allows users to log onto BusinessObjects Enterprise with their SAP Credentials and leverage SAPAuthentication.

To enable SSO for OLAP Universes on top of SAP, you must install the SAPIntegration and configure the SAP Security Plug In.

Once SAP security integration is configured, you can use SAP credentialsto launch Designer. Create the BusinessObjects Enterprise user name byconcatenating the SAP System ID and SAP Client ID as defined whenconfiguring the security integration with the SAP user ID.

For more information, see the Business Objects XI Integration for SAPSolutions Installation Guide, and the Business Objects XI Integration for SAPSolutions User Guide.


Prerequisites to using SAP NetWeaver BW in Universe Designer2

SAP NetWeaver BusinessWarehouse (BW) datasources

3

When creating an OLAP universe based on a NetWeaver BW data source,you can build the universe based directly on an InfoCube/MultiCube, or basedon a BW Query enabled on top of any InfoProvider. An InfoProvider can be:

• an InfoCube• a MultiCube or Multi-InfoProvider• an Operational Data Store (ODS)• an InfoSet

Related Topics• SAP NetWeaver Business Warehouse (BW) InfoCubes as data sources

on page 20• SAP NetWeaver BW Queries as data sources on page 20• SAP NetWeaver BWQueries as recommended data sources on page 22

SAP NetWeaver Business Warehouse(BW) InfoCubes as data sources

The following types of InfoCubes are supported as data sources for buildingOLAP universes:

• Standard and Transactional InfoCubes: Data and metadata are physicallystored in the same SAP NetWeaver Business Warehouse (BW) system

• Remote InfoCube: Data is physically stored on a remote system

Note:While fully supported, building and deploying universes on remoteInfoCubes is not recommended for ad-hoc query-, reporting-, andanalysis-use scenarios. Such architecture is generally not expected tomeet query performance expectations with interactive queries.

• MultiCubes and Multi-InfoProviders

Note:Building and deploying a Business Objects universe on top of a MultiCubeor Multi-InfoProvider is identical to building and deploying a universe ontop of an InfoCube.

All the characteristics, hierarchies, key figures, including time and unit, inthe InfoCube are visible in the universe.


SAP NetWeaver Business Warehouse (BW) data sources3 SAP NetWeaver Business Warehouse (BW) InfoCubes as data sources

SAP NetWeaver BW Queries as datasources

SAP NetWeaver BW customers use BW Queries to access SAP BusinessExplorer front-ends.

Note:In order to serve as a data source and become available through the OLAPinterface to Business Objects universes, BW queries must be released forOLE DB for OLAP. You allow external access to the BW Query in the SAPNetWeaver BW Query Designer, on the Extended tab of the Query Propertiesdialog box.

All InfoObjects in the BW query selected as rows, columns, and freecharacteristics are visible in the universe. This includes characteristics,hierarchies, key figures, structures, and variables.

Both InfoSets and Operational Data Stores (ODS) can be exposed touniverses via BW Queries.

BW Queries based on an ODS

An ODS can be exposed to a universe via a BW Query.

ODS objects are often used to manage detailed transaction-level data beforeit is aggregated into InfoCubes. Including ODS objects in the NetWeaverdata store design is a way to minimize InfoCube size and improve loadingand querying performance.

Note:An ODS is usually a large, detailed relational structure. Accessing an ODSvia the OLAP BAPI interface does not deliver ideal query performance.Consider these alternatives to meet end-user expectations for fast reportdelivery:

• Create direct access to an ODS via BAPI calls• Access the ODS tables using direct SQL in Web Intelligence

BI Queries based on an InfoSet

An InfoSet can be exposed to a universe via a BW Query.


3SAP NetWeaver Business Warehouse (BW) data sourcesSAP NetWeaver BW Queries as data sources

InfoSets are sometimes defined in SAP NetWeaver BW to report masterdata.

Note:You can report master data by basing the universes on InfoCubes, eliminatingthe requirement to go through InfoSets and BW Queries. The key differencebetween the two approaches is that master data reported off InfoCubes limitsdata to valid transactions.

Related Topics• SAP NetWeaver BWQueries as recommended data sources on page 22

SAP NetWeaver BW Queries asrecommended data sources

BW Queries are recommended as data sources for generating BusinessObjects universes for the following reasons:

• Not all SAP NetWeaver BW metadata features can be retrieved on anInfoCube level, as summarized in the following table.

SAP OLAP Business ApplicationProgramming Interface (BAPI)support level

NetWeaver BW metadata feature

InfoCube/BW QueryCharacteristics (incl. Time and Unit)

InfoCube/BW QueryHierarchies

InfoCube/BW QueryBasic Key Figures

BW Query onlyNavigational Attributes

InfoCube/BW QueryDisplay Attributes

BW Query onlyCalculated Key Figures / Formulas

BW Query onlyRestricted Key Figures

BW Query onlyCustom Structures


SAP NetWeaver Business Warehouse (BW) data sources3 SAP NetWeaver BW Queries as recommended data sources



BW Query onlyVariables

• BW Queries offer a flexible extension to the data modeling environment.InfoCubes require more effort to change.

• BW Queries offer significant functionality to create customized datasources that meet end-user requirements.

Although BW Queries have advantages as data sources, you do not needa BW Query for every report, nor do you need a universe for every existingBW Query. To minimize maintenance costs, focus the implementation strategyon limiting the final number of BW Queries and universes required to meetall the ad-hoc query and reporting needs. Keep in mind the following pointsto reduce the number of universes needed:

• When Web Intelligence is the front-end tool, you are not restricted by theoutput format in the BW Query.

• There is no direct impact on performance when working with OLAPuniverses created from large BW Queries. OLAP universe objects notinserted in the Web Intelligence query have no direct impact on the queryperformance.

Note:Business Objects recommends having a few BW Queries – from a singleone to a handful of them – for every InfoCube or MultiCube that is in scopefor ad-hoc query and reporting. Then build a universe on top of each of theseBW Queries.

SAP NetWeaver BWmultilingualuniverses

With Web Intelligence, it is possible to leverage the multilingual capabilitiesof SAP NetWeaver BW. In order to implement a multilingual environment,the NetWeaver BW system must include multilingual metadata andmultilingual data.


3SAP NetWeaver Business Warehouse (BW) data sourcesSAP NetWeaver BW multilingual universes

You must create a universe for each language supported by the solution.The language in which the universe connection is created determines thelanguage in which the universe is generated.

The user's SAP authentication determines the language of the data returnedto the query. The user must log into InfoView using SAP authentication andspecify the desired language for results returned from the SAP server.

The result-set language is dependent on SAP’s Unicode support. If the SAPsystem does not contain the data in the desired language, the data is notavailable in Web Intelligence in this language. Web Intelligence reverts todisplaying technical names instead of descriptions when the descriptionsare not translated in NetWeaver BW.


SAP NetWeaver Business Warehouse (BW) data sources3 SAP NetWeaver BW multilingual universes

About OLAP universes

4

What is an OLAP universe?An OLAP universe is a Business Objects universe that has been generatedfrom an OLAP cube or query. The universe is created automatically from aselected connection to an OLAP data source.

Once the universe has been created, it can be exported to the CentralManagement Server (CMS) as any other universe. The universe is thenavailable to Web Intelligence users to run queries and create reports.

You generate and maintain an OLAP universe in the following way:

• To generate an OLAP universe, first select the OLAP data source.

• Define a connection to the data source using the New Connection wizard,and select the connection for a new universe.

Designer generates the universe automatically. OLAP structures aremapped directly to classes, measures, dimensions, details, and filters inthe universe. The universe structure appears in the Universe pane.

• You can save and export the OLAP universe to the CMS.

• You can modify any of the OLAP universe components.

• The Update OLAP Universe wizard allows you manage the lifecycle ofthe OLAP universe. The wizard automatically refreshes the universestructure with changes made in the OLAP data source. The wizard candifferentiate generated objects from objects added or modified manually,allowing you to preserve the manual changes made in Designer.

Related Topics• Which OLAP data sources can be used to create a universe? on page 19• About connections to OLAP data sources on page 28• Designer features supported for OLAP universes on page 44• About OLAP universe lifecycle management on page 60


About OLAP universes4 What is an OLAP universe?

Which OLAP data sources can be used tocreate a universe?

You can use Designer to create OLAP universes automatically from thefollowing OLAP data sources:

• SAP NetWeaver Business Warehouse (BW)• Microsoft Analysis Services (MSAS) 2000• Microsoft Analysis Services (MSAS) 2005• Hyperion Essbase

One universe is generated automatically from one cube or query. OLAPuniverses support a single cube in the universe.

Related Topics• SAP NetWeaver Business Warehouse (BW) data sources on page 19• How SAP NetWeaver BW objects are mapped and used in a universe

on page 106• MSAS features supported for OLAP universes on page 24• How MSAS cubes are mapped to universe components on page 119• Essbase features supported for OLAP universes on page 25• How Essbase cubes are mapped to universe components on page 117

SAP NetWeaver Business Warehouse (BW) datasources

When creating an OLAP universe based on a NetWeaver BW data source,you can build the universe based directly on an InfoCube/MultiCube, or basedon a BW Query enabled on top of any InfoProvider. An InfoProvider can be:

• an InfoCube• a MultiCube or Multi-InfoProvider• an Operational Data Store (ODS)• an InfoSet

Related Topics• SAP NetWeaver Business Warehouse (BW) InfoCubes as data sources

on page 20


4About OLAP universesWhich OLAP data sources can be used to create a universe?

• SAP NetWeaver BW Queries as data sources on page 20• SAP NetWeaver BWQueries as recommended data sources on page 22

SAP NetWeaver Business Warehouse (BW) InfoCubes as datasources

The following types of InfoCubes are supported as data sources for buildingOLAP universes:

• Standard and Transactional InfoCubes: Data and metadata are physicallystored in the same SAP NetWeaver Business Warehouse (BW) system

• Remote InfoCube: Data is physically stored on a remote system

Note:While fully supported, building and deploying universes on remoteInfoCubes is not recommended for ad-hoc query-, reporting-, andanalysis-use scenarios. Such architecture is generally not expected tomeet query performance expectations with interactive queries.

• MultiCubes and Multi-InfoProviders

Note:Building and deploying a Business Objects universe on top of a MultiCubeor Multi-InfoProvider is identical to building and deploying a universe ontop of an InfoCube.

All the characteristics, hierarchies, key figures, including time and unit, inthe InfoCube are visible in the universe.

SAP NetWeaver BW Queries as data sources

SAP NetWeaver BW customers use BW Queries to access SAP BusinessExplorer front-ends.

Note:In order to serve as a data source and become available through the OLAPinterface to Business Objects universes, BW queries must be released forOLE DB for OLAP. You allow external access to the BW Query in the SAPNetWeaver BW Query Designer, on the Extended tab of the Query Propertiesdialog box.


About OLAP universes4 Which OLAP data sources can be used to create a universe?

All InfoObjects in the BW query selected as rows, columns, and freecharacteristics are visible in the universe. This includes characteristics,hierarchies, key figures, structures, and variables.

Both InfoSets and Operational Data Stores (ODS) can be exposed touniverses via BW Queries.

BW Queries based on an ODS

An ODS can be exposed to a universe via a BW Query.

ODS objects are often used to manage detailed transaction-level data beforeit is aggregated into InfoCubes. Including ODS objects in the NetWeaverdata store design is a way to minimize InfoCube size and improve loadingand querying performance.

Note:An ODS is usually a large, detailed relational structure. Accessing an ODSvia the OLAP BAPI interface does not deliver ideal query performance.Consider these alternatives to meet end-user expectations for fast reportdelivery:

• Create direct access to an ODS via BAPI calls• Access the ODS tables using direct SQL in Web Intelligence

BI Queries based on an InfoSet

An InfoSet can be exposed to a universe via a BW Query.

InfoSets are sometimes defined in SAP NetWeaver BW to report masterdata.

Note:You can report master data by basing the universes on InfoCubes, eliminatingthe requirement to go through InfoSets and BW Queries. The key differencebetween the two approaches is that master data reported off InfoCubes limitsdata to valid transactions.

Related Topics• SAP NetWeaver BWQueries as recommended data sources on page 22



SAP NetWeaver BW Queries as recommended data sources

BW Queries are recommended as data sources for generating BusinessObjects universes for the following reasons:

• Not all SAP NetWeaver BW metadata features can be retrieved on anInfoCube level, as summarized in the following table.



InfoCube/BW QueryCharacteristics (incl. Time and Unit)

InfoCube/BW QueryHierarchies

InfoCube/BW QueryBasic Key Figures

BW Query onlyNavigational Attributes

InfoCube/BW QueryDisplay Attributes

BW Query onlyCalculated Key Figures / Formulas

BW Query onlyRestricted Key Figures

BW Query onlyCustom Structures

BW Query onlyVariables

• BW Queries offer a flexible extension to the data modeling environment.InfoCubes require more effort to change.

• BW Queries offer significant functionality to create customized datasources that meet end-user requirements.

Although BW Queries have advantages as data sources, you do not needa BW Query for every report, nor do you need a universe for every existingBW Query. To minimize maintenance costs, focus the implementation strategyon limiting the final number of BW Queries and universes required to meetall the ad-hoc query and reporting needs. Keep in mind the following pointsto reduce the number of universes needed:



• When Web Intelligence is the front-end tool, you are not restricted by theoutput format in the BW Query.

• There is no direct impact on performance when working with OLAPuniverses created from large BW Queries. OLAP universe objects notinserted in the Web Intelligence query have no direct impact on the queryperformance.

Note:Business Objects recommends having a few BW Queries – from a singleone to a handful of them – for every InfoCube or MultiCube that is in scopefor ad-hoc query and reporting. Then build a universe on top of each of theseBW Queries.

SAP NetWeaver BW multilingual universes

With Web Intelligence, it is possible to leverage the multilingual capabilitiesof SAP NetWeaver BW. In order to implement a multilingual environment,the NetWeaver BW system must include multilingual metadata andmultilingual data.

You must create a universe for each language supported by the solution.The language in which the universe connection is created determines thelanguage in which the universe is generated.

The user's SAP authentication determines the language of the data returnedto the query. The user must log into InfoView using SAP authentication andspecify the desired language for results returned from the SAP server.

The result-set language is dependent on SAP’s Unicode support. If the SAPsystem does not contain the data in the desired language, the data is notavailable in Web Intelligence in this language. Web Intelligence reverts todisplaying technical names instead of descriptions when the descriptionsare not translated in NetWeaver BW.

Prerequisites to using SAPNetWeaver BW in Universe Designer

When creating a universe from an SAP NetWeaver BW data source, youcan enable SSO (Single Sign On) for view time. SSO allows users to log onto BusinessObjects Enterprise with their SAP Credentials and leverage SAPAuthentication.



To enable SSO for OLAP Universes on top of SAP, you must install the SAPIntegration and configure the SAP Security Plug In.

Once SAP security integration is configured, you can use SAP credentialsto launch Designer. Create the BusinessObjects Enterprise user name byconcatenating the SAP System ID and SAP Client ID as defined whenconfiguring the security integration with the SAP user ID.

For more information, see the Business Objects XI Integration for SAPSolutions Installation Guide, and the Business Objects XI Integration for SAPSolutions User Guide.

MSAS features supported for OLAP universes

The following table summarises the support level for MSAS features foruniverses generated from an MSAS data source.

OLAP universe support levelMSAS metadata feature

SupportedCube

SupportedLocal cube

SupportedVirtual cube (MSAS 2000)

SupportedPerspective (MSAS 2005)

SupportedDimensions

SupportedVirtual dimensions (MSAS 2000)

SupportedHierarchies

SupportedLevels

SupportedLevel Property

SupportedAttributes (MSAS 2005)

SupportedMeasures

SupportedMeasure group (MSAS 2005)

SupportedCalculated measures

SupportedDisplay folder (MSAS 2005)

Not supportedKPI (MSAS 2005)



OLAP universe support levelMSAS metadata feature

Not supportedAction

Must define custom sort order in Web Intelli-gence

Database sort order

Not supportedWrite back

Related Topics• How MSAS cubes are mapped to universe components on page 119

Essbase features supported for OLAP universes

The following table summarizes the support level for Essbase features foruniverses generated from a Hyperion Essbase data source.

OLAP universe support levelEssbase metadata feature

SupportedBlock storage mode

SupportedAggregate storage mode

Not supportedHybrid mode

SupportedAlias tables

SupportedDimensions

SupportedAttribute dimensions

SupportedDuplicate members

SupportedGenerations

Not supportedLevels

Not supportedUser Define Attributes (UDA)

Not supportedDynamic Time Series (DTS)

Not supportedEssbase Integration Services (EIS)Drill-through

Not supportedSubstitution variables

Not supportedLinked partitions



OLAP universe support levelEssbase metadata feature

Not supportedLinked Reporting Objects (LRO)

Must define custom sort order in WebIntelligence

Database sort order

Not supportedWrite back

Related Topics• How Essbase cubes are mapped to universe components on page 117



Defining connections toOLAP data sources

5

About connections to OLAP data sourcesTo generate an OLAP universe, you must first define a connection to theOLAP data source. Define one connection for each cube or query that youwant to use to create a universe.

Use the New Connection wizard to define the connection. The wizard leadsyou through the following steps in creating a connection:

• Starting the New Connection wizard in Designer.• Naming the connection and selecting the database middleware.• Defining the login parameters for the connection. These parameters vary

depending on the database middleware that you selected.• Selecting the cube or query to use to create the universe.• Defining the connection life-time.• Defining custom parameters. These parameters vary depending on the

database middleware that you selected.

Defining a connection is the first step in creating an OLAP universe. Onceyou have defined the connection, Designer generates the universeautomatically.

Note:If you define a connection from the connections list on the Tools menu, youmust create the universe as a separate step.

Related Topics• To start the New Connection wizard in Designer on page 29• To select database middleware for an OLAP connection on page 29• To define login parameters for SAP NetWeaver BW connections on

page 30• Defining login parameters for MSAS connections on page 32• Defining login parameters for Essbase connections on page 33• To select source cube or query for OLAP connections on page 34• To define configuration parameters for OLAP connections on page 35• Defining custom parameters for Essbase connections on page 37


Defining connections to OLAP data sources5 About connections to OLAP data sources

To start the New Connection wizard inDesigner

To start the New Connection wizard in Universe Designer, do one of thefollowing:

Do...Start from...

Click the New Universe icon, then click New... on the "Defi-nition" page of the "Universe Parameters" box.

New Universeicon

From an empty Designer session, select File > Parameters,then click New... on the "Definition" page of the "UniverseParameters" box.

File menu

If the Quick Design wizard is enabled, it starts automatical-ly when you start Designer. Click New... in step one of theQuick Design wizard.

Note:If the wizard has been disabled, select File > New. If thewizard does not start when you select File > New, selectTools > Options. On the "General" page of the "Options"dialog box, select the File/New starts Quick Design wizardcheck box. Click OK and select File > New.

Quick Designwizard

Select Tools > Connections. Click Add... in the "WizardConnection" dialog box.

Tools menu

To select database middleware for anOLAP connection

On the "Database Middleware Selection" page of the New Connection wizard,enter a name for the connection, select the type and the database middlewarefor the connection.


5Defining connections to OLAP data sourcesTo start the New Connection wizard in Designer

DescriptionDatabase MiddlewareSelection parameter

Select Secured for controlled access to the con-nection (recommended).

Select Shared to allow uncontrolled access to theconnection to all users.

Select Personal to restrict access to the universecreator. You can use personal connections to ac-cess personal data on a local machine only.

Connection Type

Enter a name for the connection.Connection Name

The Filter Stored Procedures Network Layers pa-rameter is not used for OLAP connections.

Filter Stored Proce-dures Network Layers

The page lists the databases and middleware thatcorrespond to your data access driver key.

Expand the node for your target database to showthe supported middleware for that database.

Expand the middleware node to show the BusinessObjects data access driver for the OLAP middle-ware.

Select the data access driver.

List of available data ac-cess drivers.

To define login parameters for SAPNetWeaver BW connections

On the "Login Parameters" page of the New Connection wizard, specify thelogin details for connecting to the SAP NetWeaver BW database.


Defining connections to OLAP data sources5 To define login parameters for SAP NetWeaver BW connections

DescriptionLogin parameter

Select Use Single Sign On when refreshingreports at view time to allow the user to benefitfrom SAP SSO.

SelectUse specified username and passwordto require the user to enter login information whenusing the connection.

Select Use BusinessObjects credential map-ping to use the user's BusinessObjects Enter-prise login credentials for the connection.

Authentication mode

Enter the SAP User logon.User name

Enter the SAP User password.Password

Enter the SAP client number (required).Client

Enter the connection language, for example ENfor English (required).

Note:The connection language determines the languagein which the universe is generated.

Language

Select Application server to connect directly tothe SAP server without using load balancing.

SelectMessage server to benefit from SAP loadbalancing capabilities.

Login mode

Select or enter the name or IP address of theSAP application server (required for Applicationserver login mode).

Application Server


5Defining connections to OLAP data sourcesTo define login parameters for SAP NetWeaver BW connections


Enter the system number, for example 00 (re-quired for Application server login mode) .System Number

Enter the System ID , Logon Group, and Mes-sage Server parameters (required for Messageserver login mode).

System ID

Logon Group

Message Server

Defining login parameters for MSASconnections

On the "Login Parameters" page of the New Connection wizard, specify thelogin details for connecting to the MSAS database.


Select Use Single Sign On when refreshingreports at view time to allow the user to benefitfrom MSAS 2005 SSO.

SelectUse specified username and passwordto require the user to enter login information whenusing the connection.


Authentication mode

Enter the MSAS server logon user name.User name


Defining connections to OLAP data sources5 Defining login parameters for MSAS connections


Enter the MSAS server logon password.Password

Enter the server name for the MSAS data source,or enter the full path file name of an MSAS cubefile.

Enter the full path file name between doublequotes, for example:

"Z:\All cubes\test.cub"

Note:If the cube file is located on a machine different fromthe BusinessObjects Enterprise machine, the twomachines must have a shared connection. You mustcreate the connection to a cube file directly on theBusinessObjects Enterprise machine.

Server

Defining login parameters for Essbaseconnections

On the "Login Parameters" page of the New Connection wizard, specify thelogin details for connecting to the Essbase database.


5Defining connections to OLAP data sourcesDefining login parameters for Essbase connections


SelectUse specified username and passwordto require the user to enter login information whenusing the connection. To synchronize Essbasesecurity with BusinessObjects Enterprise, enterthe Essbase DBuser and DBpass forUser nameand Password.


Note:TheUse Single Sign Onwhen refreshing reportsat view time option is not supported for Essbaseconnections.

Authentication mode

Enter the Essbase DBuser.User name

Enter the Essbase DBpass.Password

Enter the Essbase server name.Server

To select source cube or query for OLAPconnections

The cube browser shows the OLAP cubes available to the target server.

Expand the cube nodes to display the cubes and queries available. Thebrowser has the following tools to help you search:


Defining connections to OLAP data sources5 To select source cube or query for OLAP connections

DescriptionCube browser tool

A folder that holds links to cubes that you selectfor quick access. To add a cube to Favorites, rightclick a cube in the OLAP cube browser and selectAdd to Favorites from the contextual menu.

Favorites

Searches the names of available cubes or queriesfor a text string. Type a string in the text box andclick Search. Each found instance is highlighted.Click Search to continue searching.

Search

For SAP NetWeaver BW data sources, the In-foCubes and MultiCubes are grouped in a foldercalled $INFOCUBE.

$INFOCUBE folder

Select the cube or query to use to create the universe.

To define configuration parameters forOLAP connections

On the "Configuration Parameters" page of the New Connection wizard,define the connection parameters to manage the connection life-time. Youcan accept the default settings when you create the connection and modifythem later.


5Defining connections to OLAP data sourcesTo define configuration parameters for OLAP connections

DescriptionConfiguration pa-rameter

You define the life-time with the Connection PoolMode and Pool timeout parameters.

By default, the Connection Pool Mode is set to Keepthe connection alive for, with a default Pool timeoutof 10 minutes.

Note:Business Objects recommends you keep the defaultconnection life-time. The universe building processslows significantly if theConnection Pool Mode is setto disconnect after each transaction. Disconnectingafter each transaction also impacts key end-userworkflows such as working with hierarchical list of val-ues.

The connection life-time can have a significant impactwhen working with SAP NetWeaver BW.

However, connection life-time can also impact updatingexisting universes with changes in the BW Query. Thisis because the OLAP BAPI interface builds a metadatacache on the client side every time a connection toSAP NetWeaver BW is established. This cache is onlyemptied when the connection closes.

To minimize the risk of metadata cache being desyn-chronized with SAP BW Query updates, you canchange the Pool timeout from 10 minutes to 1 minute.

When working in parallel editing BW Queries andmapping new universes to these queries, it is recom-mended that you close Designer (so that universeconnections are also closed and the metadata cacheis emptied) before building any new universes to takeinto account changes that were just made on the BWQuery side.

Connection PoolMode

Pool timeout


Defining connections to OLAP data sources5 To define configuration parameters for OLAP connections

DescriptionConfiguration pa-rameter

The Array fetch size, Array bind size, and Login time-out parameters are not used for OLAP connections.

Array fetch size

Array bind size

Login timeout

Defining custom parameters for Essbaseconnections

On the "Custom Parameters" page of the New Connection wizard, specifythe alias table and select the dimension to be used as the Measure dimensionwhen generating the universe.


To generate the universe on an alias table otherthan the default, select the alias table from thelist.

Alias table

Select the dimension to use as the Measure di-mension. Designer generates the members ofthe dimension you select as measures in theuniverse.

Measure dimension


5Defining connections to OLAP data sourcesDefining custom parameters for Essbase connections


Defining connections to OLAP data sources5 Defining custom parameters for Essbase connections

Customizing OLAPuniverses

6

CreatingOLAPUniverseswith additionalparameters

This feature applies to OLAP universes only and allows you to defineadditional metadata parameters when you create an OLAP universe withMSAS, SAP NetWeaver Business Warehouse (BW), or Essbase.

When you create an OLAP universe you can define the following parameters:


Customizing OLAP universes6 Creating OLAP Universes with additional parameters

DescriptionGeneric OLAPop-tions

You can set the application to generate the technical nameas a detail object of the dimensions in the universe. Whenthe universe is generated, this creates detail objects thatpoint to the technical names.

Generate technicalnames as details

DescriptionSAP OLAP options

You can set the application to set the aggregationfunction of measures to database delegated.

Set measures aggre-gation to delegated

Universe level prefixes indicate the level in the hierarchyof an object. Level L00 is the top or root level, L01 isthe next level down. In the "New Universe Wizard", youcan replace OLAP universe level prefixes with a differentprefix. The level numbering is retained, but the prefix 'L'can be replaced by Level, for example. Type your ownprefix in the New prefix field. This prefix is prependedto all levels throughout the OLAP universe.

Replace prefixes L00,L01,

This option is disabled ifGenerate level 00 is set toNo.You can rename the top level (root level) L00 to All thenext time the universe is generated.

Rename level 00 toAll

This option only applies to SAP Characteristics. Youcan disactivate this option for Characteristics and hier-archies. Level 00 is always generated for hierarchyvariables. You can regenerate the Level numbers (L00,L01, L02...) when you generate or update a universe.The level numbers are appended to the level names(e.g. "Monthly Sales_L01"). This is useful for Web Intel-ligence reports, where the All level is used to aggregateresults for a query. This avoids having to create the ag-gregate field in the Web Intelligence report.

Generate level 00

Defining OLAP options for your OLAPuniverse

Use the OLAP options to define how specific universe metadata is generated


6Customizing OLAP universesDefining OLAP options for your OLAP universe

from an OLAP source. You can select OLAP options from the "OLAP" pageof the "Options" dialog box (Tools > Options > OLAP). All content of theOLAP source is extracted and created in the universe depending on selectedoptions. You can select the following OLAP universe generation options:


Customizing OLAP universes6 Defining OLAP options for your OLAP universe

DescriptionGeneric OLAPop-tions

You can set the application to generate the technicalname of the universe as a property. When the universeis generated, this creates an object that points to thetechnical name.



You can set the application to generate delegatedmeasures for measures that use the aggregation func-tion. When the universe is generated, any measuresusing the aggregation function are set to database del-egated.


Universe level prefixes indicate the level in the hier-archy of an object. Level L00 is the top or root level,L01 is the next level down. In the "New UniverseWizard", you can replace OLAP universe level prefix-es with a different prefix. The level numbering is re-tained, but the prefix 'L' can be replaced by Level, forexample. Type your own prefix in the New prefixfield. This prefix is prepended to all levels throughoutthe OLAP universe.


This option is disabled if Generate level 00 is set to No.You can rename the top level (root level) L00 to ALLwhen the universe is next generated. This is useful forWeb Intelligence reports, where the All level is used toaggregate results for a query. This avoids having tocreate the aggregate field in the Web Intelligence report.


This option only applies to SAP Characteristics. Youcan disactivate this option for Characteristics only. Level00 is always generated for hierarchies and hierarchyvariables.

You can regenerate the Level numbers (L00, L01,L02...) when you generate or update a universe. Thelevel numbers are appended to the level names (e.g."Monthly Sales_L01")

Generate level 00


6Customizing OLAP universesDefining objects in OLAP universes

Defining objects in OLAP universesYou can use the SQL editor to define a Select statement or a Where clausefor an object, and to insert MDX operators and functions for OLAP universeobjects. The options and functions available in the SQL editor depend onthe underlying database.

Designer features supported for OLAPuniverses

OLAP universes are created automatically. Once you have created the OLAPuniverse, you can modify any of the universe components.

These Designer features are supported for generated OLAP universes:

• Hide, duplicate, and rename classes and objects (dimension, detail, andmeasure)

• Insert new classes and objects (dimension, detail, and measure)• Edit an object's format• Edit an object's data type• Define primary and foreign keys• Parse dimension, detail, and measure object MDX syntaxes• Check universe integrity• Edit hierarchies• Create cascading list of values• Define a delegate search for a list of values, allowing users to limit loading

of the list of values at query run time• Use default values for variables• Define measures with database delegated projection function (smart

measures)• Refresh the universe structure

In addition, the following features are available uniquely for OLAP universes:

• Create calculated measures (SAP Netweaver BW and MSAS only)• Create pre-defined conditions• Define optional prompts

All objects based on OLAP universes are generated with index awareness.If there are duplicate values in a hierarchy for an object, index awareness


Customizing OLAP universes6 Designer features supported for OLAP universes

eliminates inconsistency in the list of values. For example, say that Parisoccurs twice in the hierarchy, once under the parent France and once underthe parent Texas. If the user selects Paris under France, only rows for Paris,France are returned.

The following Designer features are not supported for OLAP universes:

• You cannot set row-level security authorizations in an OLAP universe.• You cannot edit a list of values in an OLAP universe.• You cannot view and edit the universe entity-relationship schema as no

schema is generated for OLAP universes.

Related Topics• Calculated measures in OLAP universes on page 49• Predefined conditions in OLAP universes on page 54• Optional prompts in OLAP universes on page 57• Database delegated projection function on page 45

Database delegated projection functionIn a universe, any measure can hold a projection function (Sum, Min, Max,Count, and Avg). The projection function is used to aggregate the measurelocally in Web Intelligence when the number of dimensions displayed in areport is smaller than the number of dimensions in the query result set.

Non-additive measures, such as ratio, average, and weight, can only beshown at the same aggregation level as the query result set. Therefore,non-additive measures generally have their projection function set to Nonein the universe.

The projection function Database delegated allows you to delegate theaggregation of a non-additive measure to the database server. These arecalled smart measures in Web Intelligence. A smart measure has its projectionfunction set to Database delegated on the properties page of the objectproperties.

Note:For OLAP universes based on MSAS and Essbase data sources, allmeasures are created in the universe with the projection function set toDatabase delegated by default.


6Customizing OLAP universesDatabase delegated projection function

Note:Please be aware of the following limitation when using a smart measurebased on a measure that has aggregate aware set: It is stronglyrecommended to ensure that the aggregate tables used in the measuredefinition have consistent data (the aggregate values are accurate regardingdetail values) otherwise the smart measures can produce inconsistent data.For example, if a year aggregate table and a day aggregate table are usedfor a smart measure, the year aggregate table is consistent with the dayaggregate table for complete years, but for the current year, the year tablecan be empty while the day table is accurate on a daily basis. In this case,a report that uses smart measures based on the current year and daily tablescan give incoherent results.

Example: Smart measure

In this example, a query contains two dimensions: Country and Region,and three measures: Order Amount, Delivered Amount, and % of DeliveredAmount.

% DeliveredOrder QuantityAmount Deliv-ered

L01 Region

99.997497,332,680497,318,880Reg1

99.998199,466,536199,463,776Reg2

99.997198,933,072198,927,552Reg3

299.992Sum:

The sum for % Delivered is incorrect because it is a summation of the %Delivered column.

If this measure has a projection function set to Database delegated in theuniverse, when the user refreshes the report, Web Intelligence connectsto the database to calculate the correct value.


Customizing OLAP universes6 Database delegated projection function

% DeliveredOrder QuantityAmount Deliv-ered

L01 Region

99.997497,332,680497,318,880Reg1

99.998199,466,536199,463,776Reg2

99.997198,933,072198,927,552Reg3

299.992Sum:

99.997Total:

Note:

The some functions such as the ratio function (Average) must be used withcaution. When calculating an average from a column, the behavior of thisfunction can be unexpected when it is not configured correctly.

For example, the SQL function sum(Shop_facts.Margin)/sum(Shop.facts.Quantity_sold) can have unexpected results.When incorrectly configured, it will calculate the average for each cell andreturn the sum of those averages. To correct this behavior, theparametrization of the function must be performed as follows:

1. Go to the Edit Properties option for the function.2. For the option Choose how this measure will be projected when

aggregated, select the FunctionDb delegated from the Function dropdownlist.

3. Save your changes.

Related Topics• Setting aggregate projection for a measure on page 48


6Customizing OLAP universesDatabase delegated projection function

Setting delegated measures for OLAPuniverses

You can set the application to generate delegated measures for measuresthat use the aggregation function. When the universe is generated, anymeasures using the aggregation function are set to database delegated...

Related Topics• Replacing OLAP universe level prefixes on page 69• Regenerating Level 00 for OLAP universes on page 68• Renaming level L00 to ALL on page 68

Setting aggregate projection for ameasureWhen you create a measure you must specify the way the aggregate functionwill be projected onto a report.

Returned values for a measure object are aggregated at two levels of thequery process:

• Query level. Data is aggregated using the inferred SELECT statement.

• Microcube to block level. When data is projected from the microcube tothe block in a report. This projection function of measures allows localaggregation in the microcube.

Note:A microcube is a conceptual way to present the data returned by a querybefore it is projected onto a report. It represents the returned values held inmemory by a Business Objects reporting product. The block level is the 2dimensional report that a user creates with the returned data. A user canchoose to use all, or only some of the data held in the microcube to createa report. A user can also do aggregate functions on the returned values inthe microcube (local aggregation) to create new values on a report.

The two levels of aggregation fit into the query process as follows:

• User creates a query in Web Intelligence.

• Web Intelligence infers the SQL from the query and sends a SELECTstatement to the target database.


Customizing OLAP universes6 Setting delegated measures for OLAP universes

• The data is returned to the microcube. This is the first aggregation level.

• The microcube projects the aggregated data onto the report. Data is splitout in the Query pane requiring aggregation to lower levels. This is thesecond aggregation level.

When you initially make a query the result set of the Select statement isstored in the microcube, and all data then held in the microcube is projectedinto a block. As data is projected from the lowest level held in the microcubeno projection aggregation is taking place.

However, when you use the Query pane to project only partial data from themicrocube, aggregation is required to show measure values at a higher level.

For example, in the previous example, if you do not project the year datainto the block, the three rows related to Year need to be reduced to one rowto show the overall Sales Revenue for that resort, so a sum aggregation isused.

You set projection aggregation on the "Properties" page of the "EditProperties" sheet for a measure (right-click Object > Object Properties >Properties).

Projection aggregation is different from SELECT aggregation.

Related Topics• Database delegated projection function on page 45

Calculated measures in OLAP universesYou can create calculated measures in the universe to restrict queries.Calculated measures in OLAP universes are like definitions on the measureobject in non-OLAP universes, except that you define the restriction usingMDX functions embedded in XML tags rather than using SQL.

Calculated measures are available for these OLAP data sources:

• SAP NetWeaver Business Warehouse (BW)• MSAS 2000 and 2005

Calculated measures can be used in filters or the where clause.


6Customizing OLAP universesCalculated measures in OLAP universes

Syntax for calculated measure expressions

The syntax for a calculated measure consists of calculations embedded inthe tags <EXPRESSION></EXPRESSION>.

Designer functions are allowed in calculated measure expressions, such as:

• @Select• @Prompt• @Variable• @Where

Note:Expressions for calculated measures cannot include the @Aggregate_Awarefunction.

Constants are allowed in the expression, for example "10" or "ABC".

Calculated measures can reference any OLAP metadata:

• measures• dimensions• dimension levels• MDX expressions

The check integrity validates the XML syntax and any of the Designerfunctions.

Recommendations for calculated measure expressions

Use @Select (Measure name) rather than the measure definition for thefollowing reasons:

• @Select is resolved at query time.• Calculated measures can reference other calculated measures if they

are inside a @Select function.• The validity of objects inside the @Select function is checked.

Generate and set the index awareness for each object definition.

Use a reference to an object or detail whose definition refers to the TechnicalName or Unique Name of the level or attribute.


Customizing OLAP universes6 Calculated measures in OLAP universes

Example: Calculated measure expression

<EXPRESSION>@Select(Key Figures\Order Amount)*@Select(KeyFigures\Order Quantity)</EXPRESSION>

Related Topics• To create a calculated measure in an OLAP universe on page 51

To create a calculated measure in an OLAP universe

To create a calculated measure in an OLAP universe:

1. In Designer, open an OLAP universe.2. Insert a new measure object in the universe.3. In the Where: box, enter or paste the object definition as an XML/MDX

expression.4. Click Parse to review the object definition and fix any errors.5. Click OK to save the object definition.6. Select Tools > Check Integrity.

The integrity check validates the XML syntax and any Designer@FUNCTIONS.

Related Topics• Calculated measures in OLAP universes on page 49

About MDX functions for cube queriesUse the MDX editor to define your cube queries.

When adding a new object or a predefined filter to an OLAP universe, thereis a list of supported MDX expressions corresponding to the specific datasource connection.

A library of available expressions is stored in the .prm connection file. Whenyou open the Edit Properties pane for an object and opend the Edit Selectpane for the query, the available expressions are displayed in the Functionspane. To insert the expression in the SELECT or WHERE statement, click


6Customizing OLAP universesAbout MDX functions for cube queries

in the position in the expression where you want to insert the expression anddouble-click on the appropriate expression.

OLAP Universe MDX Dictionary - List of Functions (PRM file)

When adding a new object or a predefined filter to an OLAP universe, anexplicit list of MDX functions (mainly member functions) and operators ismade available in the object and filter editors for the appropriate OLAPconnection (SAP or MSAS) that you can use in the expression. For adescription of how to set the connectivity for SAP or mySQL (sap.prm,sqlsrv_as.prm), refer to the Data Access Guide. The available functions andoperators depend on the connection type of the universe. This list of functionsis provided by the PRM file for each connectivity. It does not provide thewhole list of supported functions, only the most frequently used functions.

The following MDX operators are available for queries.

• Equal• Not equal• In List• Not In List• Greater• Greater Or Equal• Less• Less Or Equal• Between• Not Between• Like• Not Like

The list below shows examples of some of the available MDX folder functionswhen editing a condition. The available functions depend on the underlyingdatabase.

• Set functions (ADDCALCULATEDMEMBERS, ALLMEMBERS ...)• Statistical/Numeric functions (AGGREGATE, AVG ...)• Navigation/Member functions (ANCESTOR, ASCENDANTS...)• Metadata functions (AXIS, HIERARCHY...)


Customizing OLAP universes6 About MDX functions for cube queries

XML syntax for filter and WHEREstatements

This section describes the XML syntax for defining the WHERE clause orfilter statements in your OLAP universe. You must add the FILTER or FILTEREXPRESSION tags manually, and then enter your expression between thetags either manually or with Designer's MDX editor.• Use <FILTER= "your_object_definition"> when using a single object

definition. Enter your object definition inside the double quotes.• Use <FILTER EXPRESSION= "yourcomplexMDX_expression"> when

using a complex MDX expression containing one or more objects. Enteryour expression inside the double quotes.

The syntax for a single filter object is as follows:

<FILTER = “your_object_definition”><CONDITION OPERATORCONDITION="yourOperator"><CONSTANT VALUE="your_Value"/></CONDITION></FILTER>

Where:• yourMDX_expression is the single object definition, enclosed in double

quotes.• CONSTANTVALUE is either CONSTANT CAPTION or CONSTANT TECH_NAME

• yourOperator is the filter expression operator (equals, inlist...). Whenthe InIist operator is used, you must insert a CONSTANT CAPTION orCONSTANT TECH_NAME element for each item in the list.

• your_Value is the defined filter value when CONSTANT CAPTION is used,or the object identifier if CONSTANT TECH_NAME is used.

The syntax for a single filter object using the InList operator, where threecountries are listed, is as follows:

<FILTER= "your_object_definition "><CONDITION OPERATORCONDITION="InList"><CONSTANT CAPTION="England"/><CONSTANT CAPTION="France"/><CONSTANT CAPTION="Germany"/></CONDITION></FILTER>

The syntax for a complex filter expression and the TECH_NAME for thefiltered value is as follows:


6Customizing OLAP universesXML syntax for filter and WHERE statements

<FILTER EXPRESSION="yourComplex_MDX_Expression"><CONDITION OPERATORCONDITION="Equal"><CONSTANT TECH_NAME="1"/></CONDITION></FILTER>

Example: Filter with a calculated member in the filter expression

<FILTER EXPRESSION="IIF([0CALYEAR].CurrentMember > “2000”,1,0)"><CONDITION OPERATORCONDITION="Equal"><CONSTANT CAPTION="1"/></CONDITION></FILTER>

Predefined conditions inOLAPuniversesPredefined conditions in OLAP universes are like conditions in non-OLAPuniverses except that you define the WHERE clause using XML rather thanSQL.

To manually create predefined conditions in anOLAP universe

To create a predefined condition:

1. In Designer, open an OLAP universe and click the conditions radio buttonat the bottom of the Universe pane.The conditions view of the Universe pane appears. It contains a tree viewof the classes in the universe.

2. Right click a class and select Condition... from the contextual menu.3. In the Where: box, edit the XML template filter.

The template filter has the format:

<FILTER "[Level Object definition]"><CONDITION OPERATORCONDITION="Operator">

<CONSTANT Level Attribute="Value"/</CONDITION>

</FILTER>

Replace the elements in the template as follows:


Customizing OLAP universes6 Predefined conditions in OLAP universes

Possible Values:Template ele-ment:

Enter the dimension level or measure implied in thefilter. Enter the object definition not the object name.

Level Objectdefinition

Enter one of:• Equal• Not Equal• Greater than• Less than• Greater than or equal to• Less than or equal to• Between• Not Between• In List• Not in List• Matches pattern• Different from pattern

Operator

Enter one of:• NAME• CAPTION• TECH_NAME• DESCRIPTION

Level Attribute

Enter the value or a prompt. Define one value perCONSTANT tag.

Value

An example of an edited predefined condition:

<FILTER KEY="[0D_DIV].[LEVEL01]"><CONDITION OPERATORCONDITION="InList">

<CONSTANT CAPTION="Internal"/><CONSTANT CAPTION="Service"/>

</CONDITION></FILTER>


6Customizing OLAP universesPredefined conditions in OLAP universes

4. Click Parse to review the syntax and fix any errors.5. Click OK to save the condition.

Related Topics• Predefined conditions in OLAP universes on page 54• Optional prompts in OLAP universes on page 57

XML Syntax for predefined filter options

Syntax for predefined conditions

A single predefined condition may contain multiple filters combined with theAND and OR operators. By default, all filters are combined with the ANDoperator. To include filters using OR, you must use the AND and OR operatortags.

The functions @Select, @Prompt and @Variable are allowed in thepredefined filter definition.

Predefined filters can include one or multiple prompts. Prompts can bemandatory or optional.

Example: Using AND and OR tags for pre-defined conditions

<OPERATOR VALUE="AND"><FILTER "[Level Object definition]">

<CONDITION OPERATORCONDITION="Operator"><CONSTANT Level Attribute="Value"/>

</CONDITION></FILTER><OPERATOR VALUE="OR">

<FILTER "[Level Object definition]"><CONDITION OPERATORCONDITION="Operator">

<CONSTANT Level Attribute="Value"/></CONDITION>

</FILTER><FILTER “[Level Object definition]">

<CONDITION OPERATORCONDITION="Operator"><CONSTANT Level Attribute="Value"/></CONDITION>

</FILTER></OPERATOR>

</OPERATOR>


Customizing OLAP universes6 Predefined conditions in OLAP universes

Optional prompts in OLAP universesUniverses generated from OLAP data sources support optional prompts.

For SAP NetWeaver BW optional variables, filters with the optional conditionsare automatically generated in the universe.

In pre-defined conditions or in an object's WHERE clause, to make a promptoptional, embed the XML filter expression between the two XML tags:<OPTIONAL> and </OPTIONAL>.

Example: Optional prompt in a pre-defined condition

<OPTIONAL><FILTER KEY="[Products].[Family]" >

<CONDITION OPERATORCONDITION="InList" ><CONSTANT CAPTION="@prompt('Enter value(s) for

Product family:','A','Products\Family',Multi,primary_key,persistent)"/>

</CONDITION></FILTER>

</OPTIONAL>

Related Topics• Tomanually create predefined conditions in an OLAP universe on page 54

To improve performance of certainqueries onSAPNetWeaver BWuniverses

For queries on SAP NetWeaver BW universes that include only the key andmedium name detail objects of a dimension, you can modify the generatedsyntax of the objects to improve query performance.

To modify the syntax:

1. Open the universe in Designer.2. Double click the key detail object you want to modify.3. In the Select text box on the "Definition" tab of the "Edit Properties" dialog

box, change the syntax to refer to the NAME attribute of the SAPcharacteristic.


6Customizing OLAP universesOptional prompts in OLAP universes

For example, for the object L01 Customer Key, change the generatedselect syntax:

[Z_CUSTOM].[LEVEL01].[[2Z_CUSTOM]].[Value]

to refer to the NAME attribute:

[Z_CUSTOM].[LEVEL01].[NAME]

4. Click OK to save the changes.5. Follow the same steps for the name object. Change the syntax to refer

to the DESCRIPTION attribute of the SAP characteristic.For example, for the object L01 Customer Medium Name, change thegenerated select syntax:

[Z_CUSTOM].[LEVEL01].[[5Z_CUSTOM]].[Value]

to refer to the DESCRIPTION attribute:

[Z_CUSTOM].[LEVEL01].[DESCRIPTION]


Customizing OLAP universes6 To improve performance of certain queries on SAP NetWeaver BW universes

OLAP universe lifecyclemanagement

7

About OLAP universe lifecyclemanagement

Note:When you open a universe created with a version of Universe Designer priorto XIR3.1 SP2, you must refresh and save the universe before making anychanges in the universe or in the OLAP source.

OLAP universes are generated automatically from an OLAP data source (forexample, an SAP NetWeaver BW Query or an MSAS 2005 cube). InDesigner, you can create and change objects in the existing OLAP universe.

The "Update OLAP Universe" wizard allows you to refresh the structure ofOLAP universes automatically with changes made in the OLAP data source.The wizard compares the universe with the updated data source. The wizardcan differentiate generated objects from objects added or modified manually,allowing you to keep the changes made manually in Designer. The wizarddoes not update objects that were manually added in Designer.

What can be detected and updated depends on the items and the datasource, as shown in the table below.

Deleted items canbe detected in

Modified itemscan be detectedin

New items canbe detected in

What the wizardcan detect

All data sourcesAll data sourcesAll data sourcesDimensions

All data sourcesAll data sourcesSAP NetWeaverBW and MSASonly

Hierarchies

All data sourcesAll data sourcesAll data sourcesLevels

MSAS onlyMSAS onlyMSAS onlyProperties


OLAP universe lifecycle management7 About OLAP universe lifecycle management

Deleted items canbe detected in

Modified itemscan be detectedin

New items canbe detected in

What the wizardcan detect

All data sourcesAll data sourcesAll data sourcesMeasures

SAP NetWeaver BWonly

SAP NetWeaverBW only

SAP NetWeaverBW only

SAP NetWeaverBW Variables

All data sourcesAll data sourcesAll data sourcesSub-classes

Note:When you update a universe created with a version of Universe Designerearlier than XIR3.1 SP2, if the name of a dimension has changed in the SAPcube, the refresh of the dimension does not work: The dimension is duplicatedin the universe. You must manually update the classes in the universe.

Related Topics• To refresh an OLAP universe on page 65• Overview: relationship between universe object status and OLAP objectstatus on page 61

• How dimensions are managed in OLAP universe updates on page 70• How hierarchies or characteristics aremanaged in OLAP universe updates

on page 76• How levels are managed in OLAP universe updates on page 86• How SAP variables are managed in OLAP universe updates on page 91• How key figures or measures are managed in OLAP universe updates

on page 96• HowSAP key dates are managed in OLAP universe updates on page 101

Overview: relationshipbetweenuniverseobject status and OLAP object status

The table below gives a brief overview of the relationship between an SAPOLAP object state and universe object state. There are specific notesconcerning most of the actions, for more information refer to the more detailedsections in this chapter.


7OLAP universe lifecycle managementOverview: relationship between universe object status and OLAP object status

Universe object status

OLAP metadataHiddenMovedDelet

edUpdated*Unchanged

Universe equivalent = classDimension

NoCNoCNoCUpdNoCUnchanged

Status

UpdUpdNoCUpdUpdUpdated*

NoCDel/ObNoCDel/ObDel/ObDeleted

MoveNoCNoCNoCMoveMoved

CreSCreSN/ACreSCreSCharacter-istic creat-ed

CreCreN/ACreCreCreated

Universe equivalent = sub-classHierarchy or Characteristic

NoCNoCNoCUpdNoCUnchanged

Status


UpdMDX

UpdMDXNoCUpdMDXUpdMDXChanged

CreCreCreCreCreDisplay At-tribute

Del/ObDel/ObNoCDel/ObDel/ObNavigationAttribute

Del/ObDel/ObNoCDel/ObDel/ObDeleted

MoveMoveNoCMoveMoveMoved

CreCreCreCreCreNew


OLAP universe lifecycle management7 Overview: relationship between universe object status and OLAP object status



edUpdated*Unchanged

Universe equivalent = levelLevel

NoCNoCNoCNoCNoCUnchanged

Status




CreCreCreCreCreNew

Universe equivalent = filterVariable


Status UpdUpdCreUpdUpdUpdated*


CreCreCreCreCreNew

Universe equivalent = measureKey figure


Status




CreCreCreCreCreNew

Universe equivalent = parameterKey date


7OLAP universe lifecycle managementOverview: relationship between universe object status and OLAP object status



edUpdated*Unchanged

N/AN/ACreN/ANoCUnchanged

Status N/AN/AN/AN/ADelDeleted

N/AN/ACreN/ACreNew

LEGEND:• *:The one of the object properties (name, description...) has changed.• Cre: Create the equivalent object• CreS: Create the equivalent sub-class object• Del/Ob: Deleted or Obsolete (obsolete objects are hidden and their names

prefixed with ##)• Move: The object is moved• N/A: Does not apply• NoC: No change• Upd: Updated• UpdMDX: Update the MDX definition

Related Topics• To refresh an OLAP universe on page 65• How dimensions are managed in OLAP universe updates on page 70• How hierarchies or characteristics aremanaged in OLAP universe updates




OLAP universe lifecycle management7 Overview: relationship between universe object status and OLAP object status

To refresh an OLAP universeTo refresh the structure of an OLAP universe:

• In Designer, open the universe you want to update.• Select View > Refresh Structure.

The Update OLAP Universe wizard appears.• Click Begin.

The Updated metadata definitions page appears.

Select keep options when you want to preserve modifications to objectsin the universe that were made manually. All keep options are selectedby default. You can choose to keep the following attributes:

DescriptionOption

Class, Dimension, Measure, Detail and Conditionnames.

Keep business name

If the object has changed in the universe (for exam-ple, a detail is changed to a dimension, the updatewill not reintroduce the initial object type). Thisconcerns Dimensions, Measures, and Details.

Keep type of objects

When this is selected, if the description is updatedin the OLAP source, the universe is not updatedwith this information.

Keep description ofobjects

Character, Numeric, Date, and Long text objects.Keep data type of ob-jects

You can keep the options that were initially set:• Associate a list of values• Automatic refresh before use• Hierarchical display• Export with universe• Delegate search

Keep list of values op-tions of objects


7OLAP universe lifecycle managementTo refresh an OLAP universe

DescriptionOption

The options are:

Security access level

The object can be used in• Used in result• Used in condition• Used in sort

Keep advanced op-tions of objects

Items that are no longer in the data source will bedeleted from the universe.

Delete obsolete ob-jects

Items that are no longer in the cube will be hiddenin the universe and prefixed by /##/.

Hide obsolete objects

• Select the desired options and click Next.

The "Change Management Results" page appears showingadded/deleted/hidden objects. Hidden objects are moved to a separateclass in the universe and appear in italic font preceded by /##/.

• In the Added metadata options pane, set the options for how addedmetadata is treated


OLAP universe lifecycle management7 To refresh an OLAP universe

DescriptionGeneric OLAP op-tions

You can set the application to generate the tech-nical name of the universe as a property. Whenthe universe is generated, this creates an objectthat points to the technical name.


Any manually deleted universe objects will be regen-erated.

Regenerate all manu-ally deleted objects


You can set the application to set the aggregationfunction of measures to database delegated.


Universe level prefixes indicate the level in the hier-archy of an object. Level L00 is the top or root level,L01 is the next level down. In the "New UniverseWizard", you can replace OLAP universe level prefix-es with a different prefix. The level numbering is re-tained, but the prefix 'L' can be replaced by Level,for example. Type your own prefix in the New prefixfield. This prefix is prepended to all levels throughoutthe OLAP universe.


This option is disabled if Generate level 00 is set toNo. You can rename the top level (root level) L00 toAll the next time the universe is generated.


This option only applies to SAP Characteristics. Youcan disactivate this option for Characteristics only.Level 00 is always generated for hierarchies and hi-erarchy variables. You can regenerate the Levelnumbers (L00, L01, L02...) when you generate orupdate a universe. The level numbers are appendedto the level names (e.g. "Monthly Sales_L01"). Thisis useful for Web Intelligence reports, where the Alllevel is used to aggregate results for a query. Thisavoids having to create the aggregate field in theWeb Intelligence report.

Generate level 00

• On the Change Management results page, select one of:


7OLAP universe lifecycle managementTo refresh an OLAP universe

DescriptionOption

If you are not satisfied with the results, you can click OK,then close the Universe without saving or exporting.

OK

If you are satisfied with the changes, click Export to saveand export the updated universe to the CMS.

Export

ClickCheck Integrity to perform an integrity check. It checksthe structure, parses objects, parses joins, parses conditions,and checks cardinality. When the check is complete, the In-tegrity Check Results page appears. From this page youcan print the results of the check.

Check In-tegrity

If you do not see all changes to the universe that you expect, stop, thenrestart Designer before trying the update again. This makes a new connectionto the data source and clears the cache.

Related Topics• Synchronizing the universe and the OLAP cube on page 69• About OLAP universe lifecycle management on page 60

Regenerating Level 00 for OLAPuniverses

You can regenerate the Level numbers (L00, L01, L02...) when you generateor update a universe. The level numbers are appended to the level names(e.g. "Monthly Sales_L01")

Related Topics• Setting delegated measures for OLAP universes on page 48• Replacing OLAP universe level prefixes on page 69• Renaming level L00 to ALL on page 68

Renaming level L00 to ALLYou can rename the top level (root level) L00 to ALL when the universe isnext generated. This is useful for SAP BusinessObjects Web Intelligence


OLAP universe lifecycle management7 Regenerating Level 00 for OLAP universes

reports, where the ALL level is used to aggregate results for a query. Thisavoids having to create the aggregate field in the Web Intelligence report.

Example:

Related Topics• Setting delegated measures for OLAP universes on page 48• Replacing OLAP universe level prefixes on page 69• Regenerating Level 00 for OLAP universes on page 68

Replacing OLAP universe level prefixesUniverse level prefixes indicate the level in the hierarchy of an object. LevelL00 is the top or root level, L01 is the next level down. In the "New UniverseWizard", you can replace OLAP universe level prefixes with a different prefix.The level numbering is retained, but the prefix 'L' can be replaced by Level,for example. Type your own prefix in the New prefix field. This prefix isprepended to all levels throughout the OLAP universe.

Related Topics• Setting delegated measures for OLAP universes on page 48• Regenerating Level 00 for OLAP universes on page 68• Renaming level L00 to ALL on page 68

Synchronizing the universe and theOLAP cube

When you update a universe, the objects in the universe are compared withthe objects in the OLAP cube. The comparison ensures that changes madein the cube do not adversely affect the universe. This means that any objectsused (and even deleted) in the universe must always be available. Any newobjects in the OLAP cube are made available to the universe. To see howthe different objects are affected by changes, see the links below.

When object properties are updated, only certain properties are updated inthe universe, other properties should not change. The following table showswhat happens.


7OLAP universe lifecycle managementReplacing OLAP universe level prefixes

Related Topics• To refresh an OLAP universe on page 65• How dimensions are managed in OLAP universe updates on page 70• How hierarchies or characteristics aremanaged in OLAP universe updates



How dimensions are managed in OLAPuniverse updates

This applies to SAP, MSAS, and Essbase data sources. The universe classis the equivalent of the OLAP dimension. How the universe objects aremanaged with respect to the OLAP objects depends on the type of change.Refer to the topics listed below to see how the universe objects are impactedby specific OLAP object changes.

Related Topics• To refresh an OLAP universe on page 65• When a dimension is unchanged on page 70• When a dimension is updated (name, description) on page 71• When a dimension is deleted on page 73• When a dimension is moved on page 74• When a hierachy or characteristic is created on page 75• When a dimension is new on page 76

When a dimension is unchanged

The following table shows what happens to the equivalent universe class inthe different possible situations when the dimension is unchanged:


OLAP universe lifecycle management7 How dimensions are managed in OLAP universe updates

What happens to the universe classWhen the universeclass

The universe class is unchangedIs unchanged

Update the business name if the option Keep busi-ness name is selected.

Update the description if the option Keep descrip-tion is selected.

Remain unchanged if these options are not select-ed.

Is updated

No change to the universe class.

Create the object if the optionRegenerate Objectsmanually deleted is selected. Do not regeneratechildren that had not been deleted

Is deleted

No change to the universe class.Is moved

No change to the universe class.Is hidden

Related Topics• To refresh an OLAP universe on page 65• When a dimension is updated (name, description) on page 71• When a dimension is deleted on page 73• When a dimension is moved on page 74• When a hierachy or characteristic is created on page 75• When a dimension is new on page 76

When a dimension is updated (name, description)

The following table shows what happens to the equivalent universe class inthe different possible situations when the name or description of thedimension is updated:


7OLAP universe lifecycle managementHow dimensions are managed in OLAP universe updates


Update the business name if the option Keep businessname is selected.



Is unchanged




Is updated

No change to the universe class.

Create if Option: Regenerate Objects manuallydeleted is selected.

Do not regenerate children that had not beendeleted.

Is deleted




Is moved







Is hidden

Related Topics• To refresh an OLAP universe on page 65• When a dimension is unchanged on page 70• When a dimension is deleted on page 73• When a dimension is moved on page 74• When a hierachy or characteristic is created on page 75• When a dimension is new on page 76

When a dimension is deleted

The following table shows what happens to the equivalent universe class inthe different possible situations when the dimension is deleted:


Delete if the optionDelete obsolete objects is select-ed. Make the sub-class obsolete if the option Hideobsolete objects is selected. Do not delete if the classcontains custom objects

Is unchanged


Is updated




No change to the universe class.Is deleted


Is moved

No change to the universe classIs hidden

Related Topics• To refresh an OLAP universe on page 65• When a dimension is unchanged on page 70• When a dimension is updated (name, description) on page 71• When a dimension is moved on page 74• When a hierachy or characteristic is created on page 75• When a dimension is new on page 76

When a dimension is moved

The following table shows what happens to the equivalent universe class inthe different possible situations when the dimension is moved:


Move the class accordinglyIs unchanged

No changeIs updated




No change.

Create if Option: Regenerate Objects manuallydeleted = Yes

Do not regenerate children that had not beendeleted

Is deleted

No changeIs moved

Move the class accordinglyIs hidden

Related Topics• To refresh an OLAP universe on page 65• When a dimension is unchanged on page 70• When a dimension is updated (name, description) on page 71• When a dimension is deleted on page 73• When a hierachy or characteristic is created on page 75• When a dimension is new on page 76

When a hierachy or characteristic is created

Hierachy applies to MSAS or Essbase data sources, characteristic appliesto SAP data sources. The following table shows what happens to theequivalent universe class in the different possible situations when the SAPcharacteristic is created:


Create sub-classIs unchanged

Create sub-classIs updated




Does not applyIs deleted

Create sub-classIs moved

Create sub-classIs hidden

Related Topics• To refresh an OLAP universe on page 65• When a dimension is unchanged on page 70• When a dimension is updated (name, description) on page 71• When a dimension is deleted on page 73• When a dimension is moved on page 74• When a dimension is new on page 76

When a dimension is new

The universe class is created when the dimension is created.

Related Topics• To refresh an OLAP universe on page 65• When a dimension is unchanged on page 70• When a dimension is updated (name, description) on page 71• When a dimension is deleted on page 73• When a dimension is moved on page 74• When a hierachy or characteristic is created on page 75

How hierarchies or characteristics aremanaged in OLAP universe updates

This section applies to hierarchies for MSAS and Essbase data sources, andcharacteristics for SAP data sources. The universe sub-class is the equivalent


OLAP universe lifecycle management7 How hierarchies or characteristics are managed in OLAP universe updates

of the OLAP characteristic. How the universe objects are managed withrespect to the OLAP objects depends on the type of change. Refer to thetopics listed below to see how the universe objects are impacted by specificOLAP object changes.

Related Topics• To refresh an OLAP universe on page 65• When a hierarchy or characteristic is unchanged on page 77• When a characteristic business name or description is updated on

page 78• When a characteristic's active hierarchy is changed on page 80• When a characteristic display attribute is changed to a navigation attribute

on page 81• When a hierarchy or characteristic is deleted on page 83• When a hierarchy or characteristic is moved on page 85• When a hierarchy or characteristic is new on page 86

When a hierarchy or characteristic is unchanged

The following table shows what happens to the equivalent universe sub-classin the different possible situations when the hierarchy or characteristic isunchanged:

What happens to the universe sub-classWhen the universesub-class

No changeIs unchanged

No changeIs updated

No change.


Do not regenerate children levels that had not beendeleted

Is deleted

No changeIs moved


7OLAP universe lifecycle managementHow hierarchies or characteristics are managed in OLAP universe updates


No changeIs hidden

Related Topics• To refresh an OLAP universe on page 65• When a characteristic business name or description is updated on



When a characteristic business name or descriptionis updated

The following table shows what happens to the equivalent universe sub-classin the different possible situations when the characteristic is updated:





Is unchanged







Is updated

No change.


Do not regenerate children levels that had not beendeleted

Is deleted




Is moved




Is hidden

Related Topics• To refresh an OLAP universe on page 65• When a hierarchy or characteristic is unchanged on page 77



• When a characteristic's active hierarchy is changed on page 80• When a characteristic display attribute is changed to a navigation attribute


When a characteristic's active hierarchy is changed

This applies to SAP data sources only. The following table shows whathappens to the equivalent universe sub-class in the different possiblesituations when the characteristic's active hierarchy has changed:


Update the MDX definitions of existing objects in thesub-class to reference the new active hierarchy.

Reports built before refresh continue to workIs unchanged


Reports built before refresh continue to workIs updated

No change.


Does not regenerate children levels that were notdeleted.

Is deleted


Reports built before refresh continue to work.Is moved




Update the MDX definitions of existing objects in thesub-class to reference the new active hierarchy.Is hidden


page 78• When a characteristic display attribute is changed to a navigation attribute


When a characteristic display attribute is changed toa navigation attribute

This applies to SAP data sources only. The following table shows whathappens to the equivalent universe sub-class in the different possiblesituations when the characteristic display attribute is changed to a navigationattribute:


CreateIs unchanged

CreateIs updated

CreateIs deleted

CreateIs moved




CreateIs hidden


page 78• When a characteristic's active hierarchy is changed on page 80• When a hierarchy or characteristic is deleted on page 83• When a hierarchy or characteristic is moved on page 85• When a hierarchy or characteristic is new on page 86

When a characteristic navigation attribute is changedto a display attribute

This applies to SAP data sources only. The following table shows whathappens to the equivalent universe sub-class in the different possiblesituations when the hierarchy or characteristic navigation attribute is changedto a display attribute:


Delete if the optionDelete obsolete objects is select-ed. Make the sub-class hidden if the option Hide ob-solete objects is selected. Does not delete if the classcontains custom objects.

Is unchanged


Is updated




No changeIs deleted


Is moved


Is hidden


page 78• When a characteristic's active hierarchy is changed on page 80• When a hierarchy or characteristic is deleted on page 83• When a hierarchy or characteristic is moved on page 85• When a hierarchy or characteristic is new on page 86

When a hierarchy or characteristic is deleted

The following table shows what happens to the equivalent universe sub-classin the different possible situations when the hierarchy or characteristic isdeleted:




Delete if the optionDelete obsolete objects is select-ed. Make the sub-class obsolete if the option Hideobsolete objects is selected. Do not delete if the sub-class contains custom objects.

Is unchanged

Delete if the optionDelete obsolete objects is select-ed, make the sub-class obsolete if the option Hideobsolete objects is selected. Do not delete if the sub-class contains custom objects.

Is updated

No changeIs deleted


Is moved


Is hidden



on page 81• When a hierarchy or characteristic is moved on page 85• When a hierarchy or characteristic is new on page 86



When a hierarchy or characteristic is moved

If the characteristic is moved within the same dimension, there is no change:ignore the table below. The following table shows what happens to theequivalent universe sub-class in the different possible situations when thehierarchy or characteristic is moved to another dimension:


Move the sub-class accordingly.Is unchanged

Move the sub-class accordingly.Is updated

No change.


Do not regenerate children levels that had not beendeleted.

Is deleted

No change.Is moved

Move the sub-class accordingly.Is hidden



on page 81• When a hierarchy or characteristic is deleted on page 83• When a hierarchy or characteristic is new on page 86



When a hierarchy or characteristic is new

The universe sub-class created when the hierarchy or characteristic iscreated.



on page 81• When a hierarchy or characteristic is deleted on page 83• When a hierarchy or characteristic is moved on page 85

How levels are managed in OLAPuniverse updates

Note:In the universe, do not move levels to other hierarchies. If you want to movea level, copy and paste the level to the new hierarchy.

The universe level or dimension object is the equivalent of the OLAP level.How the universe objects are managed with respect to the OLAP objectsdepends on the type of change. Refer to the topics listed below to see howthe universe objects are impacted by specific OLAP object changes.

Related Topics• To refresh an OLAP universe on page 65• When a level is unchanged on page 87• When the name or description of a level is updated on page 87• When a level is deleted on page 89• When a level is moved on page 90• When a level is new on page 90


OLAP universe lifecycle management7 How levels are managed in OLAP universe updates

When a level is unchanged

The following table shows what happens to the universe level in the differentpossible situations when the level is unchanged:

What happens to the universe levelWhen the universelevel


No changeIs updated

No change. Create if Option: Regenerate Objectsmanually deleted = YesIs deleted

No changeIs moved

No changeIs hidden

Related Topics• To refresh an OLAP universe on page 65• When the name or description of a level is updated on page 87• When a level is deleted on page 89• When a level is moved on page 90• When a level is new on page 90

When the name or description of a level is updated

The following table shows what happens to the universe level in the differentpossible situations when the name or description of a level is updated:


7OLAP universe lifecycle managementHow levels are managed in OLAP universe updates





Is unchanged




Is updated





Is moved




Is hidden



Related Topics• To refresh an OLAP universe on page 65• When a level is unchanged on page 87• When a level is deleted on page 89• When a level is moved on page 90• When a level is new on page 90

When a level is deleted

The following table shows what happens to the universe level in the differentpossible situations when the level is deleted:


Delete if the optionDelete obsolete objects is select-ed. Make the sub-class obsolete if the option Hideobsolete objects is selected.

Is unchanged


Is updated

No change.Is deleted


Is moved


Is hidden

Related Topics• To refresh an OLAP universe on page 65• When a level is unchanged on page 87• When the name or description of a level is updated on page 87• When a level is moved on page 90


7OLAP universe lifecycle managementHow levels are managed in OLAP universe updates

• When a level is new on page 90

When a level is moved

The following table shows what happens to the universe level in the differentpossible situations when the level is moved:


Move the level accordingly (within the same hierarchy).Is unchanged

Move the level accordingly (within the same hierarchy).Is updated

No change. Create if Option: Regenerate Objectsmanually deleted = Yes.Is deleted

No change. Create if Option: Regenerate Objectsmanually deleted = Yes.Is moved

Move the level accordingly (within the same hierarchy).Is hidden

Related Topics• To refresh an OLAP universe on page 65• When a level is unchanged on page 87• When the name or description of a level is updated on page 87• When a level is deleted on page 89• When a level is new on page 90

When a level is new

The universe level is created when the OLAP level is created.

Related Topics• To refresh an OLAP universe on page 65• When a level is unchanged on page 87



• When the name or description of a level is updated on page 87• When a level is deleted on page 89• When a level is moved on page 90

HowSAPvariables aremanaged inOLAPuniverse updates

This section only concerns SAP data sources. The universe filter andassociated list of values objects are the equivalent of the OLAP variable.How the universe objects are managed with respect to the OLAP objectsdepends on the type of change. Refer to the topics listed below to see howthe universe objects are impacted by specific OLAP object changes.

Related Topics• To refresh an OLAP universe on page 65• When an SAP variable is unchanged on page 91• When the name or description of an SAP variable is updated on page 92• When an SAP variable is deleted on page 93• When an SAP variable is new on page 95

When an SAP variable is unchanged

The following table shows how universe filters are managed in the differentpossible situations when the SAP source variable is unchanged:

What happens to the universe filterWhen the universe fil-ter


No changeIs updated

Create. If the characteristic referenced in the variableis not in the universe, then create a sub-class for thatcharacteristic too.

Is deleted

No changeIs moved


7OLAP universe lifecycle managementHow SAP variables are managed in OLAP universe updates


No changeIs hidden

Related Topics• To refresh an OLAP universe on page 65• When the name or description of an SAP variable is updated on page 92• When an SAP variable is deleted on page 93• When an SAP variable is new on page 95

When the name or description of an SAP variable isupdated

The following table shows how universe filters are managed in the differentpossible situations when either the name or description of the SAP sourcevariable is updated:





Is unchanged




Is updated


OLAP universe lifecycle management7 How SAP variables are managed in OLAP universe updates


Create. If a characteristic referenced in the variableis not in the universe, then create a sub-class for thatcharacteristic too.

Is deleted




Is moved




Is hidden

Related Topics• To refresh an OLAP universe on page 65• When an SAP variable is unchanged on page 91• When an SAP variable is deleted on page 93• When an SAP variable is new on page 95

When an SAP variable is deleted

The following table shows how universe filter is managed in the differentpossible situations when the SAP variable is deleted:




Delete if the optionDelete obsolete objects is select-ed. Make the sub-class hidden if the option Hide ob-solete objects is selected. When made obsolete: alsochange from Compulsory to Optional to avoid automat-ic application in queries

Is unchanged


Is updated



Is moved


Is hidden

Related Topics• To refresh an OLAP universe on page 65• When an SAP variable is unchanged on page 91• When the name or description of an SAP variable is updated on page 92• When an SAP variable is new on page 95


OLAP universe lifecycle management7 How SAP variables are managed in OLAP universe updates

When an SAP variable is new

The following table shows how universe filters are managed in the differentpossible situations when the SAP variable is new:



Is unchanged


Is updated


Is deleted


Is moved


Is hidden

Related Topics• To refresh an OLAP universe on page 65• When an SAP variable is unchanged on page 91• When the name or description of an SAP variable is updated on page 92• When an SAP variable is deleted on page 93



How key figures or measures aremanaged in OLAP universe updates

SAP data souces use key figures, MSAS and Essbase data sources usemeasures. The universe measure is the equivalent of the OLAP key figure.How the universe objects are managed with respect to the OLAP objectsdepends on the type of change. Refer to the topics listed below to see howthe universe objects are impacted by specific OLAP object changes.

Related Topics• To refresh an OLAP universe on page 65• When a key figure or measure is unchanged on page 96• When the name, description, or data type of a key figure or measure isupdated on page 97

• When a key figure or measure is deleted on page 99• When a key figure or measure is moved on page 100• When a key figure or measure is new on page 101

When a key figure or measure is unchanged

The following table shows what happens to the universe measure in thedifferent possible situations when the SAP key figure or MSAS/Essbasemeasure is unchanged:

What happens to the universe measureWhen the universemeasure


No changeIs updated

No change. Create if the option Regenerate Objectsmanually deleted = YesIs deleted

No changeIs moved

No changeIs hidden


OLAP universe lifecycle management7 How key figures or measures are managed in OLAP universe updates

Related Topics• To refresh an OLAP universe on page 65• When the name, description, or data type of a key figure or measure isupdated on page 97

• When a key figure or measure is deleted on page 99• When a key figure or measure is moved on page 100• When a key figure or measure is new on page 101

When the name, description, or data type of a keyfigure or measure is updated

The following table shows what happens to the universe measure in thedifferent possible situations when the SAP key figure or MSAS/Essbasemeasure is updated:




Update the data type if the option Keep data typeof objects is selected.


Is unchanged


7OLAP universe lifecycle managementHow key figures or measures are managed in OLAP universe updates






Is updated






Is moved





Is hidden



Related Topics• To refresh an OLAP universe on page 65• When a key figure or measure is unchanged on page 96• When a key figure or measure is deleted on page 99• When a key figure or measure is moved on page 100• When a key figure or measure is new on page 101

When a key figure or measure is deleted

The following table shows what happens to the universe measure in thedifferent possible situations when the SAP key figure or MSAS/Essbasemeasure is deleted:



Is unchanged


Is updated



Is moved


Is hidden

Related Topics• To refresh an OLAP universe on page 65• When a key figure or measure is unchanged on page 96


7OLAP universe lifecycle managementHow key figures or measures are managed in OLAP universe updates

• When the name, description, or data type of a key figure or measure isupdated on page 97

• When a key figure or measure is moved on page 100• When a key figure or measure is new on page 101

When a key figure or measure is moved

The following table shows what happens to the universe measure in thedifferent possible situations when the SAP key figure or MSAS/Essbasemeasure is moved:


Move the object accordingly.Is unchanged

Move the object accordingly.Is updated

No change. Create if Option: Regenerate Objectsmanually deleted = Yes.Is deleted

No change.Is moved

Move the object accordingly.Is hidden


• When a key figure or measure is deleted on page 99• When a key figure or measure is new on page 101



When a key figure or measure is new

The universe measure is created when the OLAP key figure or measure iscreated.


• When a key figure or measure is deleted on page 99• When a key figure or measure is moved on page 100

How SAP key dates are managed inOLAP universe updates

This section applies to SAP data sources only. The universe parameter isthe equivalent of the OLAP Key Date. How the universe objects are managedwith respect to the OLAP objects depends on the type of change. Refer tothe topics listed below to see how the universe objects are impacted byspecific OLAP object changes.

Related Topics• To refresh an OLAP universe on page 65• When a SAP key date is unchanged on page 101• When a SAP key date is deleted on page 102• When a SAP key date is new on page 103

When a SAP key date is unchanged

The universe parameter is the equivalent of the OLAP Key Date. The followingtable shows what happens to the universe parameter in the different possiblesituations when the SAP key date is unchanged:


7OLAP universe lifecycle managementHow SAP key dates are managed in OLAP universe updates

What happens to the universe parameterWhen the universeparameter


Not applicableIs updated

Not applicableIs deleted

Not applicableIs moved

Not applicableIs hidden

Related Topics• To refresh an OLAP universe on page 65• When a SAP key date is deleted on page 102• When a SAP key date is new on page 103

When a SAP key date is deleted

The universe parameter is the equivalent of the OLAP Key Date. The followingtable shows what happens to the universe parameter in the different possiblesituations when the SAP key date is deleted:


DeleteIs unchanged


Not applicableIs deleted




OLAP universe lifecycle management7 How SAP key dates are managed in OLAP universe updates

Related Topics• To refresh an OLAP universe on page 65• When a SAP key date is unchanged on page 101• When a SAP key date is new on page 103

When a SAP key date is new

The universe parameter is the equivalent of the OLAP Key Date. The followingtable shows what happens to the universe parameter in the different possiblesituations when the SAP key date is new:


CreateIs unchanged


CreateIs deleted



Related Topics• To refresh an OLAP universe on page 65• When a SAP key date is unchanged on page 101• When a SAP key date is deleted on page 102


7OLAP universe lifecycle managementHow SAP key dates are managed in OLAP universe updates


OLAP universe lifecycle management7 How SAP key dates are managed in OLAP universe updates

How the different OLAPcubes are mapped touniverses

8

How SAP NetWeaver BW objects aremapped and used in a universe

When you create a universe from either an InfoCube or a BW Query, Designermaps SAP NetWeaver BW OLAP structures to equivalent classes and objectsin the universe.

All InfoObjects in the BW Query set as rows, columns, free characteristics,and filters are exposed to the universe. This includes characteristics,hierarchies, key figures, structures, and variables.

Hierarchies are mapped, allowing Web Intelligence users to drill downaccording to BW hierarchies.

For InfoCubes, all the dimensions, key figures, and hierarchies are mapped.

The following table shows the universe objects created for each BW object.

Universe objects created:NetWeaver BW object:

ClassDimension Group

Subclass with dimension and detailobjectsCharacteristic

If data source is a BW Query: Sub-class containing dimension and detailobjects for each hierarchy level in thecurrently defined hierarchy

If data source is an InfoCube: Sub-classes containing dimension anddetail objects for each hierarchy levelfor all hierarchies defined for thecharacteristic

Characteristic with hierarchy


How the different OLAP cubes are mapped to universes8 How SAP NetWeaver BW objects are mapped and used in a universe

Universe objects created:NetWeaver BW object:

Class with single dimension objectfor the structure

Structure based on Characteristics(BW Queries only)

Subclass with dimension and detailobjects (same as Characteristic)Navigation attribute

Detail object for the dimensionDisplay attribute

ClassKey Figure structure

Measure object in the class for theKey Figure structure with dimensionobjects for units/currency.

Key Figure

Measure and dimension objects(same as Key Figure)

Calculated Key Figure (BW Queriesonly)

Measure and dimension objects(same as Key Figure)

Restricted Key Figure (BW Queriesonly)

Filter mandatory in query

In the class for the dimension towhich the variable applies, two dimen-sion objects supporting the list ofvalues, one for caption, one for de-scription.

Variables (BW Queries only)

Universe parameters defining keydate variable in the universeKey date variable (BW Queries only)


8How the different OLAP cubes are mapped to universesHow SAP NetWeaver BW objects are mapped and used in a universe

Characteristics in the Filters section of the BW Query are not mapped.However, the filtering applies to the universe. If the filter has a fixed value,the filter is applied transparently when running the Web Intelligence query.If the characteristic has a variable defined, the variable is mapped with theselimitations:

• The variable always behaves like a mandatory variable• Hierarchy and hierarchy node variables are supported except for the

hierarchy version variable

To avoid these limitations, Business Objects recommends moving thecharacteristic from the Filter section to the Free section of the BW Query.

Related Topics• How characteristics are mapped and used on page 108• How key figures are mapped and used on page 109• How hierarchies are mapped and used on page 109• How variables are supported in universes on page 110• How variables are mapped to a universe on page 113

How characteristics are mapped and used

When no hierarchy is defined on the characteristic in the BW Query orInfoCube, Designer creates a class containing the characteristic as twodimension objects: Level 00 and Level 01. The Level 00 dimension representsthe aggregation of the characteristic when all members are selected (themember returned from NetWeaver is All members). The Level 01 dimensioncontains all members for the characteristic as a flat list of values.

For each dimension object, Designer creates a detail object for the key, upto three detail objects for the description (short, medium, and longdescriptions), and a detail object for each display attribute.

The SELECT clause is defined using the technical name of the characteristic.

Navigation attributes defined in the BW Query are mapped in the parentobject class in the same way as characteristics are mapped.

Note:A large number of navigation attributes defined in the universe negativelyimpacts the performance of the query in Web Intelligence.



Stuctures defined in the BW Query that are based on characteristics areincluded in the universe as single-dimension objects with the elements ofthe structure as dimension members.

How key figures are mapped and used

All key figures in the InfoCube or defined in the BW Query are included inthe universe under a single object class called Key Figures.

Most key figures are defined in NetWeaver BW with either a currency or aunit characteristic. For each key figure, Designer creates:

• A measure object with numeric format corresponding to the key figurewithout the unit.

• A dimension object with character format that contains the unit or currency.For example, 'USD', '€', 'km'.

• A dimension object with character format that contains the key figure andthe unit (formatted value) based on user preferences configured on theSAP server. For example, '200 USD', '345 €', '25 km'.

The Key Figures class includes the calculated key figures and restricted keyfigures defined in the BW Query. The original calculation and restrictions areapplied to the query, but are not exposed in the universe.

How hierarchies are mapped and used

Hierarchies are mapped to allow Web Intelligence users to drill down withSAP NetWeaver BW hierarchies in the same way as custom-made universehierarchies.

Note:The Use Query Drill option in the Web Intelligence Document Propertiesdialog box significantly improves drill down performance.

When a hierarchy is defined on a characteristic in the BW Query, Designercreates one hierarchical structure in the universe, with a subclass for eachlevel in the hierarchy. The structure depends on the current BW Querydefinition:

• If a hierarchy is defined in the BW Query, Designer creates this hierarchystructure in the universe.



• If a hierarchy variable is defined in the BW Query that allows the user tochoose a hierarchy at run time, Designer creates a generic hierarchy inthe universe. The structure has the highest number of levels defined forany of the hierarchy structures available for the characteristic.

When building a universe on top of an InfoCube, all hierarchies defined onthe characteristic are exposed in the resulting universe. Designer createssubclasses for each hierarchical structure, each containing subclasses forthe levels in that hierarchy.

In the universe, Level 00 of a hierarchy represents the top node of thestructure. When multiple tops exist for the hierarchical structure, the Level00 dimension contains all top nodes as a list of values. When the hierarchyattribute is set to not filter unassigned nodes, it is necessary to include Level00 with the top node for unassigned members. Unassigned members aregrouped at the lowest level of the hierarchy.

Note:Most often SAP NetWeaver BW hierarchies have only one top node. Youcan delete the Level 00 objects from the default universe to make the universesimpler to use. Generally, you only need to keep Level 00 when there is aneed to query/report unassigned members.

If the number of levels in a hierarchy changes in the BW Query, you mustupdate the universe.

Related Topics• About OLAP universe lifecycle management on page 60

How variables are supported in universes

SAP variables can be interpreted as user prompts defined in the BW Query.Variables can be mandatory or optional, and can have default values.

Variables for characteristics are used to filter values for a characteristic.Variables are populated with values when a query is executed. They canstore characteristic values, hierarchies, hierarchy nodes, texts, and formulaelements.

NetWeaver BW variables apply to BW Queries only.



Note:When defining the variable in the BW Query Designer, on the SAP NetWeaverBW Variables Wizard Other Settings dialog box, the Ready for Input optionmust be selected.

The following types of SAP NetWeaver BW variables are supported inuniverses:

• Characteristic variables• Hierarchy variables, except for the hierarchy version variable• Hierarchy node variables• Currency variables• Formula variables• Text variables (as replacement path)• Key date variables

The following table shows universe support for user entry BW variables. Userentry variables can be mandatory or optional, and can have default values.

Support LevelVariable Type

supportedsingle value prompt

Characteristic(including keydate and curren-cy)

supportedmultiple single valueprompt

supported

this is not supported for the keydate variable which is a singlevalue variable

interval prompt

supported as interval prompt

this is not supported as an intervalprompt for the key date variablewhich is a single value variable

selection option prompt

not supportedpre-calculated value set

supportedText



Support LevelVariable Type

price, quota, and numeric valuessupportedFormula

supported except for version vari-ableHierarchy

supportedHierarchy node

The following table shows universe support for other processing types ofBW variables.

Processing Type

Variable typeSAP exitCustomer ex-

itAuthorizationReplace-ment path

supported

supported, noprompt is cre-ated in theuniverse

supportedsupportedCharacteristic

N/AsupportedN/AsupportedText

supportedwithout userentry

supportedN/AsupportedFormula

supportedsupportedN/AN/AHierarchy

supportedwithout userentry

supportedN/AN/AHierarchy node

The Exclude operator is supported, however Web Intelligence does notspecify that the selected value be excluded from the query. Other operators,such as Less than and Greater than, can only be used with Selection optionentry type. The selection option type is turned into an interval for WebIntelligence prompting.



Note:To process BW variables in Web Intelligence, you must include at least onemeasure in the Web Intelligence query.

Related Topics• How variables are mapped to a universe on page 113• How key date variables are supported in a universe on page 115• How hierarchy and hierarchy node variables are supported in a universe

on page 117

How variables are mapped to a universe

The user needs to be prompted for all optional and mandatory variables,even when the dimension is not used in the result set, allowing the user tolimit the result set. Therefore, a variable defined in the BW Query is mapped,even if the corresponding characteristic is not in the query.

The user needs to know if a variable is mandatory or optional, and be ableto ignore optional variables. Optional variables are defined as optional in theuniverse, and become optional prompts in Web Intelligence. Mandatoryvariables become mandatory prompts in Web Intelligence.

For characteristic variables, Designer creates a mandatory filter in theuniverse. A mandatory filter is a pre-defined query filter object which is hiddento Web Intelliegence users, but is applied systematically and transparentlyto all Web Intelligence queries built on the universe.

Mapped toVariable Type

Universe mandatory filterCharacteristic variable, including cur-rency and formula variable

Universe mandatory filterHierarchy variable

Class mandatory filterHierarchy node variable

Universe parametersKey date variable

For each mandatory filter, two dimension objects are created as referenceobjects for the @Prompt function to display the expected list of values. The



list of values dimensions are hidden in the universe. They are necessary forthe correct functioning of the prompt so must not be deleted and must bemoved or modified carefully.

Default values for variables are defined in the @Prompt function in the filterusing the primary key, persistent/not persistent, and default valuesparameters. The @Prompt function syntax can be seen in the Propertiespage of the filter in the universe.

To avoid conflict between BW variables and filters defined by Web Intelligenceusers, objects involved in an SAP variable definition are generated with theoption Can be used in Condition unchecked in the Advanced page of theobject properties. This restricts Web Intelligence users from includingdimensions involved in SAP variables in the Filter pane.

Example: WHERE clause generated for an SAP BW variable

This example shows the WHERE clause generated for a BW variable ondimension object Customer2. The syntax for the generated WHERE clausefor a variable can be seen on the Properites page of the filter.

<FILTER KEY="[Z_VAR002]"><CONDITION OPERATORCONDITION="Equal">

<CONSTANT TECH_NAME="@Prompt('Customer Variable Single Value Mandatory','A','Customer2\LovCustomer Variable Single Value

MandatoryBase',mono,primary_key)"/>

<CONDITION></FILTER>

The prompt text is generated from the BW variable name. You can edit thetext to make it more descriptive.

Customer2\LovCustomer Variable Single Value MandatoryBase is the nameof the hidden universe object that is used to build the list of values.

Note:If you rename the class or move the list of values object to another folder, youmust update the syntax in the filter key.



How variables and lists of values are supported

An SAP BW Query can contain more than ten variables, which means thatten or more lists of values can be loaded. Loading and refreshing lists ofvalues can have an important impact on performance. The following optionsare available for improving query performance for queries with variables:

• At universe generation time, all SAP BW variables (except key date) aremapped to mandatory filters. By default, the filter objects are notassociated with a list of values (except for hierarchy node variables). Youmust explicitly associate a list of values in the object properties page.

• Optional variables are generated as optional prompts. An optional promptdoes not automatically load the list of values at query run time.

• The delegate search option on the list of values properties presents theuser with an empty list of values at query run time. The user enters searchcriteria to limit the number of values returned in the list of values.

To activate the delegated search option for a list of values, edit the list ofvalues properties on the object properties page of the object to which thelist of values applies.

Note:The delegated search is not supported for cascading lists of values.

Related Topics• Optional prompts in OLAP universes on page 57

How key date variables are supported in a universe

A key date variable in a BW Query allows you to specify a date fortime-dependent data. Key dates can influence the data retrieved for adimension, for example, a product description can change over time. A keydate can influence a hierarchy structure, for example, a specific cost centercan be on Level 01 in one year, and on Level 02 in a different year.

The key date variable is a special SAP BW variable because the date valueentered by the user is not contained in any dimension of the BW Query. Thekey date is a property of the query.

In a BW Query, the key date variable can be defined for two uses:



• To specify the valid date for a specific hierarchy, impacting only thathierarchy.

• To specify a date for the complete query. In this case, the key date thatis set in a query influences the following:• time-dependent master data• currency exchange rates• the list of hierarchies• time-dependent hierarchy structures

Note:In the universe, the use of a key date is limited to the whole universe.Therefore, the key date generated in a universe impacts all other SAPvariables and data.

SAP NetWeaver BW supports only one key date variable per BW Query,therefore a universe contains only one key date variable.

Key date variables can be mandatory or optional, and can have a defaultvalue. If no default value is defined and the user does not enter a value, thequery uses the current system date.

The key date variable properties of the query are mapped to five universeparameters, described in the following table.

DescriptionParameter

Set to Yes if a key date is enabled onthe universe.KEYDATE_ENABLED

Technical name of the key date vari-able.KEYDATE_NAME

Caption for the key date variable pre-sented when prompting the user for avalue.

KEYDATE_CAPTION

Default value for the key date, if it ex-ists.KEYDATE_DEFAULT_VALUE

Set to Yes if a user must enter a valueor use the default.KEYDATE_MANDATORY



At query run time, Web Intelligence proposes the same key date for allqueries. The user can modify the key date. A "Keydate Properties" dialogbox is available to manage which key date is used. The user is prompted forthe key date before any other type of variable prompt.

How hierarchy and hierarchy node variables are supported in auniverse

A hierarchy variable is used to prompt the user for the hierarchy to be usedin the query. Web Intelligence users can create queries and reports to retrieveand display members from any hierarchy.

If the hierarchy variable is optional and the user leaves the prompt empty,no hierarchy is used in the report.

A report contains the largest number of hierarchy levels independent of thehierarchy that is selected. Hierarchy levels that are not returned in the resultset are empty in the report.

A hierarchy node variable is used to prompt the user for the node to bedefined as top node for the hierarchy in the query.

When a query contains both a hierarchy and hierarchy node variable, theWeb Intelligence user must first select a hierarchy in the list of availablehierarchies. Next, the user selects the hierarchy node. The list of hierarchynodes available shows hierarchy nodes for all hierarchies. The list is notfiltered based on the hierarchy selected. The user is responsible for selectinga node from the correct hierarchy. Selecting a hierarchy node from a differenthierarchy can cause the report to be empty.

Related Topics• How hierarchies are mapped and used on page 109

How Essbase cubes are mapped touniverse components

Designer creates a universe from an Essbase cube by mapping Essbaseoutlines to equivalent classes and objects. You identify the cube data sourcewhen you create the connection.


8How the different OLAP cubes are mapped to universesHow Essbase cubes are mapped to universe components

Essbase alias tables define a set of alternate names for dimensions, levels,and members in the outline. Designer generates the universe using thenames according to the alias table you select when you create the connectionto the Essbase data source.

In an Essbase outline, measures are defined as dimensions. You select thedimension to use as the measures dimension when you create the connectionto the Essbase data source. Designer generates the members of thatdimension as measures in the universe.

Any dimension supports hierarchies with multiple levels. A maximum of onehierarchy can be defined for each dimension.

The following table shows which objects are created in the universe for eachEssbase outline element.

Universe object created:Essbase Object

A class containing the generations forthe dimension.Dimension

An object in the dimension class withtwo detail objects: one for caption, onefor name.

Generation

A class named according to the dimen-sion selected as the measures dimen-sion in the universe connection (usuallyMeasures class or Accounts class).

Measures dimension

A measure object in the measure classor subclass. The measures are createdwith a structure of class and subclassthat matches the structure in the Ess-base outline.

Measure

Measures are generated with the aggregation projection function set toDatabase delegated by default. When refreshing the Web Intelligence report,the aggregation of the measure is delegated to the database server.

Related Topics• About connections to OLAP data sources on page 28• Database delegated projection function on page 45


How the different OLAP cubes are mapped to universes8 How Essbase cubes are mapped to universe components

HowMSAScubes aremapped touniversecomponents

Designer creates a universe from MSAS cubes by mapping MSAS structuresto equivalent classes and objects. You specify the cube data source whenyou create the connection.

The following table shows which objects are created in the universe structuresfor each MSAS object. This mapping applies to MSAS virtual cubes and localcubes (.cub files) as well as MSAS standard cubes.

Universe object created:MSAS Object:

A class containing objects for that di-mension.Dimension

A subclass in the dimension class.Display Folder (MSAS 2005)

A subclass in the corresponding dimen-sion class or a sub-subclass in thecorresponding display folder class.

Hierarchy

A subclass in the corresponding dimen-sion class or a sub-subclass in thecorresponding display folder class.

Attribute (MSAS 2005)

A Measure class containing all mea-sure objects. Measure objects are cre-ated in the Measure class, or the sub-class for the Measure Group.

Measures

A subclass in the Measure class.Measure Group (MSAS 2005)

An object in the dimension class orsubclass, and a Level All object whichrepresents the aggregate of all sub-levels.

Level


8How the different OLAP cubes are mapped to universesHow MSAS cubes are mapped to universe components

Universe object created:MSAS Object:

A detail in the level object to which itapplies.Level Property

Measures are generated with the aggregation projection function set toDatabase delegated by default. When refreshing the Web Intelligence report,the aggregation of the measure is delegated to the database server.

Related Topics• About connections to OLAP data sources on page 28• Database delegated projection function on page 45


How the different OLAP cubes are mapped to universes8 How MSAS cubes are mapped to universe components

More Information

A

LocationInformation Resource

http://www.sap.comSAP BusinessObjects productinformation

Select http://help.sap.com > SAP BusinessObjects.

You can access the most up-to-date documentation cover-ing all SAP BusinessObjects products and their deploymentat the SAP Help Portal. You can download PDF versionsor installable HTML libraries.

Certain guides are stored on the SAP Service Marketplaceand are not available from the SAP Help Portal. Theseguides are listed on the Help Portal accompanied by a linkto the SAP Service Marketplace. Customers with a mainte-nance agreement have an authorized user ID to accessthis site. To obtain an ID, contact your customer supportrepresentative.

SAP Help Portal

http://service.sap.com/bosap-support > Documentation• Installation guides: https://service.sap.com/bosap-inst

guides• Release notes: http://service.sap.com/releasenotes

The SAP Service Marketplace stores certain installationguides, upgrade and migration guides, deployment guides,release notes and Supported Platforms documents. Cus-tomers with a maintenance agreement have an authorizeduser ID to access this site. Contact your customer supportrepresentative to obtain an ID. If you are redirected to theSAP Service Marketplace from the SAP Help Portal, usethe menu in the navigation pane on the left to locate thecategory containing the documentation you want to access.

SAP Service Marketplace

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibraryDeveloper resources


More InformationA

http://www.sap.com

http://help.sap.com/

http://service.sap.com/bosap-support

https://service.sap.com/bosap-instguides

https://service.sap.com/bosap-instguides

http://service.sap.com/releasenotes

https://boc.sdn.sap.com/

https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary

LocationInformation Resource

https://www.sdn.sap.com/irj/boc/businessobjects-articles

These articles were formerly known as technical papers.

SAP BusinessObjects articleson the SAP Community Net-work

https://service.sap.com/notes

These notes were formerly known as Knowledge Base ar-ticles.

Notes

https://www.sdn.sap.com/irj/scn/forumsForums on the SAP Communi-ty Network

http://www.sap.com/services/education

From traditional classroom learning to targeted e-learningseminars, we can offer a training package to suit yourlearning needs and preferred learning style.

Training


The SAP Support Portal contains information about Cus-tomer Support programs and services. It also has links toa wide range of technical information and downloads.Customers with a maintenance agreement have an autho-rized user ID to access this site. To obtain an ID, contactyour customer support representative.

Online customer support

http://www.sap.com/services/bysubject/businessobjectsconsulting

Consultants can accompany you from the initial analysisstage to the delivery of your deployment project. Expertiseis available in topics such as relational and multidimensionaldatabases, connectivity, database design tools, and customized embedding technology.

Consulting


AMore Information

https://www.sdn.sap.com/irj/boc/businessobjects-articles

https://service.sap.com/notes

https://www.sdn.sap.com/irj/scn/forums

http://www.sap.com/services/education





More InformationA

IndexAadd

connection OLAP 28additional OLAP parameters 40aggregate

set projection for measure 48alias

tables Essbase 117authentication

Essbase connections 33MSAS connections 32SAP NetWeaver BW connections 30

Ccalculated measure

in OLAP universe 49characteristics

mapping in OLAP universe 108classes and objects

mapping in OLAP universe (Essbase) 117mapping in OLAP universe (MSAS) 119mapping in OLAP universe (NetWeaver BW)

106modifying in OLAP universes 44

condition objectdefining in OLAP universe 54

Configuration optionsin OLAP universes 41

connectionOLAP universe 28parameters overview OLAP 28

createconnection OLAP 28

create (continued)universe from OLAP source 18

Ddefine

condition object in OLAP universe 54connection OLAP 28

EEssbase cube

defining connection 28features supported in universe 25mapping objects to universe 117

Hhierarchy

mapping in OLAP universe (NetWeaver BI)109

variables (NetWeaver BW) 117

Iindex awareness

in OLAP universes 44

Kkey date variables

in OLAP universes 115key figures

mapping in OLAP universe 109


Llist of values

and SAP NetWeaver BW variables 115

Mmandatory filter

variables (SAP NetWeaver BW) 113MDX functions 51measure

aggregate projection 48calculated 49database delegated projection function 45

MSAS cubedefining connection 28features supported in universe 24mapping objects to universe 119

multilingual universesSAP NetWeaver BW 15, 23

OOLAP additional parameters 40OLAP universes

creating 18data sources supported 19defining connection 28mapping Essbase objects 117mapping MSAS objects 119mapping SAP NetWeaver BW objects 106MDX functions 51modifying 44options 41

optional promptin OLAP universe 57

Pprompt

optional (OLAP universe) 57

Rrefresh

OLAP universe 60

SSAP NetWeaver BI

defining connection 28SAP NetWeaver BW

data sources for OLAP universe 12, 19features supported in universe 14, 22mapping to OLAP universe 106multilingual universes 15, 23

Single Sign On (SSO)MSAS 2005 32SAP NetWeaver BW 10, 23

smart measure 45synchronizing OLAP universes 69

Uuniverse

OLAP 18refresh OLAP 60update OLAP 60

universe lifecycle (OLAP) 60update

OLAP universe 60

Vvariables

in OLAP universe (NetWeaver BW) 110


Index

using sap netweaver business intelligence in universe designer

Documents