Conversion of the relational universes in BI 4.x, from UNV to UNX

Page restrictions apply Attachments:8 Added by Sinisa Knezevic, last edited by Sinisa Knezevic on Apr 08, 2011  (view

change)

Product versions:SAP BusinessObjects BI4.0*Main Contributors: Sinisa Knezevic, Tamotsu Nagata, Patrice Le Bihan *

1. Introduction 2. Relational Universe Features Summary

o Linked universe (core and derived) o Access Restrictions o @ Script o Strategies o Parameter and PRM file(Customizations) o Stored procedure Universe o Universe based on a Data Federator source o Business Views o Javabean Universe o OLAP Universe o Universe password o Universe scheduled auto save o Advanced joins

3. How to convert a legacy universe UNV o What you need to know when you migrating universes to SAP BO BI4.0?

Link to this Page Link Tiny Link Wiki Markup Close Move Page – ‘Con

Set Page Location Move OK Cancel Click to select the Search

Recently View ed There w ere no re Know n Location The specif ied pag Brow se Error reading the

You could try relo HTTP Status You must make a Failed to retrieve There w ere no pa Show ing <b>{0}<

Move failed. Ther You cannot move Conversion of the Clients and Sema BOBJ

Business Intellige You cannot move Page Ordering Back Reorder Move

Unknow n user or Page Restrictions Editing restricted Cancel Close Save

139821073

view

o UNV vs. UNX o Conversion with IDT o Convert UNV universe from CMS (Scenario 1) o Convert UNV universe from CMS (Scenario 2) o Convert UNV universe from File o The best practices after conversion

4. Impact of a conversion to the BI Clients - WebIntelligence, Crystal Reports, Desktop Intelligence

o WebIntelligence reports o Crystal Reports o Desktop Intelligence reports

1. Introduction

In this article we are describing conversion of XI3.1 relational universe (UNV) toSAP BO BI4.0 relational universe (UNX).The reader of this article has to be aware thatprimary 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 thatyou 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 coexistin the same repository and run on the same BI4.0 server. When conversion ofUNV 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.0universe UNX as well as the best conversion practices.

2. Relational Universe Features Summary

the feature exists or can have a different workflow or namethe feature exists partially, has a different workflow or have workaroundsthe feature does not exist

New Features of BI 4.0 XI3.1 Functional

area XI3.1(UNV)

BI4.0 (UNX)

BI4.0 Functional area

Project   Project Shared Project   Project Data Foundation   Universe Context Universe DF Calculated column   DF Data Foundation view   DF List of Values as standalone and shareable metadata

  DF/BL

Prompts as standalone and shareable metadata

  DF/BL

DF advanced search   DF View data Universe DF Comment   DF Family   DF Business Layer   Universe Universe view   BL Attribute Universe outline BL Folder Universe outline BL Query   BL Navigation Paths Hierarchies BL

Features which are fully converted

XI3.1 Functional area

XI 3.1 (UNV) BI 4.0 (UNX)

BI4.0 Functional area

Dimensions Universe outline BL Measures Universe outline BL Tables Universe schema DF Alias tables Universe schema DF Derived tables (including nested derived tables)

Universe schema DF

Joins (including shortcut joins)

Universe schema DF

@Aggregate_Aware BO functions BO functions/BL @DerivedTable BO functions BO functions/BL @Prompts BO functions BO functions/BL @Select BO functions BO functions/BL @Variable BO functions BO functions/BL @Where BO functions BO functions/BL Controls - Query Limits Universe BL

parameters

SQL restrictions Universe parameters

DF/BL

Lists of values Universe DF/BL Multilingual universe Universe Universe Connections Connections Connections

Features which are fully converted but with changes

XI3.1 Functional area

XI 3.1 (UNV) BI 4.0 (UNX)

BI4.0 Functional area

Self-joins Universe schema DF Contexts Universe schema DF Classes and sub classes Universe outline BL Details Universe outline Attributes/BL Conditions Universe outline Filters/BL Linked universe (core and derived)

