SAP BO BI4.0 UNV to UNX Universe Conversion Relational DB

SAP BO BI4.0 UNV to UNX Universe Conversion

Relational DB

Sinisa Knezevic

April, 2011

© 2011 SAP AG. All rights reserved. 2

Agenda

Introduction

Semantic Layer vs. universe

BI4.0 Acronyms

UNV vs. UNX

How to convert a legacy universe UNV

Starting a UNV conversion

Convert UNV universe from CMS (Scenarios 1&2)

Convert UNV universe from File

UNV features conversion summary

Features not converted

Best practices after conversion

Tips to know

Impact on Webi/Crystal/Deski reports and Xcelsius dashboards

UNX New Features

Demo


Introduction

Semantic Layer vs. universe

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 the universe?

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 role of the universe is to provide the business user with

semantically understandable business objects, such as, Customer, Country, Quarter.

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.


Introduction

BI4.0 Acronyms

Acronym Definition

DSL Dimensional Semantic Layer

CSL Common Semantic Layer

MSU Multi-Source Universe

DF Data Foundation

BL Business Layer

IDT Information Design Tool

UDT Universe Design Tool


Introduction

UNV vs. UNX

The conversion of the relational UNV to UNX universe

XIR2/XI3.1/BI4.0 UNV universe

• universe file with extension .unv

• corresponds to legacy semantic layer

• single universe file when exported or edited

• connection (secured, personal, shared)

• Authoring tools: XI3.1 Universe Designer or BI4.0 Universe Design Tool

SAP BO BI4.0 UNX universe

• universe file with extension .unx

• corresponds to new semantic layer (CSL/DSL)

• single file when published, three files/resources when edited in IDT CNX file for local connection (CNS file for secure connection)

DFX file for Data Foundation - The DF is the dedicated part of the Semantic Layer to model data sources

BLX file for Business Layer - The BL is visible part of the Semantic Layer to the end users

• connection (secured, local)

• Authoring tool: BI4.0 Information Design Tool



Starting a UNV conversion

Information Design Tool provides the ability to convert a UNV universe from:

• The CMS repository - recommended for converting a Universe along with its security items.

• The file system - allows you to do a conversion of a UNV file that was saved for all users

(using a shared or personal connection).

To start the conversion go to the File menu.

Launching the

conversion



Convert UNV universe from CMS - Scenario 1

In this scenario, we use Upgrade Manager to move the XI3 CMS content to

the new BI4 CMS repository.

XI3 CMS

Information

Design Tool

UniverseDesigner XI3 Retriev

e

Warehouse.unv

Export

BI4 CMS

UNV files

Convert

UNX universe

Warehouse.unx

Upgrade

Upgrade Manager

UNV universe

Warehouse.unv

Local

resources



Convert UNV universe from CMS - Scenario 2

In this scenario, we use Universe Design Tool BI4 to export a UNV Universe

into the BI4 CMS repository. That UNV Universe can then be converted into a

UNX Universe using Information Design Tool.

Information

Design Tool

Universe Design Tool BI4

Retrieve

Export

BI4 CMS

UNV files

Convert

UNX universe

Warehouse.unx

UNV universe

Warehouse.unv

Local

resources



Convert UNV universe from File

Information Design Tool allows you to convert a UNV universe file without

requiring a CMS.

Information Design Tool BI4.0

UniverseDesigner XI3

Convert

Save for all users








@Script

• Recovers the results of an executed script created in the XI3.1 Desktop Intelligence

module. Desktop Intelligence does not exist in SAP BO BI4.0, so there is no need for this

function.

Strategies

• Custom strategies are not supported in .UNX universes.

Parameter (Customizations)

• Customizations to SQL generation parameter settings in the PRM file or in the universe

parameters are not converted. You can add customized values to the converted PRM file,

and customize universe parameter settings in the converted universe using the Information

Design Tool.

Stored Procedure Universe

• The conversion is not supported. BI4.0 UNX does not support stored procedure. The

workaround is to use UNV if you need SP.




Universe based on a Data Federator source

• The conversion is not supported. The workaround is to create the BI4.0 multi-source universe

with IDT tool against the same data sources. In that way you will leverage Data Federator

embedded into BI4.0 platform

Business Views

• The conversion of Business Views created with Business View Manager XI 3 is not supported.

Javabean Universe

• The conversion is not supported. The workaround is to create BI4.0 UNX universe with IDT tool

by using Java Beans middleware.

OLAP Universe

• The conversion of the XI3.1 SAP OLAP UNV universe to BI4.0 OLAP UNX universe is not

supported. XI3.1 SAP OLAP UNV universe can be upgraded with BI4.0 Upgrade Manager to

BI4.0 and used the same way it is used in XI3.1. The users of BI4.0 have additionally option to

reuse SAP BEx query (used to create XI3.1 SAP OLAP universe) with BICS connection in BI4.0

WebIntelligence to access the same SAP BW data

Universe password

• The feature is not supported in BI4.0




Universe scheduled auto save

• The feature is not supported in BI4.0

Advanced joins

• The filters in FROM. The feature is not supported in BI4.0

Linked universe (core and derived)

• A core universe is converted like any .UNV universe. The conversion of a core universe does

not trigger the conversion of the derived universes that depend on it. A derived Universe is

converted via the "Convert from CMS" path. When you convert a derived universe, the

conversion automatically includes all core universes that the derived universe is linked to. You

do not need to convert the core universes ahead of time as a separate step. The data

foundation of the converted universe contains all the tables and joins from all core universes

and any tables, joins, or contexts that were defined in the derived universe. The business layer

contains all classes, objects, and conditions from all core universes including the classes,

