1. Introduction

In this article we are describing conversion of XI3.1 relational universe (UNV) to
SAP BO BI4.0 relational universe (UNX).The reader of this article has to be aware that
primary focus of this article is not OLAP universe. The article will reference SAP XI3.1 OLAP
universe only to clarify conversion of this type of universe. The common acronyms that
you could encounter when reading BI4.0 documentation related to the BI4.0 Semantic Layer are:

Acronym

Definition

DSL

Dimensional Semantic Layer

CSL

Common Semantic Layer

MSU

Multi-Source Universes

DF

Data Foundation

BL

Business Layer

IDT

Information Design Tool

UDT

Universe Design Tool

IDT user guide can be found here. It can help reader understand main IDT concepts and above terminology.

BI4.0 Semantic Layer can be referred as DSL or CSL and corresponding universe has extension UNX.
XI3.1 Semantic Layer is legacy Semantic Layer and corresponding universe has extension UNV.
BI4.0 supports both types of universes. Legacy (UNV) and new (UNX) universes could coexist
in the same repository and run on the same BI4.0 server. When conversion of
UNV to UNX is done inside of BI4.0, UNV still exists and it can be used as it is used in XI3.1.

The focus of this article are UNV features/functionalities and their conversion into new BI4.0
universe UNX as well as the best conversion practices.

2. Relational Universe Features Summary

the feature exists or can have a different workflow or name the feature exists partially, has a different workflow or have workarounds the feature does not exist

The information about universe features conversion can be found in
SAP BO BI4.0 Information Design Tool User Guide. The below list shows only those universe features
that could not be converted or have significante changes after conversion. They could be found
in this guide as well. Please refer "Converting .unv universes" chapter for more information on
the subject.

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. The derived universe contains a link to a core universe.
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.

Access Restrictions

When converting a universe in a repository, universe Access Restrictionsare converted into
security profiles that can be edited using the Security Editor:

Object Access Restrictions are converted to Create Query and Display Data settings in
a Business Security Profile.

