Skip to main content
Metrics type: Key Metrics • Category: Ecommerce Platform
A composite 0-100 score combining several Fusion-integrity signals into one gauge. The single roll-up of whether your Oracle Fusion stack is healthy and your numbers are trustworthy.

​
At a glance

Oracle Fusion Health Score is a composite 0-100 gauge that blends several Fusion-integrity signals into one number: whether subledger-to-GL posting is running clean, whether intercompany is in balance, whether the integration flows that feed Fusion are healthy, and whether AR aging is under control. It is the single roll-up a finance leader can glance at to answer one question: can I trust the numbers coming out of my Oracle Fusion stack right now? A low score means one or more integrity signals are degraded, and the contributing cards tell you which. Sourced from a blend of Oracle ERP Cloud signals across all in-scope ledgers.

​
Calculation

Calculated automatically from your Oracle ERP Cloud 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 US Fortune 500 omnichannel speciality retailer running Oracle ERP Cloud across three Business Units under two primary ledgers. The reading is taken live on 22 Jun 26, with the 7-day trend running back to 15 Jun 26. The composite blends several integrity signals; the table below shows the contributing signals in plain terms, not exact weightings. Five things to notice:
  1. 66 is below the alert threshold of 70, so the Nerve Centre fires. Three of the four signals are dragging at once, which is what pulls the composite under the line. A single weak signal would usually leave the score in the 70s.
  2. The composite is a roll-up, not the source of truth itself. The score tells you something is wrong; the contributing cards tell you what. Here the drags trace to Subledger to GL Posting: Failed (any source), OIC Integration Flow Failures (24h), and AR Aging 60+ Days.
  3. The inputs are described generally on purpose. The exact blend and weighting of signals is part of the scoring model and is not exposed as fixed numbers, because the right emphasis varies by estate. What matters operationally is the direction and which signals are dragging.
  4. The 7-day trend gives the score context. On 15 Jun 26 the score was 81. The slide to 66 over the week shows the degradation is recent and accelerating, not a long-standing baseline. That trend is why this card carries a RT/7D window rather than a pure snapshot.
  5. Fixing one signal lifts the score. Clearing the failed Receivables posting and resolving the OIC flow failure would likely return the composite to the mid-70s even before the AR aging band recovers, because each resolved signal removes its drag.

​
Sibling cards merchants should reference together

Oracle Fusion Health Score is the roll-up. Pair it with the contributing cards to find which signal is dragging.

​
Reconciling against Oracle ERP Cloud

Where to look in Oracle ERP Cloud: There is no single native Oracle screen that produces a composite health score; the score is a Vortex IQ roll-up of signals that Oracle exposes individually. To reconcile it, inspect each contributing signal in its own Oracle home:
Navigator → General Accounting → Journals → Manage Journals (unposted and in-error journals, subledger-to-GL posting state) Navigator → General Accounting → Intercompany → Manage Intercompany Transactions / Balances Navigator → General Accounting → Period Close → Close Monitor and Receivables → Reports → Aging (close and AR-aging signals)
Each Oracle screen confirms one input. Add them up qualitatively and you can see why the composite sits where it does. For integration-flow health, the Oracle Integration Cloud (OIC) monitoring console shows recent flow runs and failures. Most Fortune 500 teams keep these screens open during close and use the Vortex IQ score as the single pane that tells them which one to look at first. Common mistakes when comparing against Oracle’s own reports:
  • Looking for a matching score in Oracle. Oracle does not publish a single health score, so there is no native number to match. Reconcile signal by signal, not score to score.
  • Assuming each signal is weighted equally. The composite emphasises signals differently. A clean intercompany position does not fully offset a stack of failed postings, so do not expect a simple average of the inputs.
  • Comparing a real-time score against a period-end Oracle snapshot. The score is live with a 7-day trend; a frozen close report reflects a single past moment.
Why our number may legitimately differ from Oracle’s reports:

​
Known limitations / merchant FAQs

What exactly goes into the score? A blend of Fusion-integrity signals: whether subledger-to-GL posting is running clean, whether intercompany is in balance, whether the integration flows feeding Fusion are healthy, and whether AR aging is under control, among related signals. Each input has its own dedicated card. We describe the inputs in plain terms rather than publishing exact weightings, because the right emphasis differs by estate and the scoring model is tuned to surface the signals that matter most. Why is there no single Oracle screen that matches this? Because Oracle exposes these signals individually, not as one composite. The score is a Vortex IQ roll-up that saves a finance leader from checking a dozen screens to answer “are my numbers trustworthy right now?”. To reconcile it, inspect each contributing signal in its own Oracle home and the score’s direction will make sense. The score dropped but each individual area looks only slightly off. Why? Because several signals dragging at once compound. The worked example shows three modest issues combining to pull the composite below 70. The score is designed to catch exactly this: a stack of small problems that no single card would flag as alarming but that together mean the books need attention. What does a low score actually tell me to do? It tells you to look at the contributing cards. The score is the smoke alarm; the sibling cards are where the fire is. Resolve the dragging signals (a failed posting, an integration flow failure, an aging breach) and the score recovers as each drag is removed. Why is the window RT/7D rather than just real-time? Because a score in isolation lacks context. Knowing the score is 66 today matters far more when you also know it was 81 a week ago. The 7-day trend distinguishes a sudden, recent degradation from a long-standing baseline, which changes how urgently you respond. Does a perfect score mean nothing can be wrong? No. The score reflects the integrity signals it blends, which are the most common sources of untrustworthy numbers, but it cannot catch every possible issue. Treat a high score as strong reassurance, not an absolute guarantee, and keep the specific operational cards in view for anything outside the composite’s inputs. How fresh is the score? The composite is computed live from signals Vortex IQ reads through the Oracle Fusion REST API and the integration monitoring layer, with a short cache, so it reflects the stack as of the last sync window. The 7-day trend is rebuilt continuously so the direction stays current.

​
Tracked live in Vortex IQ Nerve Centre

Oracle Fusion Health Score is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud 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.