SAP® Analytics · Embedded analytics

Real-time KPIs, right where people work.

S/4HANA embedded analytics reads live transactional data through CDS views — no copies, no overnight loads. We build the KPIs, apps and dashboards on top, in Fiori, SAC, Power BI or Tableau.

0
data copies — reads live S/4HANA data
CDS
views as the one data model
4 app types
KPI tiles, overview pages, list pages, reports
Any front end
Fiori, SAC, Power BI or Tableau
01 — How it works

Three layers. Zero data copies.

Embedded analytics runs inside S/4HANA itself. The data model reads live tables on SAP® HANA, so a booking made a second ago is in the report now.

03
Front ends
Where people see the numbers — inside their daily apps.
Fiori KPI tilesOverview pagesSAC livePower BITableau
02
Virtual data model
CDS views and analytical queries that turn tables into business terms — with authorisations built in.
CDS viewsAnalytical queriesDCL access control
01
Live data
Transactional data in S/4HANA on SAP® HANA — no extraction, no overnight load.
S/4HANASAP® HANA
02 — What we build

From a single KPI tile to a full dashboard.

Custom CDS views

Analytical CDS views and queries on top of the SAP® standard model — clean core, upgrade-safe.

Smart Business KPIs

KPI tiles with targets and thresholds on the Fiori launchpad, with drill-down to the document.

Overview & list pages

Overview pages and analytical list pages that combine KPIs, charts and filters for one role.

SAC stories, live

SAP® Analytics Cloud on a live connection — dashboards without replicating data.

Power BI & Tableau

Connect your existing BI tools to S/4HANA models, with SAP® definitions and authorisations kept.

Authorisations

Access control (DCL) on every view, so users only see what their SAP® roles allow.

03 — Embedded or data warehouse?

Use both — for different questions.

Embedded analytics is unbeatable for operational, real-time questions inside S/4HANA. It does not replace a data warehouse for history, many sources or group-wide KPIs.

Embedded analytics

Operational
  • Real-time data, exactly as booked
  • Inside Fiori, next to the transaction
  • Light modelling, fast to build
  • S/4HANA data only

BW/4HANA · Datasphere

Strategic
  • History and snapshots over years
  • SAP® and non-SAP® sources combined
  • Group-wide KPIs and governance
  • Planning and consolidation on top
DATA FOUNDATIONNeed history, many sources or group KPIs? See our data warehouse services. Data foundation →
04 — How we work

From KPI list to live app.

  1. 1

    KPI workshop

    Which decisions need which numbers — per role, with definitions everyone agrees on.

  2. 2

    Model

    Standard CDS views first, custom views only where needed — documented and upgrade-safe.

  3. 3

    Build apps

    KPI tiles, overview pages or SAC stories, shown to users every two weeks.

  4. 4

    Enable

    Key users learn to build their own reports on the same model.

FROM QUATELIO · EISQuestions your dashboards don't answer yet? Ask them in plain English. Explore EIS →
FAQ

Good questions to start with

Do we need BW if we have embedded analytics?

For operational reporting on S/4HANA data, often not. For history, many sources or group-wide KPIs, a data warehouse — BW/4HANA or Datasphere — is still the better place. Most customers use both.

Does embedded analytics slow down S/4HANA?

Well-built CDS views run directly on SAP® HANA and are designed for this. We check heavy queries and design views so that operational work is not affected.

Can we use Power BI instead of Fiori or SAC?

Yes. Power BI and Tableau can read S/4HANA analytical models. We keep the definitions and authorisations in SAP®, so every tool shows the same number.

Is it upgrade-safe?

Yes, when built on released SAP® CDS views and the clean core approach. We avoid modifying SAP® standard objects.

Let's put your KPIs where people work.

Book a KPI workshop — you leave with a KPI list, a data model plan and a first app design.

Book a KPI workshopAll analytics services