Concept card

SAP BusinessObjects Web Intelligence (WebI)

As of 2026-09-27

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP BusinessObjects Web Intelligence (WebI)?

The ad hoc reporting tool of the BusinessObjects suite, built on universes. The most-used and least-replaceable BI artefact in most SAP estates, because what users value is the freedom to change the question.

What it is

Web Intelligence — WebI to everyone who uses it — is the ad hoc reporting tool of the BusinessObjects suite. A user opens a universe, drags objects into a query, and gets a document they can then reshape: add a break, insert a calculation, drill down, merge two data providers, save it and schedule it. That last sentence is the whole point, and it is why WebI outlives every prediction of its retirement.

What users actually value is not the report, it is the freedom. A WebI document is not a fixed output; it is a small analysis environment that a business analyst controls without involving IT. Any replacement is judged against that, and dashboard tools generally lose the comparison — not because they are less capable, but because they answer a question that was decided in advance. This is the single most common reason a BusinessObjects retirement stalls after the dashboards have moved.

The universe is inseparable from the tool. WebI queries are expressed against universe objects, and the joins, contexts and restriction sets in that universe are what make the query safe. Move WebI to a new platform and you are not porting reports, you are re-expressing a semantic model — and then re-teaching the people who built their own documents on top of it.

Why it matters

WebI is where BusinessObjects retirements stall. The requirement it satisfies — changing the question without involving IT — is rarely written down, and a dashboard does not satisfy it.

Key points

Ad hoc reporting on universes: query, then reshape — breaks, calculations, drill, merged data providers.
🔴 The requirement is freedom, not the report. A dashboard answers a question decided in advance; that is the whole difference.
Queries are expressed against universe objects — moving WebI means re-expressing a semantic model, not porting files.
SAP's direction is SAC on a Datasphere or live-connection foundation; fixed distributed reporting moves cleanly, ad hoc rarely does in one step.
A reduced, deliberate WebI footprint is a legitimate landing state — an accidental one is not.
The merged-provider pattern (a governed universe query joined to an ungoverned spreadsheet) is invisible to Joule and the SAP Knowledge Graph until the second source is published as a governed Data Product.
Migrating a merged-provider document is a training-and-governance project, not a technical conversion — publish the second source, model the join in Datasphere, and retrain the author.

Terms used on this page

Data provider: A query inside a WebI document. Several can coexist and be merged on shared dimensions.
Break: A WebI grouping construct that splits a block by a dimension and allows sub-totals — one of the reshape features users rely on.
Merged dimension: The WebI mechanism that joins two data providers on a common dimension inside the document.
Restriction set: Universe-level row filtering by user or group — the security WebI inherits without the report author writing it.
Ungoverned second source: A spreadsheet or manually maintained file merged into a WebI document alongside a governed universe query. Invisible to the SAP Knowledge Graph and to Joule grounding until it is published as a governed Data Product.
Document modification log: The CMS audit trail of edits (not just opens) to a WebI document. The population of documents that get edited, not just read, is the true ad hoc requirement a migration must plan for.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →