If you still run .unv universes in your SAP BusinessObjects environment, you’ve probably already seen the news: BI 2025 no longer supports them. Only .unx universes (created in Information Design Tool) are compatible.

This article is a concrete field report on converting .unv universes to .unx. No general theory — real problems and tested solutions.

Why conversion isn't a simple click

SAP provides a built-in conversion tool in Information Design Tool (IDT). In theory, you simply import a .unv and IDT generates an equivalent .unx. In practice, this tool works correctly for simple universes (single source, few contexts, no @ functions) but fails on anything more complex.

Contexts and aliases are the first friction point. In Universe Design Tool, contexts resolve loops in the database schema. IDT has a different approach to contexts, and the automatic conversion doesn’t always produce the expected result.

Calculated objects with @ functions (@Select, @Where, @Variable) are the second problem. These functions specific to the .unv ecosystem don’t always have a direct .unx equivalent. The conversion requires manual rework of the business layer.

Finally, multi-source universes (data federations) require specific handling. A .unv universe is by definition single-connection. If you have universes combining data from multiple sources, the migration to .unx involves rethinking the data foundation architecture.

The method that works: batch-based with cross-validation

The approach we recommend rests on three principles. First, never convert all universes at once. Proceed in batches of 5-10 universes, starting with the simplest to build confidence and refine the process.

Second, each converted universe is validated by query comparison. Identify the 5-10 most-used WebI reports that consume that universe. Run these reports on the original .unv and on the new .unx. Compare results row by row.

Finally, WebI reports must be mass-repointed to the new .unx universes. SAP provides an API for this, but tools like Wiiisdom 360View or BI Platform Support Tool (BPST) do it more efficiently at scale.

The realistic timeline

For a mid-size environment (30-50 universes, 500-1,000 WebI reports), the full conversion typically takes 3-5 months alongside production. This timeline includes conversion, validation, report repointing, and user acceptance testing.

The key lesson: don’t wait until the day of the BI 2025 migration to discover conversion problems. Start the project at least 6 months before any major version upgrade.

Important note: if you’re still on BI 4.2, UNV → UNX conversion must be completed before the version migration. Migrating to BI 4.3 SP05 then converting universes is the recommended order because BI 4.3 still supports both formats.