Skip to main content
Card class: Card
Revenue split across Oracle ERP Cloud business units. Available only when Multi-Ledger is enabled.

​
At a glance

Revenue split across Oracle Business Units. Available when multiple BUs are connected. Bar chart for entity-level revenue concentration view.
What it countsSUM(revenue) GROUP BY business_unit.
CurrencyReporting ledger consolidated.
Time window30D
Rolesowner, finance

​
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 retailer:
BURevenue 30D
US Retail Inc$48M
UK Retail Plc$24M
EU DTC NV$12M
Mexico Distribucion$8M
Five things: (1) US dominance; (2) FX consolidation impact; (3) per-BU vsP trend; (4) margin profile differs by BU; (5) inter-co flows excluded post-Financial Consolidation Hub.

​
Sibling cards merchants should reference together

CardWhy pair
Revenue Booked into GLTotal.
Business Unit PerformanceMulti-dim view.

​
Reconciling against the vendor’s own dashboard

Where to look in Oracle ERP Cloud:
Financial Reporting Center → Income Statement by Business Unit OTBI → GL Real Time group by BU
Cross-connector reconciliation: Internal Oracle metric.

​
Known limitations / merchant FAQs

Inter-co eliminated? Yes if Financial Consolidation Hub view applied. Single-Ledger? Card hides if only one BU.

​
Tracked live in Vortex IQ Nerve Centre

Revenue by Business Unit 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.