Bobj Faq

Questions and Answers: SAP
Business Objects BI 4.0 and the

New Semantic Layer for
SAP Net Weaver BW and OLAP
Applies to:
SAP Business Objects BI Solutions 4.0, and the latest version of the Universe Designer called, universe
design tool and the new metadata modeling tool called, information design tool. For more information, visit
the Business Objects homepage.
Summary
This document summarizes frequent questions for SAP Netweaver Business Warehouse and OLAP
customers on SAP BusinessObjects BI Solutions, especially on the capabilities of the new semantic layer
with SAP BusinessObjects BI 4.0. It is meant compliment the SAP Business Objects product documentation
that is delivered at release.
We welcome your feedback, comments and additional questions.
(Version 3.0, last update, 1 Dec. 2010)
Authors:
Didier Mazou, Elizabeth Imm, Abdellatif Astito,
Company:
SAP
Created on:
18 October 2010
Authors Bio
Didier Mazou is an expert product manager in the semantic layer team at SAP
BusinessObjects Enterprise Information Management. Didier is the expert on most major
OLAP databases, SAP Netweaver BW and relational databases. Before joinging the product
group in 2005 Didier was a strategic pre-sales field representative specializing in closing large
database deals. He currently resides in France and works out of the SAP Lab in Levallois.
Elizabeth Imm has worked in the semantic layer team since 2004. She was global program
lead for SAP BusinessObjects XI 3.0 product documentation and manager of a team of
information developers for information design tool, universe design tool and other semantic
layer tools before becoming a product owner this year.
Abdellatif Astito is a senior program manager at the SAP Labs Paris in Levallois France. Since
joining the company in 2000, he has been responsible for software specification for universe
design tool with a focus on improvements for OLAP database support.
SAP COMMUNITY NETWORK

2010 SAP AG
SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

1
Questions and Answers: SAP Business Objects BI 4.0 and the New Semantic Layer for
Table of Contents
Purpose............................................................................................................................................................... 3
General Questions .............................................................................................................................................. 3
What is the semantic layer? ............................................................................................................................ 3
What is a universe?......................................................................................................................................... 3
How do I create a universe? ........................................................................................................................... 3
What are the main benefits of the semantic layer from an IT perspective? .................................................... 4
What are the main benefits of the semantic layer from a user perspective? .................................................. 4
What are the ways I can access SAP Netweaver Business Warehouse? ..................................................... 5
Can I access SAP Netweaver BW through a universe or native BICS connectivity? ..................................... 5
Do I need to continue to create universes on BEx queries? ........................................................................... 5
Are there differences between universe access and direct access? .............................................................. 5
Do I need to continue to invest in BEx queries? ............................................................................................. 5
What are the major differences between SAP BusinessObjects universes and BEx queries? ...................... 6
What are the client tools that can consume SAP Netweaver BW universes? ................................................ 6
Can I reuse OLAP universes that were created with SAP BusinessObjects Enterprise XI 3.x? .................... 6
What OLAP sources does BI 4.0 support? ..................................................................................................... 6
Do I need specific training to create and/or consume SAP Netweaver BW universes? ................................. 7
Detailed capabilities questions ........................................................................................................................... 7
Is SAP BWs time-dependent master data available in the SAP BusinessObjects semantic layer? .............. 7
Are hierarchies supported in the semantic layer, SAP BusinessObjects Web Intelligence and SAP Crystal
Reports? .......................................................................................................................................................... 7
Is data security addressed for universes that are based on Infocubes? ........................................................ 7
Can I reuse SAP BEx query features?............................................................................................................ 7
What main features are missing for dimensional universes on top of InfoProviders ...................................... 8
Are there BEx query features that are available in universes on Infocubes and if so which ones? ............... 8
What SAP Netweaver BW features are supported by the universes in BI 4.0? ............................................. 9
How do you consume SAP BEx queries? ....................................................................................................... 9
Can you consume SAP BEx queries with SAP BusinessObjects Web Intelligence and SAP Crystal
Reports? .......................................................................................................................................................... 9
Are there restricted features in SAP Business Objects Web Intelligence while using dimensional
universes? ....................................................................................................................................................... 9
Are universes impacted when SAP Infocubes are updated?........................................................................ 10
Is it possible to mix relational data and OLAP data in a single universe? .................................................... 10
Can I use the translated metadata from SAP Netweaver BW in universes? ................................................ 10
What are the differences between SAP Netweaver BW relational universes and SAP Netweaver BW
dimensional universes?................................................................................................................................. 11
What multi-dimensional concepts are used in dimensional universes? ....................................................... 12
Related Content ................................................................................................................................................ 13
Copyright........................................................................................................................................................... 14

2010 SAP AG

2
Purpose
The purpose of this document is to provide brief answers to common questions surrounding SAP Netweaver
BW access in SAP Business Objects Enterprise BI 4.0 and more generally, supported features of OLAP
databases.
This document does not replace the Information Design Tool User Guide released with the product.
This document explains the semantic layer positioning and strategy within the overall SAP portfolio.
General Questions
What is the semantic layer?
The semantic layer is an abstraction layer between the database and the business user that frees the
business users from needing to know the data structures and technical names. It enables business users to
access, interact, and analyze their data regardless of the underlying data sources and their schemas.
The semantic layer encompasses the following elements: universes, query generation, calculator, local
cache (that is, a microcube), query panel, and database connectivity parameters.
What is a universe?
The information design tool is an SAP BusinessObjects metadata design environment that enables a
designer to extract, define, and manipulate metadata from relational and OLAP sources to create and deploy
SAP BusinessObjects universes.
A universe is an organized collection of metadata objects that enable business users to analyze and report
on corporate data in a non-technical language. These objects include dimensions, measures, hierarchies,
attributes, pre-defined calculations, functions, and queries. The metadata object layer, called the business
layer, is built on a relational database schema or an OLAP cube, so the objects map directly to the database
structures via SQL or MDX expressions. A universe includes connections identifying the data sources so
queries can be run on the data. The role of the universe is to provide the business user with semantically
understandable business objects, such as, Customer, Country, Quarter, Revenue, or Margin. The user is
then free to analyze data and create reports using the business objects that relevant to their needs without
requiring knowledge of the underlying data sources and structures.
Universes provide:
Access to all the major relational sources

Support for OLAP sourcesSAP Netweaver BW 7.0, Microsoft Analysis Services 2005 and 2008
General access capabilities via open database connectivity (ODBC)
In summary, a universe:
Facilitates access to information to make it easier to answer business questions

Maintains IT control of the data access
Provides failsafe access to trusted information
Increases the range of information that is accessible to business users
How do I create a universe?

With BI 4.0, universes can be authored with the new universe tool called the information design tool. The
information design tool is an SAP BusinessObjects metadata design environment that enables a designer to
extract, define, and manipulate metadata from relational and OLAP sources to create and deploy SAP
BusinessObjects universes.

2010 SAP AG

3
What are the main benefits of the semantic layer from an IT perspective?
The common semantic layer provides a:
Single point of administration for all data sources
Reduces the cost of delivering BI by leveraging existing IT investments in data

Reduces, postpone or eliminate ETL development cycles
Extends and leverage existing BI platform security model
Promotes schema neutralitydoes not impose any ETL or data warehousing
Provides multi-source universes for relational sources
Common semantic for all
Uses and shares the same concepts and vocabulary independently of the sources and users
Provides consistent modeling workflows and capabilities for all data sources
Trusted and secure environment
Provides data lineage traceable from end-user reports

Supports and extend database security
Extends from development to production cycle
Design environment to empower users and reduce IT bottlenecks
Increases user self-sufficiency and reduce IT bottleneck

Provides predefined and reusable queries, parameters, filters, calculations, list of values etc
What are the main benefits of the semantic layer from a user perspective?
Consistent user experience
Provides same user experience that is independent of the source

Exposes business terminology that is relevant to business users needs (easy to evolve as needs
change)
Reduces costs for training across departments and data domains

Trusted and secure environment
Provides the users with confidence that they always access trusted informationdata lineage
Secures the data, the documents, the queries, the parameters, etc.
Autonomous users
Presents users with user-friendly business terms

Enables users to create and change reports without involving IT
Makes informed real-time decisions possible with up-to-date data
Increases productivity by publishing re-usable queries, calculations, parameters, filters, list of values,
etc.

2010 SAP AG

4
What are the ways I can access SAP Netweaver Business Warehouse?
There are three possible access points depending on your requirements.
Access SAP Netweaver BW by creating:
A direct access to SAP Business Explorer (SAP BEx) queries from the SAP BusinessObjects client
tools using BI consumer services (BICS).
A dimensional universe (.unx file) on SAP Netweaver BW Infocubes.

A relational, multi-source enabled universe (.unx file) based on SQL on the following SAP Netweaver
BW InfoProviders:
o
InfoCubes (CUBE)
MultiProviders (MPRO)
Virtual Providers (VIRT)
DataStore Objects (ODSO)
InfoObjects (IOBJ).
Can I access SAP Netweaver BW through a universe or native BICS connectivity?

Yes, both access methods are permitted in BI 4.0. Both provide a common user view and approach for all
query and reporting needs in the enterprise:
Single access point for the (report creator) user via the Query Panel.
Same formula language
Same metaphor
Common and shared vocabulary
Do I need to continue to create universes on BEx queries?
No, you do not need to build a universe to access SAP Netweaver BW. With BI 4.0, you can gain direct
access to SAP Netweaver BW by selecting an existing BEx query from a catalog of BEx queries. The BEx
query selection is then available in the SAP BusinessObjects query and analysis tools such as SAP
Business Objects Web Intelligence, Crystal Reports or Dashboards. The access method is not SQL or MDX,
but SAPs BICS interface.
Are there differences between universe access and direct access?
Yes, universes are generated and persisted on the SAP BusinessObjects repository for SAP Netweaver BW
Infocubes. Direct access generates an equivalent, temporary, universe structure automatically on the fly, but
they are not persisted and therefore cannot be shared or reused.
Therefore, maintenance for universes is significantly lower as each universe may serve many more users
and reports than a typical BEx query.
Universes need to be synchronized and updated with any Infocube changes.
Universe metadata can be reorganized and renamed. Designers can extend the Infocube by adding
calculated/restricted key figures, variables, pre-defined filters, named sets, etc..
Do I need to continue to invest in BEx queries?
For customers who have already invested heavily in BEx queries, SAP recommends using direct access on
BEx queries (no need for universes).
For new customers or new projects, SAPs suggestion is to evaluate both BEx query and universe solutions
based on the business needs and IT constraints.

2010 SAP AG

5
What are the major differences between SAP BusinessObjects universes and BEx queries?
BEx queries and universes have many similarities in terms of offering advanced analysis functionality.
The main differences are:
Universes provide consistent modeling features across all sources, including SAP Netweaver BW,
non-SAP, OLAP or RDBMS
Universes provide more autonomy to end users by enabling business users, not only IT experts, to
create queries
Multiple relational data sources can be mixed in a single universe to provide unified business user
access across data domains
With universes, maintenance is usually lower as each universe may serve more users and reports
than a typical BEx query
Universes provide a consistent user experience using the same query panel across BI tools (SAP
Business Objects Web Intelligence, SAP Crystal Reports and SAP BusinessObjects Dashboards)
Universes provide the same reporting capabilities for relational and OLAP data sources
In Web Intelligence, data provider synchronization is enabled for direct access to BEx queries,
universes (OLAP and relational data sources), personal data providers
Adds value to the data source by customizing and enriching a business layer that is visible to the
report creator and consumer
BEx queries support more complex SAP Netweaver BW functionalities

