First-hand knowledge.

Reading Sample
In Chapter 13, you’ll learn how the new Information Design Tool is different from
the Universe Design Tool, and how to perform the conversion from UNV to UNX.

“Comparing the Universe Design Tool

and Information Design Tool”
Contents

Index

The Authors

Christian Ah-Soon, Didier Mazoué, Pierpaolo Vezzosi

Universe Design with SAP BusinessObjects BI
The Comprehensive Guide
729 Pages, 2014, $79.95/€79.95
ISBN 978-1-59229-901-0

www.sap-press.com/3412
© 2016 by Rheinwerk Publishing, Inc. This reading sample may be distributed free of charge. In no way must the file be altered, or
individual pages be removed. The use for any commercial purpose other than promoting the book is strictly prohibited.
The Universe Design Tool and Information Design Tool share many concepts.
However, you must take some differences into consideration when converting
universes.

13 Comparing the Universe Design Tool

and Information Design Tool

Previous chapters have described the different capabilities of Information Design

Tool (IDT). IDT is the successor of the Universe Design Tool, so most concepts are
common to both tools, and IDT can be seen as a superset of the Universe Design
Tool. However, there are some slight differences you need to know about when
converting a universe created with the Universe Design Tool to the new universe
format if you expect the converted universe to behave like the original one. This
chapter compares the two tools on different topics:

EE The main workflows and capabilities

EE The connections created by the two tools
EE The data foundation and the database schema made of tables, joins, and so on
EE The business layer and its classes/folders and objects
EE The prompts/parameters and lists of values
EE The security proposed by the two tools
EE Some usability differences

Finally, the chapter describes how a universe is converted and how to perform
this conversion in IDT.

13.1 General

Table 13.1 describes the main differences between the Universe Design Tool and
IDT.

687
13 Comparing the Universe Design Tool and Information Design Tool Connections 13.2

Universe Design Tool Information Design Tool Universe Design Tool Information Design Tool

Generates universe (.unv) that can be Generates universe (.unx) that can be Can display values for only one table or Uses a common Show Values editor
consumed by the following: consumed by the following: one column at a time. The values are to display data from connections,
EE SAP Business­Objects Web Intelligence EE SAP Business­Objects Web Intelligence displayed in columns. tables, columns, query results, and so
on. This editor can display values for
EE SAP Crystal Reports 2013 EE SAP Crystal Reports for Enterprise
several tables or columns. It proposes an
EE SAP Business­Objects Explorer EE SAP Business­Objects Explorer advanced graphical display with a large
EE Query as a Web Service (relational only) number of supported charts and filtering
EE SAP Business­Objects Live Office, EE SAP Business­Objects Dashboards capabilities that can be used to profile
through SAP Business­Objects Web EE SAP Lumira (relational only) data.
Intelligence and Query as a Web EE SAP Predictive Analysis (relational Supports metadata exchange to Doesn’t support metadata exchange.
Service only) automatically create universes from
EE SAP Business­Objects Dashboard, third-party databases models or export
through Query as a Web Service universes to these models.
EE SAP Lumira
Can’t convert a universe based on a Supports the conversion of a universe
EE SAP Predictive Analysis relational source into a universe based on based on another database to a universe
SAP HANA. based on SAP HANA (as of SAP Business­
Doesn’t differ between authoring Separates the authoring and consumption
Objects BI 4.1).
and consumption resources; the only workflows. For authoring, the data
supported file is the universe that can be foundation and business layer are saved Proposes a Software Development Kit As of SAP Business­Objects BI 4.1, it
saved locally or exported to the Central in a local project. For consumption, the (SDK) that covers all Universe Design proposes an SDK that supports only
Management Server (CMS) repository. universe can be published locally or in Tool capabilities. simple workflows. Since its first release in
the CMS repository. SAP Business­Objects BI 4.0 SP4, this SDK
has been updated with new methods in
You connect to the CMS repository in You can access several CMS repositories
SAP Business­Objects BI 4.0 SP5 and SAP
the User Authentication dialog box. simultaneously. All sessions are managed
Business­Objects BI 4.1.
You can open only one session at a time. in a single location, the Repository
Before opening a new session, you must Resources view, where you can define Table 13.1  Workflow Comparison (Cont.)
close the previous one. and save predefined sessions.

Doesn’t have collaboration mode. Supports designers’ collaboration and

resource synchronization in shared 13.2 Connections
projects.
Table 13.2 compares the different connections supported by the Universe Design
Supports linked universes. Doesn’t support linked universes.
Tool and IDT.
Doesn’t support custom user attributes. Supports custom user attributes (as of
SAP Business­Objects BI 4.0 SP4).

Table 13.1  Workflow Comparison

688 689
13 Comparing the Universe Design Tool and Information Design Tool Connections 13.2

Universe Design Tool Information Design Tool Universe Design Tool Information Design Tool

Supports two local connection types: Supports only one local connection, the Supports connections created in SAP Doesn’t support connections created
EE Personal: Can be used only on the one you create in a local project. Business­Objects Data Federator XI 3.0. in SAP Business­Objects Data Federator
computer on which it was created. XI 3.0, but supports multisource data
foundations (as of SAP Business­Objects
EE Shared: Created locally on the
BI 4.0) and federated tables (as of
computer but can be used by all users.
starting from SAP Business­Objects BI
Supports a secured connection, which Supports a secured connection, which 4.1).
is the connection created in the CMS is the connection created in the CMS
Doesn’t support new connectivity Supports new connectivity types:
repository. repository. To reference a secured
supported by Connection Server. Hadoop, Web Service, OData, and so on.
connection, you must use a connection
shortcut. Supports the use of @variable in Doesn’t support the use of @variable
Supports relational connections based on Supports relational connections connection parameters. in connection parameters, except if used
Connection Server and in common with based on Connection Server and in in the BEGIN_SQL parameter, which can
IDT (interoperability). common with the Universe Design Tool be set in the data foundation or in the
(interoperability). business layer.

Supports SAP NetWeaver BW and SAS Multisource data foundation supports Relational connection, for which you Allows you to choose either local or
relational connections through SAP SAP NetWeaver BW or SAS relational have the Download connection server middleware to use a relational
Business­Objects Data Federator XI 3.0. connections based on the Federation locally right granted, uses local connection for which you have the
Query Server. These connections can only middleware. Download connection locally right
be created in the CMS repository. It isn’t granted.
possible to create them locally. Can’t copy a local connection into the Can publish a local connection into the
Supports also OLAP connection to SAP CMS repository. CMS repository and copy its parameters
NetWeaver BW. in this newly created secured connection.

Supports OLAP connections based Doesn’t support OLAP connections based You can navigate in the database In the connection editor, you can
on Connection Server created in the on Connection Server created in the structure but not in the database data. navigate in the database structure and
Universe Design Tool. Universe Design Tool. use the Show Values view to preview,
filter, and analyze data, and then display
Doesn’t support OLAP connections Supports OLAP connections created in
the data using charts.
created in IDT or CMC. IDT or CMC. These connections can be
used for multidimensional universes or You can send SQL queries to the You can run custom SQL queries directly
direct access (for SAP systems). database, but they are only validated and to a relational database or run custom
no data is returned. You can’t send direct MDX queries directly to an OLAP
Supports connections based on stored Doesn’t support connections based on
MDX queries. database.
procedures and Java beans. stored procedures and Java beans.
Table 13.2  Connection Support Comparison (Cont.)
Table 13.2  Connection Support Comparison

690 691
13 Comparing the Universe Design Tool and Information Design Tool Business Layer 13.4

13.3 Data Foundation Universe Design Tool Information Design Tool

In the Universe Design Tool, the data foundation doesn’t exist, but it can be seen as Doesn’t search text on the tables, joins, Proposes an advanced search where you
the database schema—the set of tables and joins—used in the universe. Table 13.3 and so on. can also select the table and column
types, views, and families to search.
compares the concepts supported by the Universe Design Tool for this underlying
model and data foundation created for relational universes in IDT. N/A Proposes enhanced capabilities for ease
of use: merge tables, highlight related
tables, data foundation overview while
Universe Design Tool Information Design Tool
zooming, comments, and so on.
The database schema can only be used in A data foundation can be reused by
Table 13.3  Data Foundation Comparison (Cont.)
one universe, unless you duplicate it. several different business layers and,
therefore, by several universes.

Displays the database schema as a whole. Supports data foundation views. 13.4 Business Layer
Doesn’t support table grouping and Supports families to organize tables and
colors. assign them a color. In the Universe Design Tool, the business layer doesn’t exist, but it can be seen
as the set of objects exposed by the universe to client tools. In the business layer,
Doesn’t support calculated columns. Supports calculated columns.
IDT proposes new concepts compared to the classes and objects supported in the
Defines context by explicitly adding all Defines contexts by adding only the Universe Design Tool. Table 13.4 lists these IDT enhancements.
joins that may contribute to the context. necessary joins. It’s no longer mandatory
to explicitly include or exclude all data
foundation joins. Universe Design Tool Information Design Tool

Generates only single-source universes. Supports relational multisource data Supports relational objects: dimensions, Supports the same relational objects that
Multisource is supported through a foundations. details, and measures organized in have been renamed into dimensions,
connection created in SAP Business­ classes. attributes, and measures. These objects
Objects Data Federator XI 3.0. are organized in folders.

Doesn’t support tables that query Supports federated tables (as of SAP Supports a flat representation of OLAP Supports multidimensional business
different data sources, unless they are Business­Objects BI 4.1). universe through the relational objects: layer and multidimensional objects:
defined in SAP Business­Objects Data dimensions, details, and measures. hierarchies, levels, calculated members,
Federator XI 3.0. Supports calculated measures with calculated measures, analysis dimensions,
restrictions. and named sets.
Can show the tables used by an object or Can show full dependencies between Supports full MDX expressions in these
the objects depending on a table. business layers, data foundations, multidimensional objects.
objects, tables, and columns.
Doesn’t take advantage of Proposes a Member Selector dialog box
Supports strategies. Doesn’t support strategies. multidimensionality of hierarchies in to select members in a multidimensional
Table 13.3  Data Foundation Comparison OLAP universes hierarchy and use OLAP operators.

Table 13.4  Business Layer Comparison

692 693
13 Comparing the Universe Design Tool and Information Design Tool List of Values and Parameters 13.5

Universe Design Tool Information Design Tool Universe Design Tool Information Design Tool

In an OLAP-generated universe, the In a multidimensional business layer Supports user object (also called user Does not support user object.
objects can be edited. created from an OLAP data source, defined object), used only by SAP
the generated objects, especially the Business­Objects Desktop Intelligence.
query that defines the object, can’t be
Universes are translated directly in the The data foundation and business
modified. However, you may add new
Translation Management Tool. layer are translated in the Translation
objects to the business layer.
Management Tool before publishing the
A WHERE clause can be added to an It is not possible to add a WHERE clause universe.
object in an OLAP universe. to an object in a multidimensional
Can’t save queries. Supports predefined queries; you can
universe.
create, save, and run queries in the
Only four object types are supported: More object types are supported: business layer.
character, date, long text, and number. Boolean, date, date/time, long text,
Support OLAP universes created on SAP Doesn’t support multidimensional
numeric, and string. Binary large objects
NetWeaver BW InfoProvider or BEx universes created on an SAP NetWeaver
(“blobs”) are also supported, but no
query. BW connection, but supports relational
client tools can take advantage of them
universes created on SAP NetWeaver BW
at this time.
InfoProviders. Client tools can directly
A folder name is unique in a universe. A folder name is unique only under its query SAP BEx queries.
parent folder.
Relational universes support hierarchies. Hierarchies have been renamed as
An object can have the Active or Hidden An object can have the Active, Hidden, navigation paths.
states. or Deprecated states.
The search in based only on object Also proposes an advanced search based
Doesn’t support measure details. Supports measure attributes. names. on object types.

Doesn’t support custom properties, Supports custom properties for the Table 13.4  Business Layer Comparison (Cont.)
except through the SDK. business layer, dimensions, attributes,
measures, filters, folders, and parameters.

Classes and objects are exposed as a Supports business layer views that may 13.5 List of Values and Parameters
whole in the universe. contain subset of folders and objects.
Views can be used in the business layer Among IDT changes, the list of values, prompts, and renamed parameters have
editor and also in the query panel. been completely redesigned to offer new capabilities and easier usability. Table
Classes and objects depend on the It’s possible to change the data
13.5 lists these enhancements.
database schema on which they have foundation on which a business layer
been created. relies. Universe Design Tool Information Design Tool

Filters in relational universes are defined Supports also business filters, where the Lists of values are only defined in an Lists of values are defined in a data
with an SQL expression. condition is expressed based on objects object, which can have only one list of foundation or a business layer. Their
of the business layer. values associated. editor contains a dedicated panel to
manage these lists of values.
Filters in OLAP universes are defined Business filters are the only filters
with an XML expression. supported in multidimensional universes. Table 13.5  List of Values and Prompt Comparison

Table 13.4  Business Layer Comparison (Cont.)

694 695
13 Comparing the Universe Design Tool and Information Design Tool Security 13.6

Universe Design Tool Information Design Tool Universe Design Tool Information Design Tool

A list of values can only be used in the The same list of values isn’t limited to In the @prompt function, the object is In the @prompt function, the object is
object where it’s defined. It isn’t possible a single object. It’s global to the data identified by its parent name and its identified by its full parent path and its
to use the same list of values for several foundation or business layer where it’s name. name.
objects. defined. It can be reused by several
objects, prompts, or filters. Prompts are identified by the question Parameters are identified by a name
prompted to the user. that can be different from the question
Supports only lists of values defined from Supports list of values defined from the prompted to the user. They can also have
the following: following: a description.
EE An object’s values (by default) EE An object values (except if it’s defined
Prompts can only be answered by the Supports parameters prompted to users
EE The query panel in a data foundation). Object values
user (prompt to user). and also parameters with preset values.
can be retrieved from the following:
EE The query panel Proposes a wizard to create @prompt The wizard is no longer available to
expressions. generate @prompt expressions. The
EE A custom hierarchy
editor is available to create parameters
EE A static list only.
EE An SQL expression
Supports cascading prompts. Supports cascading and hierarchical
Uses an object to attach a list of values to Can directly attach a list of values to parameter dependencies.
a prompt or a filter. a prompt, a parameter, a filter, or an
object. The @prompt function supports The @prompt function supports
alphanumeric, numeric, and date prompt. alphanumeric, numeric, date types, and
If the list of values is defined with several If the list of values is defined with several K-prompts, which return a not-quoted
columns, only the first column is used to columns, you can define which column string to give more flexibility when
return values. returns values. Furthermore, if the list concatenating strings in an expression.
of values is re-used in several places,
you can select for each case a different Using a key to compare values is named Supports the same option, but it has
column to use. the Primary Key option. been renamed as Index Aware Prompt.

Supports cascading lists of values. Supports cascading and hierarchical lists Only OLAP universe supports optional Relational and multidimensional
of values. prompts. universes support optional prompts used
in business filters.
Can’t use lists of values content in an Supports the @execute function to
Table 13.5  List of Values and Prompt Comparison (Cont.)
SQL script. return the list of values content in an SQL
script.

Prompts are expressed using the Supports the same @prompt function 13.6 Security
@prompt built-in function. but also a new object called parameter.
Parameters are also used to prompt
In IDT, security profiles are the equivalent of the Universe Design Tool access
values, but are simpler to create, richer,
restrictions. However, they have been extended. Let’s see how they can compare
and can be reused.
with one another, in terms of their functional behavior and aggregation as well as
Table 13.5  List of Values and Prompt Comparison (Cont.) their user interface.

696 697
13 Comparing the Universe Design Tool and Information Design Tool Security 13.6

13.6.1 Access Restrictions and Security Profiles (Relational Universe) Universe Design Tool Information Design Tool
In IDT, access restrictions have been replaced and extended by data security profiles Rows access restriction doesn’t Supports an alias table and derived table as the
and business security profiles. Table 13.6 points out the differences between the support an alias table or derived conditional table for the Rows data security
two concepts for a relational universe. table as the conditional table. profile (as of SAP Business­Objects BI 4.0 SP4).

Supports an alias table as the Supports an alias table as the source table only
Universe Design Tool Information Design Tool source or replacement table in the Tables data security profile (as of SAP
in the Table mapping access Business­Objects BI 4.0 SP4).
Supports access restrictions to Supports data and business security profiles:
restriction.
secure universes: Connection, EE Connections, SQL, Controls, Rows, and
SQL, Controls, Objects, Rows, Tables data security profiles are the equivalent Supports free text for the Supports only the data foundation table as a
and Table Mapping. of Connection, SQL, Controls, Rows, and name of the replacement table replacement table in the Tables data security
Table Mapping access restrictions. in the Table mapping access profile.
EE Create Query and Display Data business restriction. It’s no longer possible to type free text as the
security profiles are the equivalent of objects replacement table, and thus define the dynamic
access restriction. The first secures objects and table (using @prompt or @variable).
views in the query panel, whereas the second
Supports @variable use in Supports @variable use in the Rows data
secures objects that retrieve data.
the Rows access restriction. It security profile and Filters business security
They have been adapted to also support can substitute for predefined profile. It can substitute for predefined parameters
multisource universes. parameters. or custom user attributes.
The Filters business security profile can also
Table 13.6  Relational Universe Security Comparison (Cont.)
be used to filter data but through conditions
expressed on business layer objects. Such a filter
is always applied to the query, while a Rows data
13.6.2 Access Restrictions and Security Profiles (OLAP Universe)
security profile is added only if its conditional
table is used in the query. In the Universe Design Tool, the access restrictions you can define for an OLAP
Supports the Limit size of long Doesn’t support this parameter anymore in the universe are a limited subset of the access restrictions types supported by relational
text objects to parameter in Controls data security profile. Other parameters universes. Indeed, they secure generic database concepts without being specific to
controls access restriction. are equivalent. relational databases: connection, controls, and objects.
Supports the Warn Cartesian Doesn’t support this option anymore in the SQL IDT doesn’t convert the OLAP universes created with the Universe Design Tool.
product option in the SQL data security profile. However, the multidimensional universes created in IDT can be secured by busi-
access restriction.
ness security profiles. Table 13.7 compares the security concepts enforced by the
Objects access restriction Uses the Create Query and Display Data two tools.
is used to deny objects. By business security profiles to grant or deny objects.
default, a user can see all When a data security profile is assigned to a user, Universe Design Tool Information Design Tool
objects and classes in the all objects and views are, by default, denied to
universe, except the ones him. Create Query and Display Data business Supports the Connection Supports the Connection business security
denied by the Objects access security profiles are used to grant or deny objects access restriction. profile for multidimensional universes (as of SAP
restriction. or views. Business­Objects BI 4.1).

Table 13.6  Relational Universe Security Comparison Table 13.7  OLAP and Multidimensional Universe Security Comparison

698 699
13 Comparing the Universe Design Tool and Information Design Tool Security 13.6

Universe Design Tool Information Design Tool Universe Design Tool Information Design Tool

Supports the Controls access Doesn’t support the query parameters For access restriction aggregated by For security profiles aggregated by
restriction. replacement. priority, the value defined is the one priority, the value to apply is always the
assigned to the user, if any. Otherwise, one defined in the data security profile
Supports the Objects access Supports business security profiles:
the access restriction is applied to the with the highest priority among the ones
restriction to secure universe EE Create Query, to secure the business layer group with the highest priority. that apply to the user.
objects. objects and views
Controls and SQL access restrictions Controls and SQL data security profiles
EE Display Data, to secure the objects to query
can only be aggregated through the can be aggregated through the data
data
group priority. security profiles’ priority and also through
Objects access restriction Create Query and Display Data business security the AND, ANDOR, or OR algorithms.
is used to deny objects. By profiles can be used to grant or deny objects. The
Objects access restrictions can only be The Create Query business security
default, a user can see all first secures objects and views in the query panel,
aggregated with the AND operator. profile and Display Data business
objects and classes in the whereas the second secures objects that retrieve
security profile can independently be
universe, except the ones data.
aggregated through the AND, ANDOR,
denied by the objects access By default, a user can see all objects and views or OR algorithms.
restrictions that apply to him. in the universe. But if a business security profile
applies to him, then all objects and views are Rows access restrictions can be Rows data security profiles can be
denied to him. You can then use these business aggregated through the AND or ANDOR aggregated through the AND, ANDOR,
security profiles to grant or deny the user universe algorithms. or OR algorithms
objects and views. Doesn’t support security filters based on The Filters business security profiles for
Can’t filter data returned by an The Filters business security profile can secure objects. relational or multidimensional universes
OLAP universe. hierarchies members. can be aggregated through the AND,
ANDOR, or OR algorithms. For relational
Table 13.7  OLAP and Multidimensional Universe Security Comparison (Cont.) universes, the WHERE clauses are
merged using AND or OR operators. For
multidimensional universes, the hierarchy
13.6.3 Aggregation
members used to query data is computed
In addition to the differences in the access restriction and security profiles behav- though the union or intersection
ior, IDT offers more options to aggregate security profiles. These differences are operators.

listed in Table 13.8. Table 13.8  Security Aggregation Comparison (Cont.)

Universe Design Tool Information Design Tool 13.6.4 Security Editor

Only one access restriction can be Several data and business security profiles
IDT proposes the Security Editor which is dedicated to creating, editing, assign-
assigned to a user or a group. can be assigned to a user or a group.
ing, and managing security profiles. This editor is more complete and offers more
Defines access restriction priority Defines priority at the security profile capabilities than the security management dialog box you can use in the Universe
through groups. level.
Design Tool. The main differences between the two tools are listed in Table 13.9.
Table 13.8  Security Aggregation Comparison

700 701
13 Comparing the Universe Design Tool and Information Design Tool Security 13.6

Universe Design Tool Information Design Tool Universe Design Tool Information Design Tool

Must import the universe to edit its Can edit a universe security profiles Check universe integrity N/A
access restrictions and the user(s) and/or and the user(s) and/or group(s) they are
Refresh structure window N/A
group(s) they are assigned to. assigned to without importing it.
Use table browser N/A
Can display and manage the access Displays in the Security Editor an
restrictions of only one universe at a overview of all universes in the CMS Link universe N/A
time. repository and all of their security
profiles. N/A Use shared projects

Furthermore, the Security Editor can N/A Save for all users
display all universes that have security
profiles explicitly assigned to a user or a N/A Compute statistics
group. Table 13.10  Application-Specific Rights Comparison (Cont.)
Can’t run secured queries. Can run a query from a universe
published in the CMS repository. Security Universe Rights
assigned to the connected user applies.
The specific design rights for universes created in IDT and the Universe Design Tool
Can’t display inherited security profiles. Can display security profiles inherited by differ. Table 13.11 compares and shows the equivalencies between these rights.
a user or a group.

Table 13.9  Security Editor Comparison Universe Design Tool Information Design Tool

Create and edit queries based on Create and edit queries based on the
13.6.5 Central Management Console Rights universe universe

Both applications can benefit from the BI platform framework and define some Edit access restrictions Edit security profiles
security rights. These rights slightly differ, as described next. Assign security profiles

Data access Data access

Application Rights
Unlock universe N/A
The authoring workflows in the Universe Design Tool and IDT are different. This
affects the specific rights supported by the two tools. Table 13.10 compares and New list of values N/A

shows the equivalencies between these rights. Print universe N/A

Show table or object values N/A

Universe Design Tool Information Design Tool
N/A Retrieve universe
Apply universe constraints Administer security profiles
Table 13.11  Universe-Specific Rights Comparison
N/A Publish universes

N/A Retrieve universes

13.6.6 Connection Rights
Create, modify, or delete connections Create, modify, or delete connections
In the Universe Design Tool, relational universes are created on top of relational con-
Table 13.10  Application-Specific Rights Comparison nections that are also supported by IDT. During conversion in the CMS repository,

702 703
13 Comparing the Universe Design Tool and Information Design Tool Universe Conversion 13.8

these connections aren’t converted, and their general and custom rights are similarly
Universe Design Tool Information Design Tool
enforced in the two tools.
Supports the options to change Doesn’t propose to modify the shape of joins
OLAP connections created in the Universe Design Tool aren’t supported by IDT, the shape of join endpoints. endpoints, but the Preferences dialog box
and there is no conversion path between these connections and the OLAP ones proposes several other appearance options, such
supported by IDT. as the join lines style.

Can automatically save an Doesn’t support auto-save for resources.

edited universe.
13.7 Miscellaneous
Supports password changes. Doesn’t support password changes, except if you
must change it when you first log in to the CMS
In addition to the functional changes described previously, IDT also presents some
repository.
differences in usability and its framework compared to the Universe Design Tool.
These main changes are listed in Table 13.12. Supports passwords to protect Doesn’t support passwords to read and write
universe read and write. the universe in IDT. If retrieved from a CMS
repository, the authoring resources can be
Universe Design Tool Information Design Tool protected by authenticating against the CMS
Has only one menu bar and Displays in the menu bar and toolbar only the repository.
toolbar. main commands. Most commands are contextual Table 13.12  Additional Differences (Cont.)
and displayed in each editor and view toolbar.

Supports a Scan and Repair Supports the Check Integrity command you Even with this list of differences, universes created in both tools remain similar
command. can run on different locations to validate the and answer the same objectives and requirements. Universes created with IDT
following: propose more capabilities than universes created with the Universe Design Tool,
EE A data foundation or business layer, before which brings universe conversion to the table. Conversion of the universes cre-
saving or publishing them
ated in the Universe Design Tool to the IDT format is a straightforward process.
EE A published universe and its security
Each rule result status can be categorized as an
error, a warning, or information.
13.8 Universe Conversion
Copying objects between two We don’t recommend that you copy objects
universes works perfectly. between two data foundations or business layers IDT can convert a universe created with the Universe Design Tool to save it in the
because it may lead to erroneous results. new file format supported by IDT. You may also use the semantic layer Java SDK to
Can create .pdf reports that Can create .pdf, .html, or .txt reports that run this conversion, especially if you have a large number of universes to convert,
document the universe. document the business layer or data foundation. because IDT can only convert one universe at a time.

Supports a split screen for the Doesn’t support a split screen, but different This section first lists the universes that can be converted or not before describing
tables and joins schema. editors can be organized and displayed side by how this conversion differs between local and secured universes, especially for
side.
connections. The universe conversion is covered next, including the specific case
Supports only online help. Supports online help, context help, cheat sheets, of linked universes. Finally, the section ends by describing the security conversion:
and a Welcome page. rights, access restrictions, and object access levels.
Table 13.12  Additional Differences

704 705
13 Comparing the Universe Design Tool and Information Design Tool Universe Conversion 13.8

13.8.1 Universe Conversion Scope 13.8.2 Local versus Secured Universe Conversion
The following universes created in the Universe Design Tool can’t be converted IDT can convert both local relational universes and universes saved in the CMS
because IDT doesn’t support them: repository. If the universe is local, then the conversion also generates the differ-
ent resources in a local project. The relational personal or shared connection used
EE Relational universes based on a stored procedure or on a Java bean.
by the source universe is converted into the equivalent local connection in IDT.
EE Relational universes based on an SAP Business­Objects Data Federator XI  3.0 The same parameters are used to recreate the local connection embedded in the
connection. converted universe, as shown in Figure 13.1.
EE OLAP universes based on an OLAP connection created with the Universe Design
Tool. Only relational universes can be converted, and the remainder of this sec-
tion focuses only on relational universe. File system Local project

EE OLAP connections created in the Universe Design Tool aren’t converted because
OLAP universes aren’t converted by IDT. UNV

Convert
Oracle OLAP 9i and Oracle OLAP 10g
RDBMS
Relational universes based on a relational connection to Oracle OLAP 9i and Oracle
OLAP 10g can be converted by IDT, but they use hints in the joins between tables that
are not supported in IDT data foundation, so queries on the converted universe fail.

Figure 13.1  Local Universe Conversion

Universe conversion generates a relational universe that complies with the differ-
ent layers in IDT. The converted universe contains the three resources described You can republish the generated resources to generate a local .unx universe that
in previous chapters: can be consumed by client tools.
EE Connection or connection shortcut in case of a secured universe In a local conversion, there are no access restrictions or security rights to convert. A
EE Data foundation local conversion can convert universes created in previous releases (SAP Business­
EE Business layer Objects XI R2 or SAP Business­Objects XI 3.x), whereas a secured conversion must
have a universe created or upgraded in a CMS repository of a SAP Business­Objects
If the universe is a secured universe saved in the CMS repository, its security is BI 4.x system.
converted as well. Security in IDT reuses and extends the Universe Design Tool’s
security, so the conversion is done with respect to the original universe’s security. If the universe is secured, then the conversion generates the converted universe in
the same CMS repository. This universe reuses the same secured relational connec-
tion used by the source universe, as shown in Figure 13.2. The generated universe
SAP Business­Objects Web Intelligence Change Source
contains a connection shortcut to this secured connection.
Converting a universe doesn’t change the reports that use it. For example, SAP Business­
Objects Web Intelligence supports universes created with both tools. After the universe
conversion, you need to explicitly change the original universe used by Web Intelligence
documents so they can access the converted universe. Otherwise, they keep consuming
the universe created with the Universe Design Tool.

706 707
13 Comparing the Universe Design Tool and Information Design Tool Universe Conversion 13.8

Lists of values associated with objects are converted as explicit lists of values based
CMS Repository on business layer objects in the business layer. These new lists of values are based
on the query panel and are attached to their corresponding objects. But lists of
.unv .unx values using custom SQL are converted into list of values based on business layer
Convert
objects with custom SQL.

RDBMS
Universe parameters are converted and set either in the data foundation or in the
business layer, depending on the place where they were defined in the original
universe.

Figure 13.2  Secured Universe Conversion 13.8.4 Linked Universe

Linked universes used in the Universe Design Tool to reference a core universe in
The conversion of the universe itself is done through the creation of the data foun-
a derived universe are no longer supported in IDT, but they can be converted by
dation and business layer. These resources are converted in the same manner in a
IDT. During the conversion, the core universe is explicitly copied in the converted
local conversion or a conversion in the CMS repository.
derived universe, as shown in Figure 13.3.

The converted universes are still working and expose the same list of objects as
13.8.3 Data Foundation and Business Layer
the source universe. The dynamic link provided by the core universe is no longer
When a universe is converted, the created data foundation and business layer are provided in the converted universes, so you can’t make changes in the core that
defined to behave as in the original universe. A single-source data foundation is are inherited by all derived universes. Such changes must be explicitly made in
created for the converted universe. As shown in Chapter 5, Section 5.1, this data every converted universe.
foundation can’t be enabled for multisource. The database schema used in the uni-
verse is recreated in this data foundation. The tables, including alias and derived
tables, their columns, the joins that link them, and the contexts are recreated in
.unv .unx
this data foundation with the same properties. This data foundation contains only Convert Core
Derived
one view—the master view. The conversion also creates a business layer that relies
on this data foundation. .unv
Core
.unv .unx
The converted business layer is created with only one business layer view. The Convert
Core
Derived
objects (dimensions, measures, details, filters) and classes from source universe
are converted in the converted business layer as objects (dimensions, measures, Figure 13.3  Linked Universes Conversion
attributes, filters) and folders with the same properties: name, description, SELECT
and WHERE clauses, extra tables, translations, and so on. These objects are organized Although their behaviors are different, reusability can also be achieved in IDT by
in the same folders in which the corresponding objects are organized in the source doing the following:
universe.
EE Sharing a data foundation with several business layers
Prompts can be either converted as @prompt or as parameter objects. You select
EE Creating one single universe with the following:
this option in the conversion wizard (see Section 13.9).

708 709
13 Comparing the Universe Design Tool and Information Design Tool Universe Conversion 13.8

EE The folders and objects of the core universe and its derived universes In IDT, however, priority is no longer defined at the group level but at the data
EE Several business layer views, one for each derived universe, each view con- security profile level. If the access restriction is assigned to more than one user
taining the objects and folders of this derived universe before the conversion or group, and if this conversion doesn’t allow the converted security to properly
reflect the same security as in the source universe, then the access restriction is
converted into several data security profiles, one for each user or group.
13.8.5 Universe Rights Conversion
The names of these data security profiles are the names of the access restriction fol-
When a secured universe is converted, its security rights settings are also converted
lowed by the user or group names: <Access Restriction Name>_<user or group name>.
to secure as identically as possible the converted universe. Its rights access levels
The definitions of these data security profiles are all identical and are directly
and advanced security rights settings are recreated and assigned to the converted
retrieved from the access restriction definitions (connection, controls, SQL, rows,
universe for the same groups and users.
and table mapping security). These data security profiles are assigned to the same
Because the rights differ between the two universe types, a mapping is done users and groups as their corresponding access restrictions and are prioritized using
between them during conversion: the group priority in the Universe Design Tool.

EE The value for all general Create and edit queries based on this universe and If the access restriction defines the objects access restriction, then a business security
Data access rights are identically set. profile is created and attached to the converted universe. This business security
profile has the same name as the access restriction, and it defines both Create
EE The Edit access restrictions right is no longer supported by IDT, but its value
Query and Display Data business security profiles to deny the same objects denied
is set to Edit security profiles and Assign security profiles rights.
in the objects access restriction:
EE The following rights are no longer supported by IDT, thus their values aren’t
kept during conversion: Unlock universe, New list of values, Print universe, EE In Create Query, the master view is granted and all objects and classes denied
and Show table or object values. in the access restriction are denied in the security profile.
EE In Display Data, the All objects shortcut is granted to grant all objects by
13.8.6 Access Restriction Conversion default. Furthermore, all objects and classes denied in the access restriction are
also denied in the security profile.
The security defined in IDT is a super-set of the security set in the Universe Design
Tool and the access restriction conversion is done by mapping its parameters to This business security profile is assigned to the same users and groups as the access
equivalent security profiles. However, the slight differences between access restric- restriction.
tions and security profiles require some adaptation during the conversion phase to
get the same behavior applied to the converted universe as in the original universe. 13.8.7 Access Restriction Aggregation Option Conversion
For each universe to convert, each access restriction generates one or several data When the universe is converted, its aggregation options are converted with these
security profiles and/or a business security profile. By default, a Universe Design rules:
Tool access restriction is converted into a data security profile and assigned to the
EE The Controls and SQL data security profile aggregation option is set to Prior-
same user and group. The name of this data security profile is the name of the
ity because it’s the only one available for controls and SQL access restriction.
access restriction. The definition of this data security profile is directly retrieved
from the access restriction definition (connection, controls, SQL, rows, and table EE The Rows data security profile aggregation option is defined from the value of
mapping security). the original universe rows access restriction aggregation option:

710 711
13 Comparing the Universe Design Tool and Information Design Tool Converting Universes in Information Design Tool 13.9

EE Very restrictive (AND) if it’s AND 2. Click the Select .unv Universe from the Local File System button ( ) to
EE Moderately restrictive (ANDOR) if it’s ANDOR select the universe to convert:
EE The Create Query and Display Data business security profile aggregation option EE In the Open dialog box, navigate in the file system to select the universe to
is set to Very restrictive (AND) because it’s the only one available for the objects convert, and then click OK.
access restriction aggregation option in the Universe Design Tool. EE The dialog box closes and the universe name to convert is displayed in the
EE The Filters business security profile aggregation mode is set to Very restric- Select the .unv Universe to Convert text field. As shown in Figure 13.4,
tive (AND). the dialog box is updated. Enter the destination folder for the converted
resources.

13.8.8 Object Access Level

The Universe Design Tool supports object access level for any business objects
defined in a universe (measure, dimension, and detail). IDT also supports them
for any business objects defined in a business layer of a universe (measure, dimen-
sion, attribute, etc.).

The different access levels are identical for both tools: public, controlled, restricted,
confidential, and private. The user access level you define in the CMC can be iden-
tically defined for a universe defined with the Universe Design Tool or a universe
defined with IDT. User access levels inherited by a user from the groups the user
belongs to are also aggregated identically in the Universe Design Tool and IDT.

When a universe is converted, object access levels that are object properties are Figure 13.4  Convert a .UNV Universe Dialog Box for a Local Conversion
converted as well. The user access levels defined for this universe are also recreated
for the converted universe, for the same user(s) and group(s). 3. Click the Browse button ( ) located near the Destination Local Project
Folder text field to select the destination folder:
EE In the Select Local Project dialog box, select a project or a folder in a local
13.9 Converting Universes in Information Design Tool project, and then click OK.

Universe conversion can be run from IDT. This process converts both local uni-
EE The Select Local Project dialog box closes, and the selected project or folder
verses and universes saved in the CMS repository. We describe both workflows is displayed in the Destination Local Project Folder text field.
in the next sections. 4. To convert the @prompt expressions as parameter objects, select the Automati-
cally convert @Prompt expressions into universe named parameters check-
box.
13.9.1 Converting a Local Universe
5. Click OK to start the conversion. The converted connection, data foundation,
To convert a local universe, follow these steps:
and business layer are generated in the selected folder or project.
1. In the menu bar, select File • Convert Universe to open the Convert .unv
Universe dialog box.

712 713
13 Comparing the Universe Design Tool and Information Design Tool Summary 13.10

13.9.2 Converting a Secured Universe

The conversion of a secured universe is quite similar to a local universe; except
the security that is converted with the universe. Before starting the conversion,
make sure you have the Add objects to folder right for the destination folder
so you can create the converted universe. Then, to convert a secured universe,
follow these steps:

1. In the menu bar, select File • Convert Universe to open the Convert .unv
Universe dialog box.
2. Click the Select .unv Universe from a Repository button ( ) to select the
universe to convert:
EE In the Open Session dialog box, create a new session or open a predefined
one (see Chapter 3, Section 3.4), and then click OK.
EE In the universe browser dialog box, navigate in the Universes folder in the
CMS repository, select the universe to convert, and click OK.
EE The dialog box closes, and the universe name to convert is displayed in the Figure 13.5  Convert a .UNV Universe Dialog Box for a Conversion in the Repository
Select .unv Universe to Convert text field.
5. To convert @prompt expressions as parameter objects, select the Automatically
3. Click the Browse button ( ) located near the Destination Repository Folder
convert @Prompt expressions into universe named parameters checkbox.
text field to enter the destination folder:
6. Click OK to start the conversion. The converted universe is generated in the
EE In the universe browser dialog box, navigate in the Universes folder in the
selected folder in the CMS repository. It has the same name as the original,
CMS repository, select the destination folder, and then click OK.
except for its .unv extension that is replaced by .unx. If you’ve opted to retrieve
EE The dialog box closes, and the folder name is displayed in the Destination the converted universe at the same time, its resources are also generated in the
Repository Folder text field. local project folder you’ve selected.
4. You may optionally choose to retrieve the converted universe after the conver-
To convert a secured universe, you can also directly right-click the universe in the
sion is done:
Repository Resources view. The Convert .unv Universe dialog box opens, where
EE Click the Browse button ( ) near the Destination Local Project Folder you can define the same options previously described.
text field to open the Select Local Project dialog box.
EE Select the project or a folder in a local project, and then click OK.
EE The Select Local Project dialog box closes, and the selected project and
13.10 Summary
folder are displayed in the Destination Local Project Folder text field, as
Information Design Tool is the Universe Design Tool successor, and it proposes
shown in Figure 13.5.
several major changes and enhancements: in the workflows, in the authoring
EE To remove security from the extracted resources (see Chapter 9, Section 9.4), resources, and in their capabilities. Some features, however, aren’t identically sup-
select the Save for all users checkbox. ported, and some are not supported at all. For this reason, assessing the features

714 715
13 Comparing the Universe Design Tool and Information Design Tool

you use is important if you plan to move your existing universes created with the
Universe Design Tool to universes compatible with IDT.

When you’re ready to convert, you can use IDT to run this conversion. IDT can
convert both local and secured universe. In the latter case, security is converted
as well.

716
Contents

Preface  ....................................................................................................... 23
Acknowledgments  ...................................................................................... 27

1 Introduction to the Semantic Layer  .......................................... 29

1.1 What Is a Semantic Layer?  ........................................................... 29

1.2 A Well-Designed Semantic Layer  ................................................. 33
1.2.1 Characteristics  . ............................................................... 33
1.2.2 Designing a Semantic Layer  ............................................. 34
1.3 Semantic Layer Components  ........................................................ 35
1.3.1 The Universe  ................................................................... 36
1.3.2 The Information Engine  . ................................................. 38
1.3.3 Information Design Tool  ................................................. 40
1.3.4 Client Tool Technology  ................................................... 40
1.4 Deploying the Semantic Layer in SAP Business­Objects BI 4.0  ....... 42
1.5 SAP Business­Objects BI Applications that Consume the
Semantic Layer  ............................................................................ 44
1.5.1 SAP Business­Objects Web Intelligence  ............................ 44
1.5.2 SAP Crystal Reports for Enterprise  ................................... 46
1.5.3 SAP Business­Objects Dashboards  .................................... 47
1.5.4 SAP Business­Objects Explorer  ......................................... 48
1.5.5 SAP Lumira  ..................................................................... 50
1.5.6 SAP Predictive Analysis  ................................................... 52
1.6 Summary  ..................................................................................... 53

2 Introduction to Information Design Tool  .................................. 55

2.1 Installing Information Design Tool  ............................................... 56

2.2 Getting Started  ............................................................................ 58
2.2.1 Welcome Page  ................................................................ 58
2.2.2 New Universe Wizard   . ................................................... 60
2.3 Information Design Tool Interface  . .............................................. 62
2.3.1 Menu and Toolbar  .......................................................... 63
2.3.2 Working with Views  . ...................................................... 64
2.3.3 Working with Editors  ...................................................... 65

7
Contents Contents

2.4 Help  ............................................................................................ 67 3.4.1 Opening a Session  . ......................................................... 102

2.4.1 Context-Sensitive Help  .................................................... 67 3.4.2 Using the Session  ............................................................ 103
2.4.2 Cheat Sheets  ................................................................... 68 3.4.3 Creating a Predefined Session  ......................................... 104
2.4.3 Online Tutorials  .............................................................. 70 3.4.4 Opening a Predefined Session   ........................................ 105
2.5 Preferences  .................................................................................. 71 3.4.5 Closing a Session  ............................................................. 106
2.5.1 Business Layer Editor  ...................................................... 72 3.4.6 Deleting a Predefined Session  ......................................... 106
2.5.2 Check Integrity  . .............................................................. 72 3.5 Shared Projects  ............................................................................ 106
2.5.3 Data Foundation Editor  . ................................................. 73 3.5.1 Shared Project Definition  ................................................ 107
2.5.4 Languages  ....................................................................... 76 3.5.2 Synchronizing   . ............................................................... 107
2.5.5 Online Tutorials  .............................................................. 76 3.5.3 Security  . ......................................................................... 108
2.5.6 Secured Connections  . ..................................................... 76 3.5.4 Locking and Unlocking Resources  ................................... 109
2.5.7 Show Values  ................................................................... 76 3.6 Managing Shared Resources  ........................................................ 109
2.6 Data Preview  ............................................................................... 77 3.6.1 Creating a Shared Project  ................................................ 109
2.6.1 Raw Data Tab  ................................................................. 79 3.6.2 Opening a Shared Project  . .............................................. 113
2.6.2 Distinct Values Tab  ......................................................... 81 3.6.3 Synchronizing Resources  ................................................. 113
2.6.3 Analysis Tab  .................................................................... 82 3.6.4 Locking and Unlocking Resources  ................................... 114
2.7 Summary  ..................................................................................... 83 3.6.5 Deleting a Shared Project  ................................................ 114
3.7 Summary  ..................................................................................... 115

3 Local and Shared Projects  ......................................................... 85

4 Connecting to Data Sources  ...................................................... 117
3.1 Authoring Resources in Local Project  ........................................... 86
3.1.1 Local Project and File System  .......................................... 86 4.1 Data Sources Typology  ................................................................ 117
3.1.2 Local Project Lifecycle  ..................................................... 89 4.1.1 Relational Connections   .................................................. 118
3.1.3 Resource Dependencies   ................................................. 90 4.1.2 Relational Connections to SAP NetWeaver BW
3.2 Managing Local Projects  .............................................................. 91 and SAS   ......................................................................... 121
3.2.1 Creating a Local Project  . ................................................. 91 4.1.3 OLAP Connections  .......................................................... 121
3.2.2 Closing and Opening a Local Project   .............................. 92 4.2 Connection Persistence  . .............................................................. 123
3.2.3 Managing Resources and Folders  .................................... 92 4.2.1 Secured Connections  . ..................................................... 124
3.2.4 Filtering Resources in Projects  ......................................... 94 4.2.2 Connection Shortcuts   ..................................................... 125
3.2.5 Viewing Local Dependencies  . ......................................... 95 4.2.3 Local Connections  ........................................................... 126
3.2.6 Deleting a Local Project   ................................................. 95 4.2.4 Connection Usages  . ........................................................ 127
3.3 CMS Repository  ........................................................................... 96 4.3 Authentication Modes  ................................................................. 127
3.3.1 Session to CMS Repository  . ............................................ 96 4.3.1 Fixed Credentials  . ........................................................... 128
3.3.2 Predefined Sessions  . ....................................................... 98 4.3.2 Credentials Mapping  ....................................................... 129
3.3.3 Authentication Modes  .................................................... 99 4.3.3 Single Sign-On  ................................................................ 130
3.3.4 Folders and Objects   ....................................................... 100 4.3.4 Using Credentials Mapping for Single Sign-On  ................ 132
3.3.5 Predefined Groups  .......................................................... 101 4.4 Client and Server Deployment  ..................................................... 133
3.4 Managing Sessions  . ..................................................................... 102 4.4.1 Middleware and Drivers  .................................................. 133

8 9
Contents Contents

4.4.2 Connection Server  . ......................................................... 134 5.4.1 Create a Derived Table in the Data Foundation
4.4.3 Download Connection Locally  . ....................................... 135 Schema  ........................................................................... 185
4.4.4 Relational Connections to SAP NetWeaver BW 5.4.2 Create a Derived Table from a Selected Table  . ................ 189
and SAS  .......................................................................... 136 5.4.3 Replace a Table with a New Derived Table  . .................... 189
4.4.5 OLAP Connections  .......................................................... 136 5.4.4 Merge Multiple Tables and Derived Tables in a
4.5 Connection Parameters  ................................................................ 137 New Derived Table  ......................................................... 190
4.5.1 Authentication and Data Source Parameters  . .................. 137 5.5 Calculated Columns  ..................................................................... 191
4.5.2 Connection Server Configuration Parameters  . ................. 138 5.6 Solving Loops (Alias Tables, Contexts, Shortcut Joins)  .................. 194
4.5.3 Connection Server Custom Parameters  ............................ 139 5.6.1 Resolving Loops by Eliminating Joins  . ............................. 196
4.5.4 Configuration Files  .......................................................... 140 5.6.2 Resolving Loops with Alias Tables  ................................... 197
4.6 Managing Connections  ................................................................ 141 5.6.3 Resolving Loops with Contexts  . ...................................... 198
4.6.1 Creating a Connection in a CMS Repository  .................... 142 5.6.4 Create and Edit Contexts  . ............................................... 200
4.6.2 Creating a Local Connection  . .......................................... 145 5.6.5 Shortcut Joins  ................................................................. 203
4.6.3 Publishing a Connection  . ................................................ 146 5.6.6 Detection Tools  .............................................................. 204
4.6.4 Creating a Connection Shortcut  . ..................................... 146 5.7 Chasm Traps and Fan Traps  . ........................................................ 206
4.6.5 Editing a Connection  . ..................................................... 147 5.7.1 Fan Traps  ........................................................................ 206
4.6.6 Switching Server/Client Middleware  . .............................. 148 5.7.2 Chasm Traps  ................................................................... 209
4.6.7 Testing a Connection  ...................................................... 149 5.8 List of Values  ............................................................................... 212
4.7 Data Preview  ............................................................................... 150 5.8.1 Static List of Values  ......................................................... 213
4.7.1 Relational Database  ........................................................ 150 5.8.2 List of Values Based on Custom SQL  ............................... 215
4.7.2 OLAP Connections  .......................................................... 152 5.8.3 List of Values Parameters and Options  ............................ 216
4.8 Summary  ..................................................................................... 155 5.8.4 Customize List of Values Columns  ................................... 217
5.9 Parameters  .................................................................................. 218
5.9.1 Parameter Definition  ....................................................... 219
5 The Data Foundation  ................................................................. 157
5.9.2 Prompt Text  .................................................................... 220
5.1 Creating a Data Foundation  ......................................................... 159 5.9.3 Data Type   ...................................................................... 220
5.2 Identifying Tables, Columns, and Keys  ......................................... 162 5.9.4 Allow Multiple Values  ..................................................... 221
5.2.1 Database Catalog Browser  . ............................................. 163 5.9.5 Keep Last Values  ............................................................. 221
5.2.2 View Table Data and Information  . .................................. 165 5.9.6 Index Aware Prompt  ....................................................... 221
5.2.3 Insert Tables in the Data Foundation  . ............................. 166 5.9.7 Associated List of Values  ................................................. 221
5.2.4 Search and Filter  ............................................................. 168 5.9.8 Select Only from List  ....................................................... 222
5.3 Identifying Joins, Keys, and Cardinalities  ...................................... 169 5.9.9 Set Default Values  . ......................................................... 222
5.3.1 Joins and Cardinalities  ..................................................... 169 5.9.10 Parameter Custom Properties  .......................................... 222
5.3.2 Join Editor  ...................................................................... 172 5.9.11 Parameters Usage  . .......................................................... 223
5.3.3 Join Types  ....................................................................... 175 5.10 The SQL Editor  ............................................................................ 223
5.3.4 Detect Joins, Keys, and Cardinalities  ............................... 178 5.11 Built-in Functions  ........................................................................ 226
5.3.5 Joins Strategy  .................................................................. 183 5.11.1 @derivedtable  ................................................................ 226
5.4 Derived Tables  . ........................................................................... 184 5.11.2 @execute  ....................................................................... 227
5.11.3 @prompt  . ...................................................................... 227

10 11
Contents Contents

5.11.4 @variable  ..................................................................... 230

6 Multisource Data Foundations  ................................................. 285
5.12 Families, Comments, and Data Foundation Views  ........................ 231
5.12.1 Families  ........................................................................ 231 6.1 The Federation Technology  . ........................................................ 286
5.12.2 Comments  .................................................................... 234 6.1.1 Merging Information from Multiple Data Sources  ........... 286
5.12.3 Data Foundation View  .................................................. 235 6.1.2 Federation Query Server  ................................................. 288
5.13 Data Foundation Search Panel  ..................................................... 238 6.1.3 Supported Data Sources  .................................................. 289
5.13.1 Table and Column Names Selection  .............................. 240 6.2 Multisource Data Foundations  ..................................................... 290
5.13.2 Table Types Selection  . .................................................. 241 6.2.1 Choosing the Data Foundation Type  ............................... 290
5.13.3 Column Types Selection  ................................................ 241 6.2.2 Creating a Multisource Data Foundation   ........................ 291
5.13.4 Families Selection  ......................................................... 242 6.2.3 Multisource Data Foundation Editor  ............................... 293
5.13.5 Contexts Selection  ........................................................ 242 6.3 Working with a Multisource Data Foundation  ............................. 294
5.13.6 Possible Actions after Tables Selection in a Data 6.3.1 Creating Multisource Joins  .............................................. 294
Foundation View  .......................................................... 243 6.3.2 Creating Multisource Derived Tables  ............................... 296
5.14 Data Foundation Editor  ............................................................... 243 6.4 Federated Tables  ......................................................................... 301
5.14.1 Possible Actions in the Data Foundation Schema  .......... 245 6.4.1 Federated Tables Usage  .................................................. 301
5.14.2 Possible Actions in the Data Foundation Pane  .............. 248 6.4.2 Federated Table Definitions  ............................................ 303
5.14.3 Possible Actions in the Aliases and Contexts Pane  . ....... 248 6.4.3 The Federation Layer Editor  ............................................ 306
5.14.4 Possible Actions in the Parameters and List of Values 6.4.4 Creating Federated Tables from Scratch  . ......................... 311
Pane  ............................................................................. 249 6.4.5 Creating a Federated Table from a Source Table
5.14.5 Possible Actions in the Connection Pane  . ..................... 250 Template  . ....................................................................... 314
5.14.6 Possible Actions in the Data Foundation Toolbar  .......... 252 6.4.6 Defining Mapping Rules  .................................................. 315
5.14.7 Possible Actions in the Data Foundation View Tab  . ...... 253 6.4.7 Defining Pre-filters   ......................................................... 320
5.14.8 Possible Actions in the Actions Menu  ........................... 254 6.4.8 Defining Post-filters  ........................................................ 321
5.14.9 Data Foundation Actions  .............................................. 255 6.4.9 Defining Source Table Relationships  . .............................. 323
5.14.10 Data Foundation Properties  .......................................... 259 6.4.10 Understanding Core and Non-Core Tables  . ..................... 326
5.15 Checking Integrity  ....................................................................... 260 6.4.11 Using Federated Tables in the Data Foundation  .............. 332
5.15.1 Run the Check Integrity  ................................................ 261 6.5 Multisource Scenarios  . ................................................................ 334
5.15.2 Understand the Result of the Check Integrity Process  . .. 262 6.5.1 The Union Scenario  ......................................................... 334
5.15.3 Analyze and Fix Errors and Warnings  . ........................... 263 6.5.2 The Mixed Sources Scenario  . .......................................... 338
5.15.4 Customize the Validation Rules  ..................................... 265 6.5.3 The Data Quality Scenario  ............................................... 342
5.15.5 Validation Rules Definition  ........................................... 266 6.6 Data Federation Administration Tool  ........................................... 344
5.16 Previewing Data  .......................................................................... 267 6.6.1 Data Federation Administration Tool User Interface  ........ 344
5.17 Data Foundation Refresh Structure  .............................................. 269 6.6.2 Query Auditing  ............................................................... 346
5.17.1 Data Foundation Impacts after Refresh Structure  .......... 272 6.7 Optimization Techniques  ............................................................. 349
5.17.2 Business Layer Impacts after Refresh Structure  .............. 273 6.7.1 Preparing the Federation Query Server Environment  ....... 349
5.18 Showing Dependencies  . .............................................................. 274 6.7.2 Gathering Statistics  ......................................................... 352
5.19 Data Foundation Parameters  . ...................................................... 277 6.7.3 Deployment Factors Impacting the Performance  ............. 352
5.20 Summary  ..................................................................................... 282 6.7.4 Optimization by Parameter Settings  ................................ 353
6.7.5 The Semi-Join Functionality  ............................................ 355

12 13
Contents Contents

6.7.6 The Merge-Join Functionality  .......................................... 357 7.11 Hierarchies  .................................................................................. 408
6.7.7 The Source Discriminating Filter  ...................................... 357 7.11.1 Level-Based Hierarchies  ................................................ 408
6.8 Summary  ..................................................................................... 358 7.11.2 Parent-Child or Value-Based Hierarchies  ....................... 408
7.11.3 Hierarchy Creation  ........................................................ 409
7.12 Levels  .......................................................................................... 410
7 The Business Layer  .................................................................... 361
7.13 List of Values  ............................................................................... 411
7.1 The Business Layer Objectives  . .................................................... 361 7.13.1 List of Values Based on Business Layer Objects  ............. 415
7.2 Creating the Business Layer  . ........................................................ 363 7.13.2 List of Values Based on the Query Panel  ....................... 415
7.2.1 OLAP Direct Access  ........................................................ 363 7.13.3 List of Values Based on a Custom Hierarchy  .................. 416
7.2.2 Business Layer Entities and Concepts  .............................. 364 7.13.4 Static List of Values  ....................................................... 417
7.2.3 Multidimensional Business Layer Creation  ....................... 367 7.13.5 List of Values Based on Custom SQL  ............................. 418
7.2.4 Relational Business Layer Creation  .................................. 373 7.13.6 List of Values Parameters and Options  .......................... 419
7.2.5 The Business Layer Editor  ................................................ 375 7.13.7 Customize List of Values Columns  ................................. 422
7.3 Objects  . ...................................................................................... 376 7.14 Parameters  .................................................................................. 423
7.4 Folders  ........................................................................................ 378 7.14.1 Parameter Definition  . ................................................... 424
7.5 Dimensions  . ................................................................................ 379 7.14.2 Prompt Text  . ................................................................ 425
7.5.1 Dimension Definition: Select Clause  . ............................ 382 7.14.3 Data Type   .................................................................... 425
7.5.2 Dimension Definition: Where Clause  ............................. 384 7.14.4 Allow Multiple Values  . ................................................. 425
7.5.3 Validation   ...................................................................... 385 7.14.5 Keep Last Values  . ......................................................... 425
7.5.4 Extra Tables  .................................................................... 385 7.14.6 Index Aware Prompt  ..................................................... 426
7.5.5 Preview Data and List of Values  ...................................... 387 7.14.7 Associated List of Values  ............................................... 426
7.6 Attributes  .................................................................................... 387 7.14.8 Select Only From List  .................................................... 427
7.6.1 Attribute Definition: Select Clause and Where 7.14.9 Set Default Values  . ....................................................... 427
Clause  ............................................................................. 389 7.14.10 Parameter Custom Properties  . ...................................... 427
7.6.2 Preview Data and List of Values  ...................................... 390 7.14.11 Dependent Parameters  ................................................. 428
7.6.3 Attribute Validation and Other Properties  ....................... 391 7.14.12 Parameters Usage  ......................................................... 429
7.7 Measures and Calculated Measures  ............................................. 391 7.14.13 Mandatory and Optional Parameters  ............................ 430
7.7.1 Measure Definition: SELECT Clause and WHERE 7.14.14 Parameter Dialog Box  ................................................... 431
Clause  ............................................................................. 395 7.15 Filters and Mandatory Filters  ....................................................... 431
7.7.2 Preview Data and List of Values  ...................................... 395 7.15.1 Native Filter Validation and Extra Tables  ....................... 433
7.7.3 Projection Function  . ....................................................... 396 7.15.2 Filter Properties  ............................................................ 433
7.7.4 Measure Validation and Other Properties  . ...................... 399 7.16 Navigation Paths  . ........................................................................ 435
7.8 Calculated Members  .................................................................... 399 7.16.1 Default Navigation Paths  .............................................. 436
7.8.1 Solve Order  . ................................................................... 402 7.16.2 Custom Navigation Paths  .............................................. 438
7.8.2 Format String   ................................................................. 402 7.17 Index Awareness  . ........................................................................ 439
7.8.3 Scope Isolation  ............................................................... 402 7.17.1 Primary Key  .................................................................. 440
7.8.4 Language   ....................................................................... 403 7.17.2 Foreign Key  .................................................................. 440
7.9 Named Sets  ................................................................................. 403 7.18 Aggregate Awareness  .................................................................. 441
7.10 Analysis Dimensions  .................................................................... 406 7.18.1 The Aggregate Aware Process  ....................................... 442

14 15
Contents Contents

7.18.2 Aggregate Navigation Incompatibility  ............................. 442 7.28 Business Layers Built on Multisource Data Foundations  ............... 495
7.18.3 Aggregate Navigation Set on Measures  ........................... 444 7.29 Multidimensional Business Layer Refresh Structure  ...................... 497
7.18.4 Aggregate Navigation Set on Dimensions  ........................ 445 7.30 Business Layer Parameters and Query Governors  ......................... 500
7.19 SQL and MDX Editors  . ................................................................ 447 7.30.1 Business Layer Parameters  . ............................................. 500
7.19.1 The SQL Editor  . .............................................................. 447 7.30.2 Query Governors  . ........................................................... 503
7.19.2 The MDX Editor  .............................................................. 450 7.31 Recommendations for Building a Business Layer  .......................... 507
7.20 Object Common Properties  ......................................................... 453 7.32 Summary  ..................................................................................... 508
7.20.1 Data Types  ...................................................................... 453
7.20.2 List of Values  .................................................................. 454
8 Universe Query Panel   ............................................................... 511
7.20.3 Access Level  . .................................................................. 456
7.20.4 Usage  . ............................................................................ 457 8.1 The Query Panel Interface  ........................................................... 512
7.20.5 Source Information  ......................................................... 458 8.1.1 Launching the Query Panel  ............................................. 512
7.20.6 State  ............................................................................... 459 8.1.2 Query Panel Parts  ........................................................... 512
7.20.7 Custom Properties  . ......................................................... 460 8.1.3 Query Panel Toolbars  ...................................................... 514
7.21 Object Formatting  ....................................................................... 461 8.2 Creating Queries  .......................................................................... 516
7.21.1 Display Format  . .............................................................. 461 8.2.1 Selecting the Result Objects  ............................................ 516
7.21.2 Custom Format  ............................................................... 462 8.2.2 Applying Filters to the Query  .......................................... 524
7.21.3 Database Format  . ........................................................... 464 8.2.3 Sorting Result Objects  . ................................................... 528
7.22 Business Layer Queries  . ............................................................... 464 8.3 Setting and Answering Prompts  ................................................... 530
7.23 Built-in Functions  ........................................................................ 466 8.3.1 Choosing Contexts   ......................................................... 530
7.23.1 @aggregate_aware  ......................................................... 467 8.3.2 Customizing a Prompt in the Query Filters  ...................... 530
7.23.2 @execute  ....................................................................... 467 8.3.3 Answering a Prompt  . ...................................................... 533
7.23.3 @prompt  . ...................................................................... 468 8.4 Setting the Query Properties  . ...................................................... 536
7.23.4 @select  .......................................................................... 471 8.5 Advanced Functionalities  ............................................................. 538
7.23.5 @variable  ....................................................................... 472 8.5.1 Adding a Subquery Filter  ................................................. 539
7.23.6 @where  . ........................................................................ 473 8.5.2 Adding a Ranking Filter  ................................................... 541
7.24 Business Layer Views  ................................................................... 473 8.5.3 Using Combined Queries  . ............................................... 543
7.25 Business Layer Functionalities  ...................................................... 476 8.5.4 Setting a Custom Query Script  . ....................................... 545
7.25.1 Preview Data  .................................................................. 476 8.6 Summary  ..................................................................................... 546
7.25.2 Search, Filter, Show, and Hide  ........................................ 479
7.25.3 Find and Replace  ............................................................ 482
7.25.4 Business Layer Lifecycle Functionalities  ........................... 483 9 Publishing and Retrieving Universes  . ....................................... 547
7.26 Check Integrity  ............................................................................ 486
9.1 Publishing a Universe Locally  ....................................................... 548
7.26.1 Run the Check Integrity  .................................................. 487
9.1.1 Connection  ..................................................................... 549
7.26.2 Understand the Result of the Check Integrity Process  ...... 488
9.1.2 Security  . ......................................................................... 549
7.26.3 Analyze and Fix Errors and Warnings  . ............................. 489
9.1.3 Web Intelligence Rich Client  ........................................... 550
7.26.4 Customize the Validation Rules  ....................................... 491
9.2 Publishing a Universe in a CMS Repository  .................................. 551
7.26.5 Validation Rules Definition  . ............................................ 492
9.2.1 Connection Shortcut  ....................................................... 553
7.27 Show Dependencies  .................................................................... 492

16 17
Contents Contents

9.2.2 CMS Repository  .............................................................. 554 10.5.3 Display Data   ................................................................ 593
9.2.3 Managing Published Universes  ........................................ 555 10.5.4 Filters (Relational Universe)  . ......................................... 595
9.3 Retrieving a Local Universe  .......................................................... 556 10.5.5 Filters (Multidimensional Universe)  ............................... 596
9.3.1 Retrieved Resources  ........................................................ 557 10.6 Security Profiles Aggregation  ..................................................... 598
9.3.2 Folder  ............................................................................. 558 10.6.1 Priority Aggregation  ...................................................... 599
9.4 Retrieving a Universe from the CMS Repository  ........................... 558 10.6.2 AND, ANDOR, and OR Aggregation  ............................. 600
9.4.1 Connection Shortcuts  ...................................................... 559 10.6.3 Supported Aggregations   . ............................................. 601
9.4.2 Security  . ......................................................................... 561 10.7 Managing Security Profiles in Information Design Tool  .............. 604
9.5 Information Design Tool Workflows  ............................................ 562 10.8 User Attributes  .......................................................................... 606
9.5.1 Publishing a Universe Locally  .......................................... 562 10.8.1 Defining User Attributes  ............................................... 607
9.5.2 Publishing a Universe in a CMS Repository  . .................... 564 10.8.2 Using User Attributes  .................................................... 607
9.5.3 Managing Universes Published in a CMS Repository  . ...... 565 10.8.3 User Attributes Substitution  .......................................... 608
9.5.4 Show Repository Dependencies  ...................................... 565 10.9 Running a Secured Query  .......................................................... 608
9.5.5 Retrieving a Local Universe  ............................................. 566 10.10 Summary  ................................................................................... 609
9.5.6 Retrieving a Universe from a CMS Repository  . ................ 567
9.6 Summary  ..................................................................................... 569
11 Working in Multilingual Environments   ................................... 611

10 Securing Universes   ................................................................... 571 11.1 Languages and Locales  .............................................................. 612
11.1.1 Language  ...................................................................... 612
10.1 Rights  .......................................................................................... 572 11.1.2 Locale   .......................................................................... 612
10.1.1 Information Design Tool Rights  ....................................... 573 11.1.3 Dominant Locale   ......................................................... 613
10.1.2 Universe Rights  ............................................................... 574 11.1.4 Product Language  ......................................................... 613
10.1.3 Relational Connection Rights  .......................................... 575 11.1.5 Preferred Viewing Locale  .............................................. 614
10.1.4 OLAP Connection Rights  ................................................. 576 11.2 Translation Management Tool  ................................................... 615
10.1.5 Data Federator Data Source Rights  . ................................ 577 11.2.1 Locales in the Translation Management Tool  ................ 616
10.2 Object Access Level  ..................................................................... 577 11.2.2 Translation Management Tool   . .................................... 616
10.3 Security Profiles  ........................................................................... 579 11.2.3 Resources in the CMS Repository  .................................. 617
10.3.1 Assigned Users and Groups  ............................................. 580 11.2.4 Translation Status in the Translation Management
10.3.2 Consumption  .................................................................. 581 Tool  .............................................................................. 618
10.4 Data Security Profiles  . ................................................................. 581 11.2.5 Running the Translation Management Tool  ................... 619
10.4.1 Connections  .................................................................... 583 11.2.6 Translating Properties in the Translation Management
10.4.2 Controls  .......................................................................... 584 Tool  .............................................................................. 621
10.4.3 SQL  . ............................................................................... 585 11.3 Translating Universe Metadata  .................................................. 622
10.4.4 Rows   . ............................................................................ 585 11.3.1 Universe Translation Workflow  ..................................... 623
10.4.5 Tables  ............................................................................. 586 11.3.2 Publishing Universe  . ..................................................... 624
10.5 Business Security Profiles  ............................................................. 587 11.3.3 Data Foundation Translatable Properties  . ..................... 625
10.5.1 Connection   .................................................................... 589 11.3.4 Business Layer Translatable Properties  .......................... 626
10.5.2 Create Query  . ................................................................. 590 11.4 Multilingual Data in Relational Universes  . ................................. 627
11.4.1 Multilingual Patterns in Relational Database  ................. 627

18 19
Contents Contents

11.4.2 Retrieving a Locale in a Universe with @Variable  . .......... 629

13 Comparing the Universe Design Tool and Information
11.4.3 Using @Variable in Different Patterns  ............................. 630
Design Tool  ................................................................................ 687
11.5 Multilingual and Multidimensional Universes  . ............................. 632
11.5.1 Metadata  ........................................................................ 633 13.1 General  ..................................................................................... 687
11.5.2 Data  . .............................................................................. 634 13.2 Connections  .............................................................................. 689
11.6 Summary  ..................................................................................... 634 13.3 Data Foundation  ....................................................................... 692
13.4 Business Layer  ........................................................................... 693
13.5 List of Values and Parameters  .................................................... 695
12 Connecting to SAP ERP, SAP NetWeaver BW, and
13.6 Security  ..................................................................................... 697
SAP HANA  . ................................................................................ 635
13.6.1 Access Restrictions and Security Profiles (Relational
12.1 Access to SAP NetWeaver BW  ..................................................... 636 Universe)  ...................................................................... 698
12.1.1 SAP NetWeaver BW Interfaces  ........................................ 636 13.6.2 Access Restrictions and Security Profiles (OLAP
12.1.2 Connection Parameters to SAP NetWeaver BW  ............... 638 Universe)  ...................................................................... 699
12.1.3 Creating an SAP NetWeaver BW OLAP Connection   . ...... 640 13.6.3 Aggregation  .................................................................. 700
12.1.4 Creating a Relational Connection to SAP 13.6.4 Security Editor  .............................................................. 701
NetWeaver BW  ............................................................... 643 13.6.5 Central Management Console Rights  . ........................... 702
12.1.5 Creating a Multisource Data Foundation Automatically   . .. 648 13.6.6 Connection Rights  . ....................................................... 703
12.1.6 Creating a Business Layer Automatically  .......................... 649 13.7 Miscellaneous  . .......................................................................... 704
12.1.7 Creating a Data Foundation and a Business Layer 13.8 Universe Conversion  .................................................................. 705
Manually  . ....................................................................... 651 13.8.1 Universe Conversion Scope  ........................................... 706
12.1.8 SAP NetWeaver BW Relational Universe Performance  ..... 652 13.8.2 Local versus Secured Universe Conversion  . ................... 707
12.2 Access to SAP ERP  ....................................................................... 652 13.8.3 Data Foundation and Business Layer  ............................. 708
12.2.1 SAP ERP Connection Parameters  ..................................... 653 13.8.4 Linked Universe  ............................................................ 709
12.2.2 Creating a Relational Connection to SAP ERP  .................. 654 13.8.5 Universe Rights Conversion   .......................................... 710
12.2.3 Data Foundation on SAP ERP  .......................................... 656 13.8.6 Access Restriction Conversion   ...................................... 710
12.2.4 Single-Source Data Foundations on SAP ERP  . ................. 659 13.8.7 Access Restriction Aggregation Option Conversion   ...... 711
12.2.5 Multisource-Enabled Data Foundations on SAP ERP  ....... 661 13.8.8 Object Access Level  ...................................................... 712
12.2.6 Business Layers on an SAP ERP-Based Data Foundation  .... 663 13.9 Converting Universes in Information Design Tool  . ..................... 712
12.3 Access to SAP HANA  ................................................................... 664 13.9.1 Converting a Local Universe  .......................................... 712
12.3.1 Creating a Universe on SAP HANA Views  ........................ 665 13.9.2 Converting a Secured Universe  . .................................... 714
12.3.2 Creating a Data Foundation and a Business Layer 13.10 Summary  ................................................................................... 715
Automatically  . ................................................................ 671
12.3.3 SAP HANA Views: Recommendations and Constraints  .... 676 The Authors  ................................................................................................ 717
12.3.4 Creating a Multidimensional Access on SAP HANA  ......... 679 Index  .......................................................................................................... 719
12.4 Migrating a Universe to SAP HANA  ............................................. 681
12.5 Summary  ..................................................................................... 685

20 21
Index

@aggregate_aware, 441, 467, 674 Adaptive Processing Server, 134, 349

@catalog, 296, 297 Aggregate awareness, 171, 184, 207, 366,
@derivedtable, 184, 226 441, 467
@execute, 212, 215, 225, 227, 419, 449, 467, Aggregate navigation, 366
696 Agnostic file, 88
@prompt, 170, 184, 192, 212, 215, 218, 223, Alias table, 162, 168, 184, 196, 197, 198,
225, 227, 231, 267, 279, 383, 385, 390, 204, 206, 207, 225, 231, 232, 234, 236,
391, 395, 399, 403, 419, 423, 429, 449, 241, 245, 248, 254, 256, 266, 272, 275,
452, 465, 468, 473, 492, 501, 608, 629, 332, 375, 448, 477, 493, 585, 587, 699
677, 696, 699, 708, 713, 715 All objects, 590, 594
@select, 382, 390, 391, 395, 399, 400, 403, ALL operator, 539
404, 409, 411, 419, 449, 452, 459, 460, Allow complex operands in query panel, 505
471, 498 Allow query stripping, 505
@variable, 129, 170, 184, 192, 215, 223, 230, Allow use of subqueries, 505
279, 383, 385, 390, 391, 395, 447, 450, Allow use of union, intersect and minus
472, 501, 571, 586, 596, 607, 629, 699 operators, 505
BOUSER, 230, 472, 606 All views, 590
DBUSER, 230, 472 Alternate connection, 583, 589
DOCNAME, 230, 472 Allow users to edit list of values, 217, 420,
DOMINANT_PREFERRED_VIEWING_ 456
LOCALE, 6­30 Allow users to search values in the database,
DPNAME, 230, 472 421, 456
PREFERRED_VIEWING_LOCALE, 231, Analysis dimension, 365, 372, 404, 406, 409,
473, 630 414, 436, 461
UNVNAME, 231, 473 Type, 407
@where, 383, 449, 452, 473 ANSI SQL-92, 175, 279, 290, 294, 318, 495,
662
ANY operator, 539
A Apache, 119
Derby, 119
ABAP functions, 303, 652, 661 Hadoop, 119, 691
Access restriction, 67, 579, 697, 698 Hive, 100
Connection, 698 Array fetch size, 654
Controls, 698 Assigned groups, 580
Objects, 698 Assigned users, 580
Rows, 698 Attribute, 158, 183, 192, 274, 365, 372, 376,
SQL, 698 379, 384, 387, 393, 395, 406, 412, 414,
Table mapping, 698 429, 431, 439, 442, 447, 450, 451, 453,
Activate_multi_threaded_union_operator, 354 454, 456, 457, 458, 461, 464, 471, 473,
Activate_order_based_optimization_rule, 357 476, 477, 485, 487, 493, 501, 540, 668,
ACTIVATE_SEMI_JOIN_RULE, 356 670, 673, 677
Active Directory, 100, 607

719
Index Index

Audit, 42 Business layer view, 362, 366, 473, 694 Cheat sheet, 60, 68, 704 cs.cfg, 140
Authentication, 42, 99, 552, 638, 653, 666, Business object name, 72 Check integrity, 64, 72, 202, 226, 245, 250, CSV, 417
680 Business security profile, 67, 571, 573, 579, 260, 261, 262, 265, 273, 333, 385, 388, CUID, 555
Active Directory, 100, 607, 618 587, 698 391, 399, 450, 484, 485, 486, 487, 488, Currency, 650
Enterprise, 99, 618 Connection, 587, 589, 603 491, 500, 563, 564, 565, 704 Custom properties, 222, 259, 427, 460, 694
LDAP, 100, 607, 618 Create Query, 588, 590, 603 Cluster, 97 Custom SQL, 545
SAP, 100, 607 Display Data, 588, 593, 603 ID, 98, 561 Custom user attribute, 688
Automatic refresh before use, 217, 420, 456 Filters, 588 Name, 98, 551
Auto-save, 705 Filters (multidimensional universe), 596, CMS repository, 42, 96, 160, 230, 362, 364,
AUTO_UPDATE_QUERY, 279, 595 604 383, 457, 464, 472, 547, 551, 567, 571 D
Available locale, 616 Filters (relational universe), 595, 603 Column filter, 656
Combined query, 514, 543 Database, 177, 184, 215, 223, 274, 280, 361,
Conditional table, 585, 698, 699 370, 377, 385, 390, 395, 397, 400, 403,
B C ConnectInit, 140 408, 419, 432, 440, 442, 447, 450, 464,
Connection, 36, 55, 60, 77, 86, 117, 163, 497, 505
BEGIN_SQL, 279 Calculated column, 158, 189, 191, 212, 223, 168, 260, 263, 266, 274, 292, 486, 490, Column, 162, 163, 165, 176, 178, 180,
BEx query, 636, 695 225, 226, 231, 236, 243, 245, 260, 266, 492, 493, 689 184, 189, 192, 212, 215, 223, 246,
BICS connection, 518, 519, 636, 640 273, 274, 275, 413, 429, 430, 447, 477, OLAP connection, 361, 363, 364, 367 250, 256, 258, 260, 267, 268, 269,
BI platform, 43, 289, 292 493, 656, 676, 692 Relational connection, 157, 159, 244, 250, 270, 271, 272, 275, 279, 375, 380,
Blob, 453, 694 Calculated measure, 366, 370, 376, 382, 391, 259, 362, 667, 679 385, 391, 399, 412, 419, 432, 439,
BLOB_COMPARISON, 279 392, 471 Secured connection, 159, 160, 161, 363, 446, 447, 453, 460, 477, 493, 501
Bottom operator, 541 Calculated member, 366, 370, 372, 376, 382, 368, 667 Key column, 75, 162, 178, 182, 183, 246,
bscLogin.conf, 100 392, 399, 414, 429, 450, 451, 453, 454, Connection authentication, 127 254
Built-in functions, 178, 184, 192, 399, 403, 461, 471, 519 Credentials mapping, 128 Table, 157, 159, 162, 165, 166, 168, 169,
492 Format string property, 402 Fixed credentials, 128 175, 176, 178, 182, 183, 184, 188,
Business intelligence, 29 Language property, 403 Single Sign-On, 128 189, 190, 192, 194, 195, 197, 198,
Business layer, 37, 55, 62, 66, 72, 77, 86, Scope Isolation property, 402 Connection editor, 65 203, 205, 206, 207, 209, 215, 223,
126, 157, 159, 161, 171, 182, 183, 189, Solve order option, 402 Connection icons, 142 231, 239, 241, 243, 245, 250, 254,
190, 191, 207, 209, 210, 212, 218, 246, Calculation view, 664 Connection Server, 39, 52, 118, 134, 690 255, 256, 257, 258, 260, 266, 267,
263, 267, 273, 274, 275, 290, 298, 338, Calculator, 41, 46 ConnectionServer32, 134 268, 269, 270, 272, 275, 279, 280,
361, 512, 548, 622, 638, 663, 669, 670, Cardinality, 347 ConnectionServer64, 134 375, 380, 385, 391, 399, 419, 429,
671, 682, 693 Cartesian product, 198, 202, 206, 209, 281, Connection shortcut, 125, 146, 552 433, 447, 467, 477, 478, 488, 493,
Find and replace, 482 585 Connectivity, 31 501, 664, 668, 676
Multidimensional business layer, 361, 364, Cascading prompt, 697 Connector configuration view, 346 View, 157, 184, 250, 270, 668
367, 369, 380, 384, 388, 392, 395, Case, 302, 341, 343 Constant, 527 Database catalog browser, 165, 166, 168, 178,
399, 403, 406, 408, 410, 414, 418, Category, 618 Consumption, 581 250, 251
476, 481, 484, 492, 497, 503 Needs Translation, 618, 622 Context, 162, 195, 198, 200, 201, 202, 203, Database credentials, 129, 130
Multidimensional business layer refresh Translation Visible, 618, 622 205, 206, 207, 209, 235, 239, 242, 248, Database delegated measure, 46
structure, 384, 404, 409, 485, 497 Central Configuration Manager (CCM), 97 254, 257, 260, 266, 282, 465, 506, 530, Database schema, 682
Parameters, 366, 500, 503 Central Management Console (CMC), 121, 585, 651, 673, 674, 676, 692 Data Federation Administration Tool, 58, 286,
Query options, 216, 420 130, 290, 350, 364, 555, 562, 572, 607, Context help, 67, 704 289, 344, 644
Relational business layer, 260, 277, 361, 637, 681 Core table, 326, 341 Data Federator data source, 121, 572
364, 366, 373, 374, 380, 385, 388, Central Management Server (CMS), 42, 688 CPU, 352
392, 414, 431, 439, 453, 473, 484, Changing parameter, 657 Crystal Decisions, 44
486, 497, 500, 503, 670 Characteristic, 649
Search, filter, show, and hide, 479 Chasm trap, 157, 209, 281

720 721
Index Index

Data foundation, 36, 55, 61, 73, 77, 86, 126, Desktop Intelligence, 44 Filter (Cont.) Index awareness, 183, 184, 217, 220, 366,
157, 338, 361, 363, 374, 380, 411, 412, Dimension, 158, 162, 183, 192, 208, 210, Business filter, 430, 431, 459, 492, 495 422, 425, 439, 469
413, 423, 430, 433, 442, 443, 445, 447, 274, 282, 365, 375, 376, 378, 379, 384, Mandatory filter, 41, 431 Index awareness foreign key, 440
453, 464, 476, 478, 484, 486, 490, 493, 387, 391, 393, 395, 404, 406, 412, 414, Native filter, 431, 473 Index awareness primary key, 440
497, 548, 622, 667, 668, 669, 670, 671, 429, 431, 435, 436, 439, 442, 447, 450, Flat layout option, 515 Index aware prompt, 697
673, 676, 682, 692 451, 453, 454, 456, 457, 458, 459, 460, Folder, 88, 158, 197, 362, 365, 375, 376, InfoCube, 645
Comment, 234, 235, 236, 237, 245, 254 461, 464, 471, 473, 476, 477, 485, 487, 378, 379, 391, 392, 404, 409, 431, 436, InfoObject, 42, 580
Data foundation refresh structure, 272, 488, 493, 501, 516, 540, 649, 668, 670, 459, 460, 461, 486, 670 InfoProvider, 640
273, 274 671, 673, 674, 677 Force users to filter values before use option, Information engine, 36, 38
Detect row count, 254 Direct access, 38, 576 421, 456 Information space, 49
Editor, 65, 212, 218, 243 Distinct filter, 306 FORCE_SORTED_LOV, 279 InfoSet, 652, 661
Family, 231, 232, 235, 236, 239, 242, Dominant locale, 613 Foreign key, 656, 659 Ingres, 120
253, 692 Drill through, 436 Fully qualified hostname, 97 INNERJOIN_IN_WHERE, 280
Loop, 157, 171, 178, 194, 196, 197, 198, Driver, 134 Input column, 657, 658
202, 204, 243, 254, 260, 267 DSO, 645 Installer (client tools), 40, 56, 344
Master view, 235, 236, 237, 272 G IP address, 97
Multisource data foundation, 159, 288, IsNull, 329, 341
495, 637, 648, 661, 692 E Generic connectivity, 119 ISO 639-1, 630
Parameters, 277, 281 GreenPlum, 120 ISO 3166, 630
Refresh structure, 251, 253, 254, 259, 269 END_SQL, 279 Group, 101, 574, 578, 580, 599
Search and filter, 168 E-R model, 157, 162, 184 Administrators, 101
Search panel, 238, 240, 243, 253 EXECUTOR_STATIC_MEMORY, 353 Universe Designers, 101 J
View, 233, 234, 235, 236, 240, 241, 242, EXECUTOR_TOTAL_MEMORY, 353
245, 248, 249, 252, 253, 254, 272, 692 Export parameter, 657 Java bean, 706
Data integration, 285 H JDBC, 119, 133, 137, 665, 679
Data modeling, 157 Join, 61, 75, 157, 159, 169, 172, 175, 178,
Data preview, 77, 150, 321, 513 F Help, 60 180, 183, 184, 188, 189, 190, 194, 195,
Data provider, 41 Hierarchical Layout option, 515 196, 200, 201, 202, 203, 206, 207, 209,
Data quality, 301, 342 Fallback locale, 616, 622 Hierarchy, 366, 369, 372, 376, 382, 400, 403, 212, 223, 226, 231, 234, 236, 240, 243,
Data security profile, 67, 433, 571, 573, 579, Fan trap, 157, 206, 281 404, 406, 408, 410, 414, 429, 436, 450, 245, 246, 248, 254, 257, 258, 259, 260,
581, 698 Federated table, 225, 231, 232, 234, 236, 451, 456, 457, 458, 461, 471, 476, 477, 267, 273, 277, 280, 294, 413, 429, 430,
Connections, 583, 601 241, 256, 301, 324, 349, 448, 477, 495, 523, 525, 637 439, 447, 465, 477, 488, 659, 676
Controls, 584, 602, 698 585, 587, 692 Level-based hierarchy, 372, 408, 410, 436, Cardinality, 61, 75, 158, 169, 174, 178,
Rows, 585, 602 Federation, 286 476, 517 182, 194, 198, 205, 206, 234, 247,
SQL, 585, 602 Federation editor, 77 Parent-child hierarchy, 372, 408, 436, 517 254, 266, 267, 443
Tables, 586, 603 Federation Layer, 293, 306 Hint, 140 Filter join, 175, 178, 248, 273, 280, 478
Data source credentials, 129 Federation Query Server, 121, 135, 136, 286, HTML, 80, 704 Operator, 173, 395
Dependency, 95, 566, 692, 697 289, 297, 349, 373, 495, 529, 539, 549, Outer join, 175, 176, 184, 280
Derived table, 158, 185, 189, 190, 212, 223, 572, 573, 577, 637, 644, 690 Shortcut join, 175, 178, 195, 203, 280
225, 226, 231, 232, 234, 236, 241, 243, File system, 87 I JOIN_BY_SQL, 280
245, 254, 256, 260, 266, 272, 274, 275, Filter, 361, 365, 376, 378, 379, 383, 384,
296, 301, 332, 358, 375, 413, 429, 430, 387, 391, 413, 429, 431, 447, 449, 452, IBM, 120
447, 448, 477, 493, 495, 585, 587, 631, 461, 486, 493, 513, 515 DB2, 363 K
632, 676, 677, 699 Apply on Folder, 435 Netezza, 120
Database-specific syntax, 297 Apply on List of Values, 435 ID, 125, 554 Key figure, 650
Apply on Universe, 434 Impact analysis, 91 krb5.ini, 100
Import parameter, 657

722 723
Index Index

L Mapping rule, 304, 327 N OLE DBO, 141

MAX_CONCURRENT_MEMORY_ Online help, 704
Language, 612 CONSUMING_QUERIES, 353 Named set, 366, 370, 372, 376, 382, 403, Online tutorial, 70
Language-specific columns, 628 MAX_INLIST_VALUES, 280 414, 429, 450, 451, 454, 461, 471, 482, Open session, 96
Language-specific databases, 629 Max rows, 78 519 Operator, 505, 525, 528, 543, 596, 600
Language-specific rows, 627 MDX, 36, 362, 369, 370, 382, 385, 389, 391, Business named set, 405 AND, 170, 172, 240, 600, 701
Language-specific tables, 628 395, 397, 400, 402, 403, 406, 407, 409, Native named set, 405 Intersection, 600
LCMBIAR, 562 411, 422, 429, 430, 447, 453, 466, 479, Navigation path, 66, 365, 376, 379, 383, 387, MAX, 600
Level, 366, 372, 406, 408, 410, 414, 429, 482, 486, 597, 636, 638, 691 389, 391, 409, 435, 459, 482 MIN, 600
450, 451, 456, 457, 458, 461, 471, 476, MDX editor, 380, 382, 385, 388, 391, 392, Custom navigation path, 438, 485 Multidimensional operator, 403, 518, 597,
519, 525 399, 400, 409, 410, 447, 466 Default navigation path, 436 693
Level business type, 411 Measure, 158, 192, 207, 208, 209, 210, 274, New Universe wizard, 60 OR, 240, 600, 701
Limit execution time, 504 277, 282, 365, 369, 372, 376, 378, 379, nvl, 329, 341 Union, 385, 600, 631
Limit size of result set, 504 384, 387, 391, 395, 412, 414, 429, 431, Optimization, 349
List of values, 39, 66, 77, 158, 162, 212, 219, 442, 447, 450, 451, 453, 454, 456, 457, Oracle, 120, 122, 140, 159, 363, 634, 681,
224, 227, 254, 267, 268, 269, 274, 275, 458, 459, 460, 461, 464, 471, 473, 476, O 706
277, 365, 376, 379, 383, 387, 391, 411, 477, 485, 487, 488, 493, 500, 501, 505, Oracle hint, 706
423, 431, 440, 448, 450, 453, 454, 459, 516, 670, 673, 677 Object, 590 Oracle Hyperion Essbase, 38, 122, 363, 370,
461, 465, 467, 468, 476, 477, 482, 485, Projection function, 369, 396, 486, 498 Object access level, 377, 456, 480, 486, 571, 452, 633
487, 488, 492, 493, 495, 500, 521, 527, Member selector, 400, 403, 405, 408, 410, 577, 712 Original content locale, 616, 617, 633
535, 695, 709 411, 481, 516, 523 Confidential, 577 Owner, 296, 297, 554, 587
Based on a custom hierarchy, 416, 459 Menu (Information Design Tool), 63 Controlled, 577
Based on custom SQL, 212, 215, 217, 223, Merge-join, 357 Private, 577
418, 422, 429, 447, 453 Metadata exchange, 689 Public, 577 P
Based on the query panel, 415, 429, 459 Microcube, 46, 398 Restricted, 577
Custom list of values, 455 Microsoft, 120, 122 Object data type, 217, 220, 377, 385, 391, Parameter, 66, 158, 162, 212, 213, 218, 224,
Default list of values, 387, 396, 420, 454 Microsoft SQL Server, 140, 159, 363, 681 394, 399, 422, 425, 453, 462, 480, 486, 227, 244, 254, 268, 274, 275, 277, 279,
Static, 212, 213, 217, 417, 422, 453 Microsoft SQL Server Analysis Services, 38, 498 361, 365, 376, 412, 413, 423, 448, 450,
List of Values pane, 244 141, 363, 370, 401, 452, 519, 633 Object extra tables, 385, 391, 399, 433, 478 453, 459, 461, 465, 468, 476, 482, 485,
Local connection, 126, 145 Middleware, 133 Object format, 366, 461, 480 487, 493, 501, 504, 677, 695
Locale, 612 MIN_ACTIVATION_THRESHOLD_FOR_ Custom display format, 462, 486 Allow multiple values, 221, 425
Local project, 86, 126, 289, 363, 567, 623, SEMI_JOIN_RULE, 356 Object state, 377, 459, 480, 486, 498, 694 Associated list of values, 221, 426
671 MIN_SOURCE_CARDINALITY_THRESHOLD_ Active, 459, 481, 694 Index aware prompt option, 221, 426
Backup, 89 FOR_SEMI_JOIN_RULE, 356 Deprecated, 460, 475, 481, 694 Keep last values option, 221, 425
Local projects view, 64, 66 Min_store_cardinality_threshold_for_order_ Hidden, 415, 416, 459, 475, 481, 694 Parameter dependencies, 428
Lock, 109, 114 based_join_rule, 357 Object usage, 377, 378, 457 Prompt to users, 220, 424
Min_transfer_cardinality_threshold_for_ Object validation, 385, 391, 399, 433 Select only from list, 222, 427
merge_join_rule, 357 OData, 119, 691 Set default values, 222, 427
M MOLAP cube, 30 ODBC, 119, 133, 665 Set values, 220, 425
Monitoring, 42 OLAP, 38, 632 Partition, 334
Mapping formula, 304, 308, 315 Multiple SQL statements, 585 OLAPClient, 39, 121 Password, 705
Aggregation, 305, 315, 318 For each measure, 505 OlapClient.cfg, 141 PDF, 704
Complex formula, 305, 315, 318 MultiProvider, 645 OLAP connection, 121, 552, 572, 690, 704, Performance, 33, 349
Constant, 305, 315, 319 Multisource, 31 706 Permute, 343
Equality, 305, 315, 316 Multisource universe, 552, 559 OLAP dimension, 372, 382, 399, 406, 408 Personal connection, 690
OLAP universe, 695, 699, 706 Post-filter, 306, 309, 321
OLE DB, 119, 133 Predefined query, 695

724 725
Index Index

Predefined session, 98 Query panel, 36, 41, 45, 77, 185, 186, 194, Right (Cont.) SAP BusinessObjects Data Federator XI 3.0,
Preferences, 71 208, 210, 279, 282, 361, 373, 376, 379, Create, modify, or delete connections, 101, 690, 691, 692, 706
Preferred viewing locale, 76, 614, 639, 653 381, 387, 391, 400, 404, 410, 411, 415, 141, 148, 573, 702 SAP BusinessObjects Design Studio, 637
Pre-filter, 306, 309, 320 430, 433, 456, 457, 459, 465, 467, 481, Data access, 150, 575, 577, 608, 703, 710 SAP BusinessObjects Explorer, 48, 124, 511,
Preview data, 77, 150, 184, 267, 321, 387, 504, 511, 565, 588, 626, 673 Delete objects, 573 555, 688
390, 395, 476, 486, 513 Filter, 227, 381, 387, 391, 410, 412, 416, Download connection locally, 129, 148, SAP BusinessObjects Live Office, 688
Primary key, 656, 659, 697 431, 435, 446, 456, 457, 468, 505, 506 576, 691 SAP BusinessObjects SQL, 290, 295, 297, 305,
PRM, 140, 225, 377, 449 Results, 227, 381, 387, 390, 391, 395, Edit access restrictions, 703, 710 318, 495, 662
Product Availability Matrix (PAM), 119, 122 400, 404, 410, 411, 416, 435, 457, Edit objects, 148 SAP BusinessObjects Web Intelligence, 44,
Product language, 76, 613 468, 506 Edit script, 582 123, 157, 184, 217, 230, 364, 396, 402,
Program ID, 644 View, 345 Edit security profiles, 575, 703, 710 425, 429, 435, 436, 459, 461, 465, 472,
Project, 160, 263, 275, 374, 493, 667, 670, Query properties, 536 Link universe, 703 511, 575, 582, 614, 637, 677, 679, 682,
671 Query stripping, 46, 505, 506 Log on to the Designer and view this object 688, 706
Project synchronization, 64, 102, 109 Query technique, 39 in the CMC, 554, 573 Rich Client, 45, 57, 126, 135, 547, 550,
Prompt, 39, 358, 520 New list of values, 703, 710 614
A-prompt, 228 Print universe, 703, 710 SAP BusinessObjects Query as a Web Service,
D-prompt, 228 R Publish universes, 101, 554, 573, 702 688
DT-prompt, 228 Query script, 582 SAP BusinessObjects XI 3.0, 707
K-prompt, 228, 697 RAM, 349, 352 Refresh structure window, 703 SAP BusinessObjects XI 3.x, 60
N-prompt, 228 Ranking filter, 541 Retrieve universe, 561, 574, 575, 703 SAP BusinessObjects XI R2, 707
Publishing, 42 Raw data, 80 Retrieve universes, 101, 561, 574, 702 SAP Crystal Reports 2013, 47, 124, 688
Publishing a universe, 547 RDBMS, 157, 159, 363, 664 Save for all users, 101, 561, 574, 703 SAP Crystal Reports Business View Manager,
Recent resources, 59 Share projects, 101, 108, 574 572
Refresh query, 516 Show table or object values, 703, 710 SAP Crystal Reports for Enterprise, 46, 123,
Q Relational connection, 118, 124, 552, 572, Unlock universe, 703, 710 157, 184, 364, 425, 429, 459, 461, 465,
583, 690 Use shared projects, 703 511, 555, 575, 614, 637, 677, 679, 682,
Qualifier, 296, 297, 587 SAP NetWeaver BW, 146, 572, 573, 577, Use table browser, 703 688
Query, 66, 77, 158, 183, 184, 202, 203, 206, 583 View objects, 581, 583, 589, 608 SAP Crystal Server 2013, 118
208, 209, 210, 212, 220, 280, 281, 282, SAS, 146, 572, 573, 577, 583 Role, 640, 643 SAP Data Services, 459, 682
361, 376, 379, 383, 391, 410, 411, 412, Remote function call (RFC), 640, 643 SAP direct access, 518, 519, 637, 638
415, 425, 429, 431, 439, 440, 442, 453, Replacement table, 586 SAP ERP, 118, 303, 635, 652
459, 460, 464, 482, 485, 487, 492, 493, Report bursting, 132 S SAP HANA, 38, 46, 49, 52, 122, 123, 159,
500 Repository resources, 64, 512, 643 163, 168, 363, 373, 387, 434, 446, 565,
Properties, 216, 420 Restricted key figure, 637 SAP BusinessObjects Analysis 635, 664, 668, 676, 679, 689
Query auditing, 346 Retrieving universe, 566 Edition for Office, 637 Analytic view, 164, 664
Query banding, 140 Right, 571, 572 Edition for OLAP, 123, 637 Attribute view, 164, 664
Query drill, 46 Add objects to the folder, 142, 554, 573 SAP BusinessObjects BI, 29 Calculation view, 164
Query engine, 158, 171, 188, 194, 196, 200, Add or edit user attributes, 607 SAP BusinessObjects BI 4.0, 55, 57, 288 Hierarchy view, 164
202, 203, 207, 209, 277, 279, 280, 281, Administer security profiles, 101, 573, 702 SAP BusinessObjects BI 4.1, 57, 58, 302, 677, View, 164, 373, 664, 667, 668, 670, 671,
384, 440, 442, 446, 500, 502, 674, 676, Apply universe constraints, 702 679, 681 672, 673, 674, 676, 678
677 Assign security profiles, 574, 703, 710 SAP BusinessObjects BI Launch Pad, 615 SAP HANA Studio, 664, 667
Query filters, 541 Check universe integrity, 703 SAP BusinessObjects Dashboards, 47, 123, SAP Java Connector (JCo), 654
Query governors, 366, 502, 503 Compute statistics, 101, 573, 703 157, 184, 364, 379, 400, 404, 410, 411, SAP Lumira, 50, 511, 555, 688
Query limits, 504 Create and edit queries based on the 425, 429, 459, 461, 465, 511, 555, 614, SAP NetWeaver BW, 38, 43, 46, 121, 152,
Query options, 505 universe, 574, 703, 710 637, 677, 679, 688 289, 290, 363, 373, 387, 408, 434, 505,
Query monitoring view, 346 Create and edit query on top of this 549, 607, 635, 690, 695
universe, 608

726 727
Index Index

SAP NetWeaver BW (Cont.) Software Development Kit (SDK), 428, 460, Translation status (Cont.) Universe Landscape Migration, 57, 682
Application Server, 639, 653 689, 694, 705 NEEDS_REVIEW_TRANSLATION, 618 Universe view, 512
Client, 638, 653 Sort, 515 NEEDS_TRANSLATION, 618 Upper, 630
Logon group, 639, 653 Source discriminating filter, 357 NEW, 618, 622 User attribute, 571, 606
Message server, 639, 653 Source information, 458 SIGNED_OFF, 618 User-centric view, 606
Server type, 639, 653 SQL, 30, 36, 52, 77, 157, 165, 175, 176, 184, TRANSLATED, 618 User defined object, 695
System ID, 639, 653 189, 190, 192, 194, 196, 200, 203, 207, TXT, 704 User guide, 67
System number, 639, 653 209, 215, 217, 223, 225, 226, 255, 257, User object, 695
SAP Predictive Analysis, 52, 511, 555, 688 266, 267, 279, 280, 281, 282, 362, 377,
SAP query, 652, 662 381, 382, 384, 385, 389, 391, 395, 397, U
SAP Sybase, 363, 120 412, 413, 418, 422, 429, 430, 434, 441, V
SAP Sybase ASE, 681 446, 447, 453, 466, 477, 478, 482, 486, UNICODE_STRINGS, 281
SAP variable, 504, 665, 668, 676, 677 495, 501, 502, 505, 636, 664, 673, 674, Union, 334, 631 View, 590
SAS, 121, 289, 290, 549, 690 678, 691 Unit of measure, 650 View column values, 296
Save for all users, 562, 568, 714 SQL builder, 297, 298 Universe, 34, 55, 157, 182, 199, 205, 238, View script, 545, 546
SBO, 141 SQL editor, 174, 186, 193, 223, 224, 226, 269, 281, 361, 362, 371, 434, 441, 446, VirtualProvider, 645
Scan and repair, 704 380, 382, 384, 385, 388, 391, 392, 399, 457, 458, 473, 511, 664, 671, 673, 677 Visible locale, 616, 622
Scheduling, 42 432, 433, 439, 447, 466 Core universe, 709
Search, 94 SQL façade, 637, 652 Derived universe, 709
Secondary credentials, 129 Star schema, 649 Linked universe, 688 W
Secured connection, 124, 142, 690 Statistics, 345, 347, 352, 573 Local, 562, 566
Secured query, 608 Stored procedure, 706 Multidimensional universe, 361, 364, 525, Warn if cost estimate exceeds, 504
Security, 31, 42, 571 Strategy, 692 552, 557, 559, 579, 623, 632, 679, 695 Web Service, 119, 691
Security aggregation, 82, 601, 700 Subquery filter, 539 Multisource universe, 285 Welcome page, 58, 60, 70, 704
AND algorithm, 600, 601, 701 Substring, 630 OLAP universe, 68, 695, 699, 706 Where clause, 585
ANDOR algorithm, 600, 601, 701 Support package, 57 Relational universe, 68, 157, 164, 361,
Less restrictive, 600 Synchronizing, 107 363, 579, 623, 627, 664, 678
Moderately restrictive, 600, 712 System parameters, 353 SDK, 222 X
Multiple-assignments, 599 System parameters view, 346 Transient universe, 363
Multiple-parents, 599 Universe SDK, 428 XLIFF, 618
OR algorithm, 600, 601, 701 Universe-centric view, 606 XML, 80, 120
Parent-child, 599 T Universe conversion, 60, 687, 705 XMLA, 133, 141
Priority, 599, 700, 711 Universe Designer, 40, 55
Very restrictive, 600, 712 Teradata, 120, 140, 363, 681 Universe Design Tool, 40, 47, 55, 57, 60, 68,
Security Editor, 67, 102, 512, 573, 604, 701 Text file, 80, 88, 93, 119, 138, 149, 214, 262, 378, 387, 409, 436, 459, 547, 551, 553, Z
Security profile, 571, 697 363, 417, 489 555, 638, 687
SELFJOIN_IN_WHERE, 280 THOROUGH_PARSE, 281 Universe (Information Design Tool), 572, 574 Zoom, 693
Semantic layer, 29, 511 Top operator, 541
Semi-join, 355 Translation Management Tool, 57, 611, 615,
Session, 96, 102, 564 633, 678, 695
Shared connection, 690 Translation Server, 618
Shared project, 106, 623, 688 Translation status, 618
Shared resources, 289 FINAL, 618
SHORTCUT_BEHAVIOR, 280 NEEDS_ADAPTATION, 618
Show dependencies, 250, 273, 274, 492 NEEDS_L10N, 618
Single Sign-On (SSO), 100, 130, 552 NEEDS_REVIEW_ADAPTATION, 618
NEEDS_REVIEW_L10N, 618

728 729
First-hand knowledge.

Christian Ah-Soon has worked for SAP BusinessOb-

jects for 13 years as a program manager on areas like
administration, security, internationalization, and ins-
tallation. Christian holds a Ph.D. in computer science
and graduated from TELECOM Nancy.

Didier Mazoué works for SAP as a member of the

SAP BusinessObjects platform team, where he is the
product owner for the semantic layer. He has years
of experience with the SAP BusinessObjects product
offerings.

Pierpaolo Vezzosi works at SAP as a member of the

SAP BusinessObjects platform team, where he is the
director of solution management for the semantic
layer. He has years of experience with the SAP Busines-
sObjects product offerings.

Christian Ah-Soon, Didier Mazoué, Pierpaolo Vezzosi

Universe Design with SAP BusinessObjects BI We hope you have enjoyed this reading sample. You may recommend
The Comprehensive Guide or pass it on to others, but only in its entirety, including all pages. This
reading sample and all its parts are protected by copyright law. All usage
729 Pages, 2014, $79.95/€79.95
and exploitation rights are reserved by the author and the publisher.
ISBN 978-1-59229-901-0
© 2016 by Rheinwerk Publishing, Inc. This reading sample may be distributed free of charge. In no way must the file be alte-

www.sap-press.com/3412 red, or individual pages be removed. The use for any commercial purpose other than promoting the book is strictly prohibited.