Universe  

Access Restrictions Security Security Profiles/Security

Security assignments and priority

Security Security

Features which cannot be converted

XI3.1 Functional area

XI 3.1 (UNV) BI 4.0 (UNX)

BI4.0 Functional area

@Script BO functions  

Strategies (Custom)Universe parameters

DF

Parameter and PRM file(Customizations)

Universe parameters

Parameters/DF

Stored procedure Universe Universe  Universe based on a Data Federator source

Universe Universe

Business Views    Javabean Universe Universe Universe OLAP Universe Universe Universe Universe password Options/Save  Universe scheduled auto save Options/Save  Advanced joins Joins  

InfoThe 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 nottrigger the conversion of the derived universes that depend on it.A derived Universe is convertedvia 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 thatthe derived universe is linked to. You do not need to convert the core universes ahead of time asa separate step.The data foundation of the converted universe contains all the tables and joins from all coreuniverses 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 includingthe classes, objects and conditions that were defined in the derived universe.

Access Restrictions

When converting a universe in a repository, universe Access Restrictionsare converted intosecurity 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 ina 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 parametersare not converted. You can add customized values to the converted PRM file, and customizeuniverse 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 propertiesand business layer properties. For information on setting SQL parameters, see the related topic inInformation 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 useUNV 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 IDTtool 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 byusing 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 isused 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 UNVfile from XI3.1 CMS to BI4.0 CMS and it can be done with BI4.0 Upgrade Manager or by exportto 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 readingof the document that summarizes frequently asked questions around the universe (XI3.1 UNV) migrationfor the latest release of SAP Business Objects BI4.0. It is the great source of the information andyou should read this document if you planning universe migration project. These are few samplequestions 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 toSAP Business Objects 4.0 (BI 4)?How many universe authoring tools are delivered with BI 4?

Questions and Answers about UNV conversion

UNV vs. UNX

XI3.1 universe

corresponds to legacy semantic layer single universe file when published or edited universe file with extension .unv connection (secured, personal, shared)

SAP BO BI4.0 universe

corresponds to new semantic layer (DSL/CSL) 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 BLX file for Business Layer

universe file with extension .unx connection (secured, local)

Conversion with IDT

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

The file system 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 onthe converted universe. Certain errors in the check integrity results can be resolved by followingthe 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 universein BI4.0 repository with extension UNX. If UNX is edited with IDT tool, UNX becomes three local files/resourceswith 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 runa check integrity in the Information Design Tool on the converted universe. Certain errors in the checkintegrity results can be resolved by following the best practices described below

Errors on column data typesRefresh the structure in the data foundation just after the conversion. This avoids data-type errors inthe integrity check.

Errors on self-joins with @PromptsIf 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 possiblesolutions are described in IDT User Guide.

4. Impact of a conversion to the BI Clients - WebIntelligence, Crystal Reports, Desktop Intelligence

WebIntelligence reports

BI4.0 Upgrade Manager tool is used to migrate XI3.1 WebIntelligence reports from XI3.1 repository toBI4.0 repository. The reports and corresponding universes (UNV) are migrated as is and could run onBI4.0 platform as is. The conversion of UNV universe to UNX universe will not impact migrated XI3.1WebIntelligence reports. Migrated XI3.1 WebIntelligence reports are still pointing to UNV universewhen UNV is converted to UNX. XI3.1 migrated reports have to be edited and manually pointed to UNXin order for them to become BI4.0 WebIntelligence reports. Below image shows how to edit XI3.1WebIntellignece report in BI4.0 and change source. UNV has to be replaced with corresponding UNXversion 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.1server. The described procedure could be used as reference for those projects when there is needfor 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 repositoryto 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 2011directly consuming RDBMS data on BI 4.0. Crystal Reports 2008 consuming UNV universe against RDBMS onXI 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 Enterprisedesigner, "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 fieldsto 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.