Query layout is separated from data access
What are the client tools that can consume SAP Netweaver BW universes?
Dimensional universes (based on SAP Netweaver BW Infoproviders, SAP Netweaver BW Multiproviders and
Microsoft Analysis cubes) can be consumed directly by SAP BusinessObjects Web Intelligence (the applet,
HTML, and the Rich Client), SAP Crystal Reports.
Multisource-enabled universes (based on SAP Netweaver BW InfoProviders, SAP Netweaver BW
MultiProviders, VirtualProviders, DSOs and InfoObjects) can be consumed by SAP BusinessObjects Web
Intelligence (the applet, HTML, and the Rich Client), SAP Crystal Reports, SAP Crystal Dashboard Design
and BusinessObjects Explorer.
Can I reuse OLAP universes that were created with SAP BusinessObjects Enterprise XI 3.x?
Yes. OLAP universes created with BusinessObjects Enterprise XI 3.x will continue to work in BI4 and Web
Intelligence 4.0 users can continue to use those OLAP universes. However OLAP universes can only be
edited using the universe design tool, not the information design tool. Use the upgrade management tool to
move OLAP universes (as you would any universe) from a 3.x repository to the 4.0 repository.
However, in order to take advantage of the new BI 4.0 semantic layer and its multi-dimensional capabilities,
you will need to recreate dimensional universes using the new information design tool.
The distinction is made here between the OLAP universe, created with Universe Designer (BusinessObjects
Enterprise XI 3.x) and dimensional universe, created with information design tool (SAP BusinessObjects BI
4.0).
What OLAP sources does BI 4.0 support?
BI 4.0 supports SAP Netweaver BW and Microsoft Analysis Services (MSAS) cubes. SAP will continue to
add support for additional OLAP databases, particularly for Essbase cubes planned for BI 4.1.

2010 SAP AG

6
Do I need specific training to create and/or consume SAP Netweaver BW universes?
Report consumers do not need any specific training.

Report creators only require a standard training adapted to the client you are using: SAP
BusinessObjects Web Intelligence, SAP Crystal Reports, SAP Business Objects Dashboards, etc.
If you are a designer, you may have to customize SAP Netweaver BW universes generated by
adding pre-defined filters, variable, calculated members/measures, sets, security.
In that case, you need standard information design tool training in addition to basic multi-dimensional
knowledge (including MDX skills).
Detailed capabilities questions

Is SAP BWs time-dependent master data available in the SAP BusinessObjects semantic layer?
Yes. Time dependencies exposed through keydate variables are available if you access SAP Netweaver BW
with SAP BEx queries (via the direct BICS access).
Time dependencies may also be surfaced in Infoproviders (BEx queries are based on Infoproviders)
supported by direct access or relational access.
In order to access Infoproviders, you must generate a default SAP BEx query that contains all
characteristics, hierarchies and key figures.
Are hierarchies supported in the semantic layer, SAP BusinessObjects Web Intelligence and SAP
Crystal Reports?
Yes, with BI 4.0 the semantic layer is fully multi-dimensional, and one of the main objectives of this release.
The concept of hierarchies exists at the universe level and at the query level. Hierarchies are fully supported
for both SAP Infocubes (from which you build a universe) and SAP BEx queries (which you access directly).
This means that all business intelligence clients that consume the semantic layer, i.e., SAP Business Objects
Web Intelligence, and SAP Crystal Reports, gain access to the multi-dimensional metadata. Additionally, the
same hierarchy support is available for universes on Microsoft Analysis Services.
Is data security addressed for universes that are based on Infocubes?
Yes, BI 4.0 introduces a major feature concerning data restriction in dimensional universes in addition to the
existing data restrictions in OLAP cubes that apply data restrictions at runtime.
The security administrator defines and sets data restrictions for each hierarchy by using a member selector.
Multiple data restrictions can be combined and used with AND and OR operators.
Note that the BI authorization variables defined in BEx queries are not available for universes on Infocubes,
therefore the administrator must recreate equivalent security filters for the universe.
Can I reuse SAP BEx query features?
No, because the SAP BEx query features are bound to the SAP Netweaver BW technical elements. Today,
the following added values do not have an exact equivalent in the universe:
Restricted key figures

Calculated key figures
Structures
Variables
Conditions
Exceptions

2010 SAP AG

7
What main features are missing for dimensional universes on top of InfoProviders
BI Authorization
Navigational attributes
Time-dependency (Key date)
Calculated key figures and restricted key figures stored in the SAP Netweaver BW server
Unit and currency conversion
Are there BEx query features that are available in universes on Infocubes and if so which ones?
Yes, in BI 4.0, we provide several BEx query features on universes.
These features need to be created manually for each universe using MDX.
Here is a list of BEx query features that are available for Infocube universes:
Restricted key figures (not all use cases)

Calculated key figures (not all use cases)
Structures (not all use cases)
Variables:
o
Characteristic: single, multiple and interval selection mandatory or optional
Hierarchy node: single, multiple mandatory or optional
Conditions

2010 SAP AG

8
What SAP Netweaver BW features are supported by the universes in BI 4.0?

Please refer to the following table to understand how the metadata maps between BOE XI 3.x and BI 4.0.
Note universes in BII 4.0 may only be created on on Infocubes.
BOE release
Metadata mapping
XI 3.x
BI 4.0
Dimension
Class
Analysis Dimension
Characteristic
Sub-class
Dimension
Hierarchy
Sub-class
Hierarchy
Hierarchy level
Object
NA
Display attribute
Detail
Attribute dimension
Navigational attribute
Object
Attribute dimension
(supported as display
attribute)
Key figure without unit/currency
Measure (numeric)
Measure (numeric)
Measure (numeric)
Measure (numeric)
Property unit/currency
(string)
Property unit/currency
(string)
Object: formatted value

(string)
Property formatted value

(string)
Key figure with unit/currency
How do you consume SAP BEx queries?

SAP BEx queries are accessible only in direct access (BICS). One BEx query connection can be shared by
all clients (SAP BusinessObjects Analysis, SAP Business Objects Web Intelligence, SAP Crystal Reports,
SAP Business Objects Dashboards) and used for multiple BEx queries.
Can you consume SAP BEx queries with SAP BusinessObjects Web Intelligence and SAP Crystal
Reports?
Yes, once the connection is created, the BEx query can be selected from the client tool as if it were a
universe. Of course, direct access on a SAP BEx query does not allow you to rename, modify or add
metadata.
Are there restricted features in SAP Business Objects Web Intelligence while using dimensional
universes?
Yes. The query drill feature is only available for reports created from relational universes. SAP Business
Objects Web Intelligence also provides hierarchy navigation through fold/unfold capability with OLAP
universes. Keep in mind however that the drill will not display additional members unless you edit and
change the member selection to retrieve more members.

2010 SAP AG

9
Are universes impacted when SAP Infocubes are updated?

Yes. Each universe must be updated manually in the information design tool by selecting the Refresh
Structure option. This functionality is carried over from universe design tool on the SAP BusinessObjects
Enterprise 3.x universes (unv).
Universes can be synchronized with data source with several options that can be activated by the user in
who is charge of the update:
Select which objects to update

Keep track of deleted objects by the designer
Overwrite or not properties such as name, description, list of values, etc.
Regenerates deleted objects
At the end of the update process, users can view and select the changes that they want to apply individually
or not. Note that Life Cycle Management only updates metadata that have automatically generated from
cube definition.
Is it possible to mix relational data and OLAP data in a single universe?

No. Multi-source universes are only available for SQL sources at this time. The only exception is SAP BW:
you can build a multi-source universe on a relational source and an SAP BW source as long as the SAP BW
source is accessed through SQL, which is a supported scenario in BI 4.0. Please refer to the question below
for more details on differences between relational and dimensional SAP Netweaver BW universes.
Can I use the translated metadata from SAP Netweaver BW in universes?

It is not possible in BI 4.0 to import OLAP translated metadata in a universe.
However it is possible to generate multiple universes (one per language) and use the XLIFF import/export
capabilities in Translation Manager to merge the different translated metadata.

2010 SAP AG

10
What are the differences between SAP Netweaver BW relational universes and SAP Netweaver BW
dimensional universes?
SAP Netweaver BW (and MSAS) databases are built to be accessed directly by users without an additional
IT layer. The dimensional universe maps the structure of the OLAP cube and provides capabilities in the
universe that are not exposed in the cube. Those capabilities are accessible to all users and can be shared
in any report or query.
The table below compares the SAP Netweaver BW features in the BI 4.0 relational universe to the
dimensional universe.
Feature
Relational
Universe
Dimensional
Universe
NA
YES
Data Foundation
YES
NO
Hierarchies
NO
YES
Custom objects
YES
YES
Native filters
YES
NO
Business filters
YES
YES
Mandatory filters
YES
YES
Use Designer functions in objects or

filters definition: @Prompt, @Select,
@Variable, etc
YES
YES
Automatic update of universes (Life

Cycle Management)
NO
YES
Mandatory prompts in universe
YES
YES
Optional prompts in universe
YES
YES
List of values
YES
YES
Hierarchical list of values
YES
NO
SQL list of values
YES
NO
Business Objects list of values
YES
YES
Static list of values
YES
YES
Object format
YES
YES
Objects restriction
YES
YES
YES *
YES *
YES
YES
Calculated members
NA
YES
Calculated measures
YES
YES
NA
YES
SQL
MDX
Overwrite connection
Row level security (data restriction)

* Authorization variables are not supported
Perspectives
Named sets
Query language

2010 SAP AG

11
What multi-dimensional concepts are used in dimensional universes?

OLAP databases mainly contain dimensions and measures:
A dimension is a collection of data of the same type, allowing structuring a multidimensional

database. SAP uses characteristic as well as dimension.
A dimension may also referred to as an axis.

In a measure, each cell is associated with a single position in each dimension. Dimensions are often
organized in hierarchies.
Time, Customer, Geography and Product are common dimensions.
Measures are stored in a specific dimension called Measures in SAP Netweaver BW and Microsoft.
SAP also uses Keyfigure instead of measure.
The illustration below shows an example of a hierarchy of a dimension.
Years
L
E
V
E
L
S
Quarters
Quarters
Months
Months
1997
Quarters
Quarters
Months
M
E
M
B
E
R
S
Q1
February
Ancestor
Weeks
Weeks
Weeks
Weeks
Parent
Children
Days

2010 SAP AG
Days
Days
Days
Days
Days
Descendants

12
Related Content
For more information, visit the Business Objects homepage.

2010 SAP AG

13
Copyright
Copyright 2009 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

2010 SAP AG

14

Bobj Faq

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Bobj Faq

Загружено:

Авторское право:

Доступные форматы

Questions and Answers: SAP

Business Objects BI 4.0 and the

Didier Mazou, Elizabeth Imm, Abdellatif Astito,

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Access to all the major relational sources

Facilitates access to information to make it easier to answer business questions

How do I create a universe?

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Reduces the cost of delivering BI by leveraging existing IT investments in data

Provides data lineage traceable from end-user reports

Increases user self-sufficiency and reduce IT bottleneck

Provides same user experience that is independent of the source

Reduces costs for training across departments and data domains

Presents users with user-friendly business terms

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

A dimensional universe (.unx file) on SAP Netweaver BW Infocubes.

Virtual Providers (VIRT)

DataStore Objects (ODSO)

Can I access SAP Netweaver BW through a universe or native BICS connectivity?

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

BEx queries support more complex SAP Netweaver BW functionalities

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Do I need specific training to create and/or consume SAP Netweaver BW universes?

Report consumers do not need any specific training.

Detailed capabilities questions

Restricted key figures

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Restricted key figures (not all use cases)

Characteristic: single, multiple and interval selection mandatory or optional

Hierarchy node: single, multiple mandatory or optional

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

What SAP Netweaver BW features are supported by the universes in BI 4.0?

Key figure without unit/currency

Object: formatted value

Property formatted value

Key figure with unit/currency

How do you consume SAP BEx queries?

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Are universes impacted when SAP Infocubes are updated?

Select which objects to update

Is it possible to mix relational data and OLAP data in a single universe?

Can I use the translated metadata from SAP Netweaver BW in universes?

SAP COMMUNITY NETWORK

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

Use Designer functions in objects or

Automatic update of universes (Life

Mandatory prompts in universe

Optional prompts in universe

Hierarchical list of values

SQL list of values

Business Objects list of values

Static list of values

Row level security (data restriction)