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.
| What it counts | A weighted composite of four component cards, each normalised to a 0-100 sub-score, then blended into one figure. The components are IDoc-queue-clean (from the IDoc error queue depth), AR-aging-low (from the AR aging gauges), inventory-variance-low (from inventory sync drift), and close-on-time (from period-close status). |
| How it is calculated | Each component is scored 0-100 where 100 is perfectly healthy, then combined into a single 0-100 result. A weak component drags the composite down, so a single failing area is visible even when the other three are strong. The card is designed so no one component can hide a problem in another. |
| Numerator vs denominator | Not a single numerator-over-denominator ratio. It is a blend of four sub-scores. Read the headline for the at-a-glance health, then drill into whichever component is lowest to find the actual problem. |
| Component cards | IDoc Error Queue Depth, AR Aging 60+ Days, Inventory Sync Drift, and Period Close Status. Each is a standalone card in its own right; this card aggregates them for an executive view. |
| Currency | Score metric, currency-agnostic. The components draw on value-based and count-based inputs, but the output is a dimensionless 0-100 number. |
| Company Code scope | Respects the dashboard Company Code filter. By default blends the components across every Company Code visible to the connected SAP business user / API role. The close-on-time component is inherently multi-entity. |
| Time window | RT/7D (live composite with a 7-day trend) |
| Alert trigger | <70 |
| Roles | owner, finance, operations |
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.| Component | Underlying reading | Sub-score (0-100) |
|---|---|---|
| IDoc queue clean | 69 documents in the error queue (above the 50 alert) | 58 |
| AR aging low | 60+ share at 16.0% (just above the 15% alert) | 74 |
| Inventory variance low | sync drift within tolerance on most SKUs | 88 |
| Close on time | last close landed on the deadline, no entity late | 95 |
| SAP S/4HANA Health Score (this card) | 68 |
- 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.
- 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.
- 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.
- 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.
- 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.| Card | Why pair it with SAP S/4HANA Health Score |
|---|---|
| IDoc Error Queue Depth (last 24h) | The IDoc-queue-clean component. Usually the first to drag the score down in a commerce shop. |
| Open (Unposted) Journal Entries | The journal-side view of the same IDoc-failure problem. |
| AR Aging 60+ Days | The AR-aging-low component. |
| Inventory Sync Drift | The inventory-variance-low component. |
| Period Close Status (by CompanyCode) | The close-on-time component. |
| Period Close On-Time Rate (12mo) | The longer-run view of the close component. |
| Top Findings Across Company Codes | The multi-entity executive companion to this single-number score. |
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 ListDirect link template:WE05filtered to inbound error status, and the Application Interface Framework monitor AR component: Manage Customer Line Items Fiori app aging buckets, or transactionFBL5NInventory 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
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.
| Reason | Direction | Why |
|---|---|---|
| Component weighting | Either | The blend weights the four components in a fixed way. A manual assessment that weights, say, close-on-time more heavily will land on a different number. |
| Component thresholds | Either | Each sub-score is normalised against its own alert threshold. If you tuned a component card’s threshold, its sub-score and the composite shift accordingly. |
| Snapshot timing | Either | The score is live. Reprocessing IDocs or closing a period mid-snapshot changes a component and the composite. Match the timestamp. |
| Company Code scope | Either | The card respects the dashboard filter. A manual assessment over all entities will differ from a filtered view. |
| Missing component data | Either | If a component’s source is unavailable (for example, inventory not connected), the blend adapts, which changes the composite versus a full four-component view. |