How to connect Power BI to Oracle Fusion Cloud ERP
Short answer
Fusion is SaaS with no direct database access, so route data through BICC extracts into a warehouse, BI Publisher reports, or Oracle's own analytics layer, then point Power BI at that. Direct REST from Power BI works for small datasets only.
The first surprise for teams coming from on-prem Oracle or SQL-based ERPs is that you cannot just open a database connection to Fusion. Oracle controls the schema and the access path, and the supported ones are extracts, reports and APIs.
That shapes the whole design. Power BI wants a stable, modelled dataset. Fusion offers transactional resources and operational reports. The bridge is a layer you own or license: a warehouse fed by BICC, or Oracle's own Fusion Data Intelligence if you already pay for it.
Before building, check whether OTBI and Oracle Analytics dashboards already answer the question. Power BI earns its place when you need to blend Fusion with shop-floor, CRM or non-Oracle data, or when your organization standardizes on it.
What teams use it for
On-time delivery by supplier
Combine purchase order schedules and receipts into promised versus received lateness, sliced by supplier, buyer and commodity.
Inventory aging and turns
On-hand balances and transactions by organization and subinventory, with aging buckets and excess highlighted for planners.
Work order performance
Cost, yield and schedule adherence from manufacturing work orders, combined with MES machine data from another source.
Spend and savings
Purchase order and invoice spend by category and supplier, price variance against contract and maverick spend.
Order backlog and promise accuracy
Sales order lines, scheduled ship dates and actual shipments to show backlog by customer and promise reliability.
Oracle Fusion Cloud ERP integration surface
- BI Cloud Connector (BICC) extracts of view objects to OCI Object Storage or UCM on a schedule, with incremental support for many objects. The usual path into a warehouse.
- BI Publisher reports returning CSV or XML, callable through the report service, suited to curated, moderate-size datasets.
- Fusion REST resources, reachable from the Power BI Web connector with OAuth, but paging and throttling make them poor for large facts.
- OTBI subject areas for ad hoc analysis within Fusion, and Fusion Data Intelligence or Oracle Analytics for Oracle-managed pipelines. Licensing and availability vary.
- An on-premises data gateway only matters if your warehouse sits inside your network. Fusion itself is reached from the cloud.
How it works
- 1
Decide the data path
Pick a warehouse fed by BICC for scale, BI Publisher for small curated sets, or Oracle's analytics layer if licensed. Avoid building facts on live REST.
- 2
Configure BICC extracts
Select the view objects for purchasing, inventory, work orders and orders, schedule incremental runs, and land files in Object Storage.
- 3
Load and model
Load into Azure Synapse, Fabric, Snowflake, Autonomous Database or SQL Server. Build conformed dimensions for item, organization, supplier and calendar.
- 4
Connect Power BI
Use import mode for most reports, or DirectQuery for fresh operational views. Install a data gateway if the warehouse is on-prem.
- 5
Apply row-level security
Map Entra ID users to business units or plants in Power BI roles, matching Fusion data security as closely as practical.
- 6
Add natural-language Q&A
Use Power BI's Q&A and Copilot features where licensed, and consider a governed text-to-query layer over the warehouse for plant-specific vocabulary.
Example flows
Nightly supplier lateness model
Trigger: Scheduled BICC incremental extract completes
- Files land in Object Storage
- Pipeline loads purchase order and receipt facts
- Power BI dataset refreshes after the load finishes
Result: Buyers open a dashboard each morning with yesterday's lateness by supplier.
Plant manager question in plain language
Trigger: A manager asks which work orders ran over standard cost this week
- The question goes to a governed semantic layer over the warehouse
- The system generates a query and shows it
- Results return with a link to the report page
Result: An answer without waiting for a report change request.
Keeping data on-prem
If your reporting platform must live in your own network, land BICC files from Object Storage into a warehouse you host, such as SQL Server or PostgreSQL, and connect Power BI Report Server or the service through an on-premises data gateway. Fusion remains cloud-hosted, so only extracts cross the boundary and only on your schedule. For natural-language questions with no data leaving the site, run an open-weight model locally that writes read-only queries against the warehouse, never against Fusion.
Security checklist
- Treat the warehouse as holding production financial and supplier data, with the same access controls as Fusion.
- Mirror Fusion data security with row-level security in Power BI, and test it with real user accounts.
- Exclude banking, personal and unneeded sensitive columns from extracts rather than hiding them later.
- Store extract credentials and storage keys in a vault, with rotation.
- Limit Power BI workspace sharing and publish-to-web, which can expose reports by accident.
Ways to get it done
Oracle-native analytics (OTBI, Oracle Analytics, Fusion Data Intelligence)
Effort: Configuration, with less cross-system flexibility.
Fusion-only reporting where licensing already covers it.
BICC to your warehouse to Power BI
Effort: Weeks to a first model, ongoing pipeline maintenance.
Blending Fusion with other plant and commercial data.
Netray-supported pipeline plus Q&A layer
Effort: Pilot on one subject area, then add more.
You want governed natural-language questions over the warehouse, optionally on-prem.
Pitfalls
- !Pulling large facts through REST from Power BI times out or gets throttled. Use extracts.
- !Incremental BICC extracts need care with deletes and late changes, or your numbers drift from Fusion.
- !Item, organization and calendar differences across business units cause duplicate dimensions. Conform early.
- !Report logic copied from OTBI can differ subtly from your warehouse calculation. Reconcile totals.
- !Quarterly Fusion releases can add or change view object columns. Monitor extract failures.
Frequently asked questions
Can Power BI connect directly to the Fusion database?
No. Fusion Cloud ERP does not offer direct database access to customers. Use BICC extracts into a warehouse, BI Publisher reports, REST for small sets, or an Oracle analytics layer, then connect Power BI to that.
Do I need a data gateway?
Only if your Power BI data source is inside your network, such as an on-prem SQL Server warehouse. Cloud sources reached from the Power BI service do not need one. Fusion extracts themselves flow through BICC rather than a gateway.
Is Power BI better than OTBI?
Not automatically. OTBI is fine for operational reports inside Fusion. Power BI is better for blending sources, richer visuals and organization-wide standards. Choose by the question and where the audience already works.
How fresh can the data be?
Scheduled BICC incremental runs commonly deliver hourly to daily freshness, depending on volume and object. For near-live single records, call REST. Do not promise real time for large analytical datasets.
Can I ask questions in plain English?
Yes, through Power BI Q&A or Copilot where licensed, or a governed text-to-query layer over your warehouse. Quality depends on a clean semantic model and agreed business definitions, so budget time for that.
More for Oracle Fusion Cloud ERP
Want Power BI working on your Oracle Fusion Cloud ERP?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment