Skip to main content
Metrics type: Key Metrics • Category: Executive Overview
Composite of IDoc-queue-clean x AR-aging-low x inventory-variance-low x close-on-time. One number that tells the executive whether the SAP backbone is healthy.

​
At a glance

A single 0-100 composite that blends the most important operational-health signals from your S/4HANA Cloud connector into one executive number. It multiplies together four component scores: IDoc queue cleanliness, AR aging health, inventory variance, and period-close timeliness. A score near 100 means the integration is clean, cash is moving, stock figures agree, and closes land on time. A falling score is the earliest single-glance warning that something in the SAP backbone needs attention, before any individual card has fully alerted.

​
Calculation

Calculated automatically from your SAP data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK enterprise commerce group on SAP S/4HANA Cloud Public Edition, three Company Codes, ecom orders flowing in via IDoc. Live snapshot at 03 May 26. Four things to notice:
  1. The composite is 68, below the 70 alert threshold. The gauge fires. At a glance the executive knows the SAP backbone needs attention without reading four separate cards.
  2. The IDoc component is the culprit at 58. It drags the whole score down. The other three are healthy to strong. The composite correctly points the executive straight at the integration queue, which is where the 69 stuck documents live. Drill into Open (Unposted) Journal Entries and IDoc Error Queue Depth to act.
  3. A single weak component cannot be masked. Inventory at 88 and close at 95 are excellent, but the blend still lands at 68 because the IDoc queue is broken. This is deliberate: the score is built so one failing area cannot hide behind three good ones.
  4. The 7-day trend matters more than the absolute. A score of 68 that was 92 last week signals a sudden break, probably a new IDoc mapping error after a deployment. A 68 that has sat there for a month signals a chronic, tolerated backlog. Read the trendline, not just the number.
T-codes / Fiori apps for drilling in:
  • WE05 / BD87: IDoc monitoring and reprocessing (IDoc component).
  • FBL5N / Manage Customer Line Items: receivables aging (AR component).
  • Inventory reconciliation and stock-overview apps: variance (inventory component).
  • Manage Posting Periods / close cockpit: period-close timeliness (close component).

​
Sibling cards merchants should reference together

The S/4HANA Health Score is a roll-up. Its value is the drill-down, so the most important siblings are the four component cards it blends, plus the executive cards it sits beside.

​
Reconciling against SAP

Where to look in S/4HANA Cloud: There is no single native SAP equivalent to this composite, because SAP does not ship a blended cross-domain health score out of the box. To reproduce it, you reconcile each component against its own native source:
IDoc component: IDoc List WE05 filtered to inbound error status, and the Application Interface Framework monitor AR component: Manage Customer Line Items Fiori app aging buckets, or transaction FBL5N Inventory component: stock-overview and inventory-reconciliation Fiori apps comparing SAP stock to the commerce platform Close component: Manage Posting Periods Fiori app and the financial close cockpit Embedded Analytics: the relevant CDS views per component in your release
Direct link template: https://my{tenant}.s4hana.cloud.sap/sap/bc/ui2/flp then the relevant app per component. To validate the score, check each component card against its native SAP source, confirm each sub-score, and the composite should follow. There is no single SAP screen to compare against; the reconciliation is component by component. Common mistakes when interpreting the composite:
  • Treating it as a single SAP metric. It is a Vortex IQ composite, not an SAP-native KPI. Do not expect a matching number anywhere in the Fiori launchpad.
  • Ignoring the weakest component. The headline can look only mildly low while one component is severely broken. Always open the lowest sub-score.
  • Comparing across tenants. Two tenants with different volumes and close cadences will weight the components differently in practice. The score is most meaningful as a trend against itself, not against another business.
Why our number may differ from your own manual assessment: Cross-connector reconciliation: This card is intentionally SAP-internal. It blends signals that live only in the SAP backbone (IDoc queue, FI-AR aging, inventory variance, posting-period status) and has no commerce-platform counterpart. The commerce platforms feed the IDoc and inventory components upstream, so a commerce-side integration break will show here as a falling IDoc or inventory sub-score.

​
Known limitations / merchant FAQs

What does the score actually measure? The operational health of your SAP backbone as seen from the connector, condensed to one number. It blends whether inbound integration is clean (IDoc queue), whether cash is moving (AR aging), whether stock figures agree across systems (inventory variance), and whether finance is closing on time (period close). It is an executive at-a-glance signal, not a financial result. Why blend four cards instead of just watching them separately? Because executives do not have time to scan four cards every morning, and a problem in any one of them is a problem worth knowing about. The composite gives a single daily glance: green means the backbone is healthy, a drop means open the lowest component. The four component cards remain the place to diagnose and act; this card is the trigger to go look. What is a good score? Above 70 is the healthy floor; the alert fires below it. Above 90 means all four areas are strong. Between 70 and 90 means one area is soft but not broken. Below 70 means at least one component is failing hard enough to warrant action. As with all the cards, the threshold is tunable per workspace. How do I act on a low score? Open the component with the lowest sub-score first; it is dragging the composite. The card surfaces which one. From there, drill into that component’s own card and its native SAP source. A low IDoc sub-score sends you to WE05 and BD87; a low close sub-score sends you to the posting-period apps; and so on. Does one bad component sink the whole score? By design, a severely weak component pulls the composite down even when the others are strong, because a broken integration queue or a missed close is a real problem regardless of how healthy receivables are. The score is built so good areas cannot mask a bad one. That is the point of a health composite. Can I change the weighting or the components? The component set and thresholds are configurable per workspace in the Alert Rules tab. Businesses that care most about close timeliness can weight that component more; commerce-heavy shops that live and die by IDoc integration can weight that one. The default blend balances all four. Why is the time window RT/7D? Because the headline is best read live (so you catch a sudden break the moment it happens) but the meaning comes from the 7-day trend. A score that just dropped from 92 to 68 is a fresh incident; a score that has sat at 68 for weeks is a tolerated chronic state. The card shows both the live value and the trendline so you can tell them apart.

​
Tracked live in Vortex IQ Nerve Centre

SAP S/4HANA Health Score is one of hundreds of KPI pulses Vortex IQ tracks across SAP and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.