SAP BusinessObjects Web Intelligence (WebI)
As of 2026-08-14T00:00:00Z
What is SAP BusinessObjects Web Intelligence (WebI)?
Web Intelligence — WebI to everyone who uses it — is the ad hoc reporting tool of the BusinessObjects suite.
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.
Where it lands. SAP's direction is SAP Analytics Cloud, with the data foundation supplied by Datasphere or a live connection. For genuinely fixed, distributed reporting the transition is straightforward. For ad hoc analysis, the honest answer is that the replacement is a combination — SAC exploration for the analytical questions, a modelled Datasphere layer for the governed objects, and, in many estates, a reduced WebI footprint kept deliberately for the population that needs to change the question daily.
For a consultant, WebI is where a migration meets its most stubborn users, and it is worth naming the ad hoc requirement explicitly in the plan rather than discovering it during acceptance.
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.
Common pitfalls
- Treating WebI documents as reports — Signal: A one-to-one mapping table from WebI to SAC stories Fix: Separate read-only documents from reshaped ones. Only the first group maps one-to-one.
- Promising universe portability — Signal: "The universe comes across" Fix: It is re-expressed as a Datasphere model or a live connection. Different paradigm, real effort.
- Leaving WebI by accident — Signal: A residual footprint nobody decided to keep Fix: If ad hoc is a real requirement, keep it deliberately and scope its support. An accidental remnant has no owner.
Decision framework
| Decision | Option A | Choose A when | Option B | Choose B when |
|---|---|---|---|---|
| What replaces a given WebI document | A SAC story | The document is opened and read, not reshaped — the question is stable | SAC exploration or a retained WebI | The document is reshaped by its users — that is an analysis environment, not a report |
| How to segment the estate | By folder and owner | Convenient, and usually uninformative | By reshape behaviour | The default: documents that get modified are a different migration problem from documents that get read |