Oracle Fusion Cloud ERP and Microsoft Power BI integration

What moves between them

Oracle Fusion Cloud ERP data flows into Microsoft Power BI on a polling schedule you define, typically every 5 to 15 minutes. GL accounts, journal lines, and invoice headers are pulled from Oracle Fusion filtered by LastUpdateDate, transformed into Power BI table rows matching the schema of your push dataset, and posted via REST API. Supplier and customer reference data is synced to keep dimension lookups current. Power BI refreshes datasets on demand or on a schedule to reflect the latest rows. No data flows back from Power BI to Oracle Fusion; Power BI is read-only from Oracle Fusion perspective.

How ml-connector handles it

ml-connector stores your Oracle Fusion OAuth client credentials and Power BI service principal credentials encrypted. On each poll cycle it refreshes the Oracle Fusion bearer token (valid ~1 hour), queries the REST API with LastUpdateDate and CreationDate filters to retrieve new or changed records since the last run, and maps Oracle Fusion GL account codes, invoice totals, and line details to the column names defined in your Power BI push dataset. It then POSTs the transformed rows to Power BI and refreshes the dataset if you choose. Service principal tokens for Power BI are also refreshed on each cycle. Because Oracle Fusion cloud has no webhooks, ml-connector polls on a fixed schedule you define per dataset and tracks the last timestamp to avoid duplicate rows. If a token expires or a network call fails, ml-connector retries with exponential backoff. Every row in Power BI carries the original Oracle Fusion record ID and timestamp, so dashboards can trace a number back to its source transaction, and if a replay is needed, ml-connector can re-push historical data.

A real-world example

A mid-sized wholesale distributor runs Oracle Fusion Cloud ERP for order-to-cash, procure-to-pay, and general ledger, with a finance team spread across two locations. Before the integration, the finance manager exported GL reports and invoice summaries from Oracle Fusion once or twice per day, pasted them into a Power BI workbook, and emailed updated dashboards to the team. By afternoon the data was stale, and month-end close required hours of manual reconciliation because the Cash Application and AP Aging dashboards had to be refreshed by hand. With Oracle Fusion and Power BI connected, journal entries, invoices, and supplier payments sync every 10 minutes, dashboards update in real time, and the finance team can trust a single source of truth on screen. The sales and operations teams also use the integrated dashboard to track order status and inventory turnover without asking Finance for exports.

What you can do

• •Sync Oracle Fusion GL accounts, journal entries, and invoices to Power BI push datasets on a schedule you control.
• •Transform Oracle Fusion source records and automatically refresh Power BI datasets after each poll.
• •Authenticate with Oracle Fusion OAuth 2.0 Client Credentials and Power BI service principal tokens, refreshing both on each cycle.
• •Keep order and supplier reference data in sync between Oracle Fusion and Power BI for consistent reporting dimensions.
• •Retain full lineage from each Power BI row back to the Oracle Fusion source record for audit and replay capability.

Questions

How often do Power BI dashboards update with new Oracle Fusion data?

ml-connector polls Oracle Fusion on a schedule you define, typically every 5 to 15 minutes, and pushes the new records into your Power BI push dataset immediately. Dashboard refresh speed depends on your Power BI dataset refresh setting. Most customers see new data on screen within 10 to 20 minutes of a transaction posting in Oracle Fusion.

Can Power BI push data back into Oracle Fusion?

No. Microsoft Power BI is a reporting and analytics destination, not a transactional system. Data flows only from Oracle Fusion into Power BI. If you need to update Oracle Fusion records based on Power BI analysis, that workflow requires a separate integration in the reverse direction or manual entry in Oracle Fusion.

What happens if the Oracle Fusion or Power BI API calls fail?

ml-connector retries failed calls with exponential backoff and tracks the last successful poll timestamp. If a call fails permanently, ml-connector logs the error with full record context so you can investigate and replay the data once the API is healthy. Every row carries the source Oracle Fusion record ID for traceability.