Migrating a UNV to a UNX Universe

Posted in BI Blog on July 05, 2011 by Eric Vallo

I've been having a lot of fun with the new Information Design Tool in the SAP BusinessObjects BI4 platform. While I am working on something new and cool, I took a brief tangent to take an old universe to the next level….a UNX based universe in BI4.

This is a learning experience. For whatever reason, my brain is wired to try first, read later. Maybe I'm not alone. In this case, I'm going to walk you through my first exposure to migrating a UNV into the UNX format.

If you want to jump to the fix before you go through the steps here, go to the punch line, then come back here.

For starters, I created a new project within the Information Design Tool to migrate our handy-dandy Activity - Reloaded universe. Yeah, it's obsolete as of BI4 with the new Auditor schema, but the data is still there and good from my old XI systems, so for now, it is a keeper.

Name the new project in your workspace (think like Eclipse, because you are really building an Eclipse-like workspace here). After you get a valid name in, click Finish.

Before we go on, pay attention to that Project Location.  Thinking out loud here, it may be far easier to keep this content in a location on your file system that is easier to navigate to.  Perhaps you want to check this stuff in and out of source control?  Wouldn't that be awesome?  With the project created, the Information Design Tool should now have your project ready to go.

Now we're ready to get that .UNV file pulled into our project.  Get back to the File menu and select "Convert .unv Universe' to get the process going.

You ultimately have two options to choose from in converting the UNV file.  Work with a local universe, or import from a repository.  Since I've already migrated this universe using the Upgrade Management Tool, I'll grab it from the repository using the right-most icon.

It seems as though even though I have a session open with the CMS, it wants me to authenticate again.  I'm presuming this gives me the flexibility to go to another source system at this step.  Again, already on that system, I'm using the same.

I have four universes in UNV form on this system. I've selected Activity - Reloaded.  Click OK to continue.

While pulling in that universe, you must select the destination repository folder and destination local project folder.  Be sure to pick the right project we created above (two screenshots follow to wrap up this step).

Now we are cooking.  Click OK to convert.

Oops.  Despite having actually read the documentation on this piece, it seems that just using the Upgrade Management Tool did not make my connection work correctly. Easy enough to fix.

My next move to debug this was to go ensure I could import it in the old-school Universe Design Tool. Now, while I could screenshot this all day long, if you are here, you probably already know this part. Import the universe you wish to upgrade from the BI4 environment, and simply export it again. That upgrades your repository objects (connection and universe) to the BI4 UNV and puts them back.

Alright, lesson over.  Wash, rinse, and repeat up until now.  Then...

Woo hoo!  Your UNV is now a UNX.  The Information Design Tool has created the necessary connection, data foundation, and business layer in your project to get you going.

Many of us are still finding our way through mastering this tool.  I'm settling into a folder structure that separates my connections from my data foundations from my business layers.  See my structure here.

Note one more really cool thing.  I mentioned this way back in a Diversified Semantic Layer podcast on the new universe.  You can now also include other folders and files in your projects.  Will they play well and export to a shared repository?  It sure seems like it.  Awesome.

Now, restructuring the objects in my project doesn't come without a price.  The first thing you'll note is that the data foundation has lost its reference to the connection, which indicates an unresolved reference.  You'll also note that objects in the business layer referencing this data foundation indicate in red and will not validate.

To fix this, simply open the data foundation and edit its properties.  If you paid attention that you can have all these objects open at one item, just click the right tab.  Once open, click the properties button.

The simple fix is to put a check in the right connection (note, if more than one connection exists in your project, it is listed here).  Select the right one and click OK to fix the data foundation.

Returning to the business layer, the connection works now, objects can now be edited, and we are ready to go again.

That's the skinny on moving from a UNV to a UNX.  It's not absolutely perfect yet, but perhaps the final GA build will be.

I have more Information Design Tool blog posts coming after this one.  Stay tuned.