Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 5

KPIs in embedded analytics

9 min

SAP S/4HANA reports directly on its own transactional data. This is called embedded analytics: analytical apps, overview pages and KPI tiles that read live data through CDS (core data services) views, with no separate data warehouse in between. For a process owner, that means many standard KPIs are already available in the Fiori launchpad, if your roles include them.

Kinds of analytical content

Overview pagesA role-based page of cards, each showing a KPI or list; click a card to drill into the detail app
Analytical list pages and KPI appsA KPI or chart with filters, drill-down and a list of the documents behind it
Multidimensional reports and query browserFlexible slicing of CDS-based queries for analysts
CDS viewsThe data models underneath, reading live transactional tables
Layers of SAP S/4HANA embedded analytics, from what users see to the data model underneath.
The Sign-Off Table · thesignofftable.com/academy/sap-pow-302

Standard apps for common KPIs

SAP delivers analytical apps for many of the KPIs in lesson 1. Exact names and availability vary by release and edition, and some apps need activation, so always confirm in the SAP Fiori apps reference library for your release. Examples that process owners commonly use:

KPI areaExample standard appsNotes
Receivables, DSOAccounts Receivable Overview (overview page), Days Sales Outstanding, Overdue Receivables, Total ReceivablesDSO app shows the trend and drills into detail; check your release in the apps library
PayablesAccounts Payable Overview and related payables analytical appsCards for overdue payables, blocked invoices and cash discount
Sales fulfillmentSales order fulfillment issue analysis apps in the sales areaLists orders with delivery, credit or billing issues
Journal entriesManage Journal Entries, Display Line Items in General LedgerFilter by document type and user to count manual entries

Examples of standard analytical content. Confirm names and availability for your release.

ApproachStrengthsWatch out for
Standard analytical appDelivered, upgrade-safe, drill-down to documentsDefinition may differ from your legacy KPI
Custom analytical query on standard CDS viewsYour definition, still on live dataYou own and must regression-test it
Process mining (SAP Signavio)End-to-end flow, variants, cross-systemSeparate product and data extraction
Spreadsheet extractQuick and flexibleManual, error-prone, not repeatable; avoid for owned KPIs
Ways to get a KPI, cleanest first.
The Sign-Off Table · thesignofftable.com/academy/sap-pow-302

Overview pages are the natural home screen for a process owner. Each card shows a KPI or a short list, and clicking it opens the analytical app with the same filters applied, so you can go from "DSO is up" to the customers driving it in a few clicks. Analytical apps usually end in a list of documents; from there you can open the individual invoice or order. That drill path, from KPI to document, is what makes embedded analytics useful for root cause work and not just for reporting.

Check the definition before you trust the number

A standard app calculates a KPI one way; your legacy report may have calculated it another. DSO can be calculated in several ways (for example by a simple ratio or a "countback" method), and receivables may or may not include items not yet due. Before go-live, open the app documentation in the Fiori apps reference library, read the calculation, and compare a month of results with your legacy figure. If they differ, decide which definition becomes the official one and document why.

Access and roles

Analytical apps follow the same role concept as transactional apps. A process owner who cannot see the DSO app usually lacks the business role or catalog that contains it, not the app itself. Ask for the role during the project and test it in UAT, so the KPI is available on day one.

What would you do?

After go-live, Contoso's DSO in the standard app is 6 days higher than the ECC report showed for the same month. Grace asks whether the S/4HANA migration made collections worse. What should Dan do first?

Key points
  • Embedded analytics reads live S/4HANA data through CDS views; no separate warehouse.
  • Overview pages and analytical apps cover many standard KPIs; confirm availability in the Fiori apps reference library.
  • Check the calculation definition and reconcile to documents before trusting a KPI.
  • Test KPI apps and the roles that grant them in UAT.

Check your understanding · not graded

Lesson check

  1. 1. What does embedded analytics in SAP S/4HANA read?

  2. 2. Where should you confirm an analytical app's availability and calculation for your release?

  3. 3. A KPI app shows a different value from the legacy report. What is the first step?

  4. 4. A process owner cannot see the DSO app. What is the most likely cause?