@ 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 and PRM file(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.
Tip:
Check and reset custom settings to SQL generation parameters in the data foundation properties
and business layer properties. For information on setting SQL parameters, see the related topic in
Information Design Tool User Guide (the link to the document listed above)

Stored procedure Universe

The conversion is not supported. The feature does not exists in BI4.0 DF. The workaround is to use
UNV when you need to use 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 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 to BI4.0 and used the same way it is
used in XI3.1. No changes are required to XI3.1 SAP OLAP UNV universe to be used in BI4.0.
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

Note: The upgrade of XI3.1 SAP OLAP UNV universe to BI4.0 means move of XI3.1 SAP OLAP UNV
file from XI3.1 CMS to BI4.0 CMS and it can be done with BI4.0 Upgrade Manager or by export
to BI4.0 CMS with BI4.0 Universe Design Tool (which is compatible with XI3.1 Universe Designer)

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

3. How to convert a legacy universe UNV

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

Before we go into details about the conversion workflows/scenarios it is highly recommended reading
of the document that summarizes frequently asked questions around the universe (XI3.1 UNV) migration
for the latest release of SAP Business Objects BI4.0. It is the great source of the information and
you should read this document if you planning universe migration project. These are few sample
questions covered in the document (and there are many more in the document):
How do I convert a universe (UNV) from an SAP Business Objects Enterprise XI R2 or XI 3.x CMS to
SAP Business Objects 4.0 (BI 4)?
How many universe authoring tools are delivered with BI 4?

Conversion with IDT

CMS repository (recommended for converting a universe along with its security items)

After converting a UNV universe, it is recommended to run a check integrity in the ITD tool on
the converted universe. Certain errors in the check integrity results can be resolved by following
the best practices described in IDT User Guide chapter
"3.4 Tips for resolving check integrity errors after converting .unv universes"

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
The conversion of legacy XI3.1 universe UNV shown on the above image will produce BI4.0 universe
in BI4.0 repository with extension UNX. If UNX is edited with IDT tool, UNX becomes three local files/resources
with following extensions:

CNX files for local connections (CNS files for secure connections)

DFX files for Data Foundations

BLX files for Business Layers

Note: In order to be able to publish UNX universe to the repository you need to use secure connection
which has CNS extension. Please refer IDT User Guide for more info on different BI4.0 connection types

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.

Convert UNV universe from File

Information Design Tool allows you to convert a UNV universe file without requiring a CMS (logon into the repository).

The best practices after conversion

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 to follow for two possible
solutions are described in IDT User Guide.

WebIntelligence reports

BI4.0 Upgrade Manager tool is used to migrate XI3.1 WebIntelligence reports from XI3.1 repository to
BI4.0 repository. The reports and corresponding universes (UNV) are migrated as is and could run on
BI4.0 platform as is. The conversion of UNV universe to UNX universe will not impact migrated XI3.1
WebIntelligence reports. Migrated XI3.1 WebIntelligence reports are still pointing to UNV universe
when UNV is converted to UNX. XI3.1 migrated reports have to be edited and manually pointed to UNX
in order for them to become BI4.0 WebIntelligence reports. Below image shows how to edit XI3.1
WebIntellignece report in BI4.0 and change source. UNV has to be replaced with corresponding UNX
version of the UNV universe.

Note: You have to be in Data mode to be able to change webi report source

The conversion of XI3.1 WebIntelligence reports to BI4.0 WebIntellignece reports is not mandatory.
As mentioned before, XI3.1 WebIntelligence reports will run on BI4.0 server as they do on XI3.1
server. The described procedure could be used as reference for those projects when there is need
for full migration of all webi reports to BI4.0.

Crystal Reports

BI4.0 Upgrade Manager tool is used to migrate legacy Crystal Reports contents from XI3.1 repository
to BI4.0 repository in Crystal Reports 2011 format. The reports and corresponding database connectivity
(including universes (UNV)) are migrated as is and could run on BI4.0 platform as is.
i.e.
Crystal Reports 2008 directly consuming RDBMS data on XI 3.1 gets migrated as Crystal Reports 2011
directly consuming RDBMS data on BI 4.0. Crystal Reports 2008 consuming UNV universe against RDBMS on
XI 3.1 gets migrated as Crystal Reports 2011 UNV universe against RDBMS on BI 4.0.
The conversion of UNV universe to UNX universe will not impact migrated Crystal Reports.
The migrated XI3.1 Crystal Reports are still pointing to the original datasource (RDBMS or UNV universe).
When you wish to convert UNV universe to UNX universe in order to take advantage of new semantic layer features,
you need to convert Crystal Reports 2011 to Crystal Reports for Enterprise through a wizard
"Connect to the Common Semantic Layer" provided within Crystal Reports for Enterprise.
If open the legacy reports (Crystal Reports 2008 or Crystal Reports 2011) in Crystal Reports for Enterprise
designer, "Connect to the Common Semantic Layer" wizard starts automatically.
This wizard allows you to map the original fields (RDBMS or UNV universe objects) to corresponding UNX universe objects.
Below image shows "Connect to the Common Semantic Layer" wizard in Crystal Reports for Enterprise.Note: You need to open legacy reports in Crystal Reports for Enterprise designer in order to map existing fields
to UNX universe object through "Connect to the Common Semantic Layer" wizard.
The conversion of Crystal Reports 2011 to Crystal Reports for Enterprise is not mandatory.
As mentioned before, Crystal Reports 20011 will run on BI4.0 server as they do on XI3.1 server.
The described procedure could be used as reference for those projects when there is a need for converting Crystal Reports 20011
(with UNV universe) to Crystal Reports for Enterprise (with UNX universe) within BI4.0.

Guest

Guest

Yes, should be no different.

The catch here for CR is that UNV is supported by CR2011 and UNX is supported by CR for Enterprise. Once you migrate to UNX, you will also have to open/save your reports inside CR for Enterprise to convert the report format. There is no converter as we rely on the set location workflow to map you reports from a UNV source to a UNX source. Saving will convert the report format into a CR for Enterprise (next-gen) report.

A good and safe practice would be to convert the reports/universes to 4.0 UNV first, and ensure they are working with CR2011. Then, when ready, perform the UNV-to-UNX conversion and move over the reports over one by one.