Analytics Legends logoAI & Analytics Legends Sign inSign up
Guide

SAP BI Consulting: Four Products, One Decision About Layers

As of 2026-11-17

SAP BI consulting is the design, build and migration of reporting and analytics on SAP data. In 2026 it covers four products that sit at different layers: SAP BW/4HANA and Datasphere model and govern the data, SAP Analytics Cloud consumes it for stories and planning, and SAP BusinessObjects remains the reporting server many estates still run. A good engagement starts by deciding which layer owns each piece of logic, not by picking a tool.

What SAP BI consulting covers today

The phrase used to mean BW plus BusinessObjects. It now names a stack. BW/4HANA is a separate product from classic BW, HANA-only, with its own object model. Datasphere is the modelling and governance layer inside SAP Business Data Cloud. SAP Analytics Cloud is the consumption and planning layer. BusinessObjects is a server estate with a rights model, scheduling, publications and the universe semantic layer.

A consultant who knows one of these well and the others by name is a specialist, not a BI consultant. The distinction matters when the brief is a migration, because the work sits in the hand-over between layers.

Which layer owns which logic

Datasphere models and governs; SAP Analytics Cloud consumes. A measure needed by a second story, a planning model, Joule or a third-party tool belongs in a Datasphere analytic model, defined once. Logic that serves one story only — a calculated measure, formatting, a chart restriction — stays in SAC.

Heavy logic such as aggregation, variance and ranking runs in Datasphere, with input parameters passed from SAC. A one-off report over one or two tables can go live from SAC to S/4HANA without Datasphere at all. The choice between a live and an import connection is made per model: live keeps one copy of the truth, import creates a copy with a staleness window that someone has to write down.

The BW decision

BW/4HANA is a successor to BW, not an alternative to Datasphere or Business Data Cloud. They sit at different layers, and choosing one does not settle the other. SAP put the BW/4HANA installed base at roughly 2,500 customers against 20,000 to 30,000 BW 7.5 customers (Sapphire 2025), so most BW estates have not yet made the move.

Conversion paths exist — in-place, remote and shell — and they trade calendar time against an architecture reset. The effort concentrates in the per-object decision: map, redesign or retire every object that has no successor in the reduced model. An estimate that names a path but no object inventory is a preference, not an estimate.

The BusinessObjects decision

The report count is the wrong scoping number for a BusinessObjects estate. The useful numbers are objects by type, monthly scheduled instances, distinct universes, and reports actually opened in the last quarter. Universes encode joins, contexts, aggregate awareness and row-level security; they are re-expressed in the target, never converted.

The decision that organises the programme is rebuild or retire, taken per report on last-quarter usage. Maintenance horizons have been extended more than once, so read the current Product Availability Matrix rather than a slide.

What to ask a firm before you hire it

Ask for the layer decision before the tool decision: where will each shared measure live, and why. Ask for the object inventory behind any BW estimate. For BusinessObjects, ask which usage data they will read before proposing a rebuild list. For SAC, ask how they will handle failing drill-downs in a live model — the usual cause is a missing primary key, relationship or hierarchy in the Datasphere model, not SAC itself.

A firm that answers these in the first meeting has done the work before. The directory lists firms that declare each product, with country and delivery mode, so you can shortlist by layer rather than by label.

What we cannot assert

SAP publishes no current count of BusinessObjects customers, and no day-rate band for BI work is stated here: rates depend on country, seniority and product, and are read on the day-rates pages from posted missions, not estimated.

Frequently asked

Is SAP BI consulting the same as SAP analytics consulting?

In practice the terms overlap. SAP BI consulting usually means reporting and data warehousing on BW, BusinessObjects and SAC; SAP analytics consulting adds Datasphere, Business Data Cloud and planning. Scope the engagement by layer, not by the label.

Do I need Datasphere to use SAP Analytics Cloud?

No. A one-off report over one or two tables can run from SAC straight to S/4HANA. Datasphere earns its place when a measure is reused by a second story, a planning model, Joule or another tool.

Can BusinessObjects universes be converted to SAP Analytics Cloud?

Not converted: re-expressed. Joins, contexts, aggregate awareness and row-level security have to be rebuilt in the target model, which is why the rebuild-or-retire decision per report comes first.

How long does a BW to BW/4HANA conversion take?

It depends on the object inventory and the path chosen (in-place, remote or shell). Any duration quoted without that inventory is a guess.

Engage the editor

This guide is written by . 27 years of SAP — Datasphere, Business Data Cloud, SAC Planning, Joule. Freelance or permanent · Hybrid / remote · Anywhere in EMEA.

Profile and contact

What this page is built on

External sources

Read next

Alert me to new SAP Analytics missions

No account needed. We first ask you to confirm by e-mail; nothing is sent without that confirmation, and every alert has a one-click unsubscribe link. Privacy

Open missions

SAP analytics jobs and contracts · freelance SAP contracts.