Oracle E-Business Suite and Microsoft Power BI integration

What moves between them

Data flows from Oracle E-Business Suite into Microsoft Power BI. ml-connector polls Oracle E-Business Suite tables on a schedule (daily, weekly, or as you define), extracts GL journals, AP invoices, PO headers and lines, and customer accounts. It transforms the data to match your Power BI push dataset schema, batches the rows, and POSTs them via the Power BI REST API. Once the data is loaded, ml-connector can trigger a dataset refresh to update your reports and dashboards. The flow is unidirectional; Power BI does not write back to Oracle E-Business Suite.

How ml-connector handles it

ml-connector stores your Oracle E-Business Suite ISG hostname and port, then builds the full REST URL per the ISG pattern. It authenticates using HTTP Basic Auth with your EBS username and password, adds the required application context headers (ctx_orgid, ctx_responsibility, and others), and polls the open interface views and GL tables on your schedule. For each poll cycle, it filters results by LAST_UPDATE_DATE with limit/offset pagination to avoid fetching unchanged records. Once the data is extracted, ml-connector maps your Oracle E-Business Suite GL code combinations, AP invoice fields, and PO dimensions to your Power BI push dataset schema. It then authenticates to Power BI with OAuth 2.0 Client Credentials using your service principal client ID and secret, and POSTs the transformed rows in batches. Session tokens from both systems expire after 30-60 minutes, so ml-connector refreshes them on 401 responses. Every poll and push carries a full audit trail, so failed records can be replayed. If a row push to Power BI fails, ml-connector backs off and retries. After all rows are loaded, it can optionally trigger a Power BI dataset refresh so your dashboards reflect the latest data immediately.

A real-world example

A mid-sized manufacturing company runs Oracle E-Business Suite for GL, AP, and procurement across multiple operating units. The finance team wants to track AP spend by vendor, department, and GL account in real-time dashboards, and they need to monitor PO aging and invoice aging by supplier. Before the integration, the controller exported GL trial balances and AP aging from Oracle E-Business Suite each week, re-keyed the data into an Excel pivot table, and published static images to SharePoint. With Oracle E-Business Suite and Power BI connected, every journal entry and invoice appears in a live dashboard within an hour of posting, finance managers can drill into GL detail by unit and cost center, and month-end close reconciliations happen in minutes instead of days.

What you can do

• •Load GL journals, GL trial balances, and GL distributions from Oracle E-Business Suite into Power BI for financial analysis and variance reporting.
• •Sync AP invoice headers, line items, and payment status to Power BI for spend analysis, aging reports, and cash flow visibility.
• •Bring PO headers and line items into Power BI to track procurement spend, aging, and supplier performance.
• •Authenticate Oracle E-Business Suite with HTTP Basic Auth plus ISG application context headers, and Power BI with OAuth 2.0 service principals.
• •Poll Oracle E-Business Suite on a schedule you define, transform data to your Power BI schema, and trigger dataset refresh to keep dashboards current.

Questions

How does ml-connector handle Oracle E-Business Suite's lack of a fixed URL and no webhooks?

ml-connector accepts the full ISG hostname and port per customer, since each Oracle E-Business Suite instance is self-hosted. Because Oracle E-Business Suite has no webhooks, ml-connector polls the GL and AP interface tables on a schedule you define, filtering by LAST_UPDATE_DATE to fetch only new and changed records. This avoids re-processing unchanged data and keeps API calls minimal.

What happens when authentication tokens expire?

Session tokens from both Oracle E-Business Suite and Power BI expire after 30-60 minutes. ml-connector detects a 401 response from either system, re-authenticates immediately (HTTP Basic Auth for Oracle E-Business Suite, OAuth 2.0 for Power BI), and retries the failed request with a fresh token. The retry is transparent to the flow.

Can I write data back from Power BI to Oracle E-Business Suite?

No. Power BI is a reporting and analytics destination. ml-connector moves data one direction: from Oracle E-Business Suite into Power BI for visualization and analysis. If you need to update Oracle E-Business Suite records, you must do that through Oracle E-Business Suite forms or a separate EBS integration.