What is a .unx universe?
When you publish/create a universe using the information design tool, which compiles the business layer, the data foundation, and the connections into a single universe file with a file name of <universe name>.unx. This is called a .unx universe and UNX universes are also referred as common semantic layer (CSL).
Universe created / Published using Information Design Tool (IDT) has below resources.
• Connection Shortcut
• Data Foundation (DF)
• Business Layer (BL)
UNX new features in BO 4.0
Below is the UNX conversion features summary.
Features which are not converted to UNX
@Script – @scripts are used to recovers the results of an executed script which is created in the XI3.1 Desktop Intelligence reports. Desktop Intelligence does not exist in SAP BO BI4.0, so there is no need for this function.
Strategies – Custom strategies (universe Parameters) are not supported in .UNX universes.
Parameter (Customization) – Customization 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 Stored Procedure.
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 WebI 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.
Impact on Webi/Crystal/Deski reports and Xcelsius
Web Intelligence reports – No impact on migrated XI3.1 Web Intelligence reports (still linked to the .unv universe). You have to edit and manually point Webi reports to UNX in order for them to become BI4.0 Web Intelligence reports.
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 data source (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.
Desktop Intelligence reports – The XI3.1 Desktop Intelligence reports are not supported in SAP BO BI4.0. They have to be converted to Web Intelligence report and complete information can be found here.
Xcelsius dashboards – No impact to Xcelsius Dashboard and Flash files will continue to work. Conversion to new format is optional and it adds new features (globalization, UNX queries…)
UNV vs UNX Comparison
How to convert UNV to UNX?
Information Design Tool provides the ability to convert a UNV universe from:
Option 1: The CMS repository -recommended for converting a Universe along with its security items (Method 1 – using Upgrade Manager Tool & Method 2 – Using Information Design Tool).
Option 2: 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) (using Information Design Tool).
Convert Universe from CMS – Upgrade Manager Tool & Information Design Tool
We can use Upgrade Manager tool to move the XI3.1 CMS content to the new BI4.0 CMS repository and then convert UNV universe to UNX universes using Information Design Tool (IDT).
Convert Universe from CMS –Information Design Tool
We can 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 Universe from File (local universe File) –Information Design Tool
Information Design Tool allows you to convert a UNV universe file without requiring a CMS.
Universe Validation after conversion
• After converting the universe, do integrity check and refresh universe structure to get updated structures and verified the tables.
• Validate the access restriction Information Design Tool.
• Test and validate the universe connection in Information Design Tool.
Please share your comments.