Skip to content

Upgrade Readiness

Upgrade Readiness compares a source and a target environment for a BI 4.3 to BI 2025 move: what is not migrated yet, what drifted after promotion, and which content is broken or at risk before you test.

Image of the Upgrade Readiness page with the source/target selector, tiles, Readiness matrix, Before / after and the affected list

../../images/web-console/insights/upgrade-full.png

What it answers

  • Which reports in the source are not in the target yet?
  • Which promoted objects changed on one side after promotion?
  • Which WebI documents still use UNV universes, and which UNV universes have no UNX twin?
  • Which documents are already broken (missing universe, cannot be opened, failed data providers)?
  • Which documents were saved by BI 2025 and will not open on BI 4.3 if you roll back?
  • Which documents use custom SQL or Business Views, and which UNX universes have no row or time limit?

Open it

In the BusinessObjects console, select Insights > Upgrade Readiness.

Filters

Filter Values Effect
Source / Target environment lists, with a swap button The pair being compared. Defaults to the first two environments. A warning shows when both are the same.
Folder path contains text, press Enter Limits the comparison to folders whose path contains the text.
Environments one button per environment Extra environment columns in the Readiness matrix (none selected = all).
Window 30d, 90d, 180d, 365d Window for the use columns in the affected list.

Panels

Panel What it shows Source
Not yet in target Source reports with no match in the target by CUID or by name and folder; notes how many were re-created rather than promoted. CMS metadata, both environments
Drift since promotion Objects with the same CUID on both sides where one copy was saved later. CMS metadata
source WebI on UNV Source WebI documents on a UNV universe. Document processing
source universe already gone Source WebI documents whose universe no longer exists. Document processing
source WebI that will not open Source WebI documents the document parser could not open. Document processing
One-way door Documents saved by WebI 14.4 (BI 2025), which BI 4.3 refuses. Document processing
Readiness matrix Checks (rows) by environment (columns). Click a number for the affected list. All of the above
Before / after Source versus target by status: Only in source, Re-created in target, In both unchanged, Source changed since, Target newer, Only in target; per object type (Reports, Universes, Connections). CMS metadata
Affected list / diff list The objects behind the clicked number: type, name, kind, folder, why listed, updated, CUID, people and service-account uses, last use; or for the diff, status and update time on each side. All of the above

Image of the Readiness matrix with the check groups and two environment columns

../../images/web-console/insights/upgrade-matrix.png

Image of the Before / after panel for one source and target pair

../../images/web-console/insights/upgrade-before-after.png

Readiness checks

Group Checks
Inventory WebI documents, Crystal reports, Publications, Excel / PDF / text files, Analysis for Office workbooks, UNX universes, Connections, Recurring schedules
Documented BI 2025 change Analysis edition for OLAP workspaces; UNV universes; WebI documents on a UNV universe; UNV with no UNX twin in its folder; UNV already paired with a UNX
Broken before you move WebI on a universe that no longer exists; WebI the parser could not open; Saved by a newer WebI, unreadable here; WebI with failed data providers
Risk to review WebI with custom or freehand SQL; Crystal reports on Business Views; UNX missing a row or time limit; UNX with no row and no time limit
Coverage WebI not deep-parsed by MetaMiner (0 means every check saw every document)

Only the "Documented BI 2025 change" group reflects changes SAP documents for BI 2025; hover a check for the basis. Everything else is marked for review, never as a blocker. UNV limits are not checked because the on/off flag is not captured.

TODO: confirm the BI 2025 statements against the current SAP BI 2025 administrator guide

Source to check: SAP BI 2025 admin guide (AOLAP removal, Universe Design Tool removal, SAP Note 3520314).

Export

Export the affected or diff list with Excel or CSV, or copy the SQL. See Insights Dashboards.