objects and conditions that were defined in the derived universe.



Best practices after conversion

Check integrity

• After converting the universe, it is recommended to refresh the structure of the data

foundation and run a check integrity in the Information Design Tool on the converted

universe. Certain errors in the check integrity results can be resolved by following the best

practices described below.

• Errors on column data types - Refresh the structure in the data foundation just after the conversion.

This avoids data-type errors in the integrity check.

• Errors on self-joins with @Prompts - If a join expression in the .unv universe contains an @Prompt

with a list of values referring to an object, the converted join needs to be reworked in the data

foundation. The steps for two possible solutions are described in IDT User Guide



Tips to know

Multilingual Universe

• In XI3, one can translate UNV Universe metadata using Translation Manager in order to

obtain a multi-lingual Universe. When converting a multi-lingual Universe, all the translated

strings regarding the universe metadata are converted as well as the language and locale

settings.

Access Restrictions

• When converting a universe in a repository, universe Access Restrictions are converted into

security profiles that can be edited using the Security Editor.

• Access Restrictions (except object restrictions) are converted to settings in a Data Security

Profile.

• Object Access Restrictions are converted to Create Query and Display Data settings in a

Business Security Profile.

Connections

• When converting a universe in a repository, the same secured relational connection is used

by both the .unv and .unx universes. Relational connections can be created and shared by

the universe design tool and the information design tool. The connections are published in

the same Connections folder in the repository. When converting a locally-stored (non-

secured) universe, personal and shared connections are converted to local connections


Impact on Webi/Crystal/Deski reports and Xcelsius

dashboards

WebIntellignece reports

• No impact on migrated XI3.1 WebIntelligence reports (still linked to the .unv universe).

• The .unv universe is preserved after conversion.

• The XI3.1 migrated reports have to be edited and manually pointed to UNX in order for

them to become BI4.0 WebIntelligence reports.

• The conversion of XI3.1 WebIntelligence reports to BI4.0 WebIntellignece reports is not

mandatory.

Crystal Reports

• The conversion of UNV universe to UNX universe will not impact migrated CR

• CR 2008 consuming RDBMS or UNV data on XI 3.1 gets migrated as CR 2011 consuming

RDBMS or UNV data on BI4.0.

• The migrated XI3.1 CR are still pointing to the original datasource (RDBMS or UNV

universe).

• Conversion of CR 2011 to CR for Enterprise is done through a wizard "Connect to the

Common Semantic Layer” which open automatically if CR 2011 is open with CR for

Enterprise.


Impact on Webi/Crystal/Deski reports and Xcelsius

dashboards

DesktopIntelligence reports

• The XI3.1 Desktop Intelligence reports are not supported in SAP BO BI4.0. They have to

be converted to WebIntelligence report and complete information can be found here

http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+from+Desktop+Intelligence+to+Web

+Intelligence

Xcelsius dashboards

• No impact. Flash files will continue to work.

• Conversion to new format is optional

• Conversion adds new features (globalization, UNX queries…)

http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+from+Desktop+Intelligence+to+Web+Intelligence

http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+from+Desktop+Intelligence+to+Web+Intelligence


UNX New Features


UNX New Features

Prompts / LOV

Prompts

• The prompts are now standalone metadata

• The prompts defined in previous universes version are supported and migrated as is

• It is now possible to create prompts without writing any code respecting (simple syntax)

• The prompt editor offer ability to choose any of the available lists of values.

• The option to automatically create a named parameter for the prompt in the business layer

List Of Value

• The LOVs are now standalone metadata

• Exists in the Business Layer and the Data Foundation

• Several types of LOVs

LOV types XI 3.x BI 4.x

Default list of values Supported Supported

Custom SQL Supported Supported

Business Objects using query panel Supported Supported

Business Objects based on custom hierarchy (any

value selection at any level depth)

Not supported Supported

Static Not supported Supported


UNX New Features

Context

XI3.1 Context

BI4.0 Context


UNX New Features

Universe View

Why use Linked Universes?

• To avoid large universes (universes that hold thousands of objects), customers are using

the linked/derived universes that allow having a core universe that is than extended to the

linked universes

Linked universes is a feature that is difficult to maintains

Universe View – The new feature in BI4.0.

• Universe view behaves like a universe but only exposes part of universe metadata.

• It is possible to create as many Universe views as needed and apply authorizations to

those views.

• Users could have access to Universe views and restrict access to the whole universe.

In a Universe view it is not possible to:

• Rename objects

• Add/Delete/Rename folders

• Reorganize the structure

• Change objects formatting


UNX New Features

Universe View


References:

BOPedia article “Conversion of the relational universes in BI 4.x, from UNV

to UNX”

http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+of+the+relational+univ

erses+in+BI+4.x%2C+from+UNV+to+UNX

What you need to know when you migrating universes to SAP BO BI4.0

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/804766e9-8dbe-2d10-

a691-82af1e70effd

For information on Linked and Core Universes, check out the section

“Linking universes” of the Universe Designer guide at

http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-

1_designer_en.pdf

http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+of+the+relational+universes+in+BI+4.x,+from+UNV+to+UNX

http://wiki.sdn.sap.com/wiki/display/BOBJ/Conversion+of+the+relational+universes+in+BI+4.x,+from+UNV+to+UNX

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/804766e9-8dbe-2d10-a691-82af1e70effd









http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_designer_en.pdf



Thank You!

Contact information:

Sinisa Knezevic

RIG Specialist

SAP Technology RIG Americas

3460 Hillview Ave.

Palo Alto, CA 94304, USA

T +1 650 856-5344

[email protected]

Documents

SAP BO BI4.0 UNV to UNX Universe Conversion Relational DB