Oracle PeopleSoft and Microsoft Power BI integration

What moves between them

The main flow is from Oracle PeopleSoft into Microsoft Power BI. GL account balances, supplier master records, purchase orders, and invoice status flow from PeopleSoft on a daily or weekly schedule, depending on your close calendar and reporting cadence. Employee records, absence balances, and payroll summaries are pushed at the same cadence. Each record includes date stamps for reconciliation and drill-down. The connector transforms PeopleSoft rowset format into Power BI table rows and posts them to your datasets via REST, then triggers a dataset refresh so your dashboards reflect the latest data immediately. No data flows back from Power BI to PeopleSoft; Power BI is read-only.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the PeopleSoft OPRID and password, or OAuth2 token if your version supports it, and the Power BI service principal client ID and secret. At sync time, it authenticates to Oracle PeopleSoft using HTTP Basic Auth or Bearer token, issues a REST or SOAP request with a date-range filter to pull only new or changed records, and parses the response from PeopleSoft's rowset or XML format. The connector then maps each field to the Power BI table schema you have defined, validates that all required columns are present, and POSTs the rows as JSON to your Power BI push dataset. If the POST succeeds, it triggers a dataset refresh so downstream reports and dashboards query the fresh data. If a POST fails, the connector retries with exponential backoff and logs a detailed audit record so you can see exactly which records succeeded and which failed. Because Oracle PeopleSoft is behind your firewall, the connector must run with network access to your PeopleSoft hostname and port, either via a static IP whitelist or a reverse proxy. Token expiry is tracked so a refresh does not cause an outage mid-sync.

A real-world example

A mid-market manufacturing company runs Oracle PeopleSoft for finance and procurement, with a separate payroll operation. Before the integration, the CFO and procurement team exported GL data and PO status from PeopleSoft by hand each week, loaded it into Excel, and manually refreshed their Power BI dashboards. Reporting lags by 2-3 days, and any restatement in PeopleSoft requires a manual refresh. With Oracle PeopleSoft and Power BI connected, GL balances and purchase orders flow into Power BI automatically every night. Dashboards update overnight, so the morning stakeholder meeting always shows current spend, cash flow, and procurement status. Month-end close includes real-time PO status and supplier invoice aging, and the manual export step is eliminated.

What you can do

• •Push Oracle PeopleSoft GL balances, cost centers, and account hierarchies to Power BI to visualize budget variance and financial health.
• •Stream supplier master data, purchase orders, and invoice status into Power BI dashboards for procurement intelligence and spend analysis.
• •Sync employee records, job titles, departments, and headcount from PeopleSoft payroll to Power BI for workforce planning and organizational reporting.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer token, and Power BI with service principal credentials, handling token expiry and refresh automatically.
• •Poll Oracle PeopleSoft on a schedule tied to your month-end, payroll, or purchasing cycle, with a full audit trail on every record pushed to Power BI.

Questions

How does the integration handle the fact that Oracle PeopleSoft is on-premise behind a firewall?

ml-connector requires network access to your PeopleSoft hostname and port. This is typically handled by whitelisting the connector IP address on your firewall, or routing through a reverse proxy that your security team has approved. Once network access is established, authentication uses your PeopleSoft OPRID and password, or OAuth2 token if you are on PeopleTools 8.58 or later.

Can I push specific GL accounts or suppliers, or does every record have to flow to Power BI?

The connector filters at the PeopleSoft query level using date-range parameters or custom business object queries, so you can scope the sync to specific business units, GL ranges, or entity types before any data reaches Power BI. Once the connector selects the records to move, it maps them to your Power BI table schema and pushes only the columns you have defined.

What happens if a Power BI push fails or a Power BI token expires?

ml-connector tracks every push attempt in its audit log, so you can see exactly which records succeeded and which failed. If a call fails, it retries with exponential backoff before giving up. Power BI tokens expire after one hour; ml-connector automatically refreshes the token by re-authenticating with your service principal credentials before the next sync run, so expiry does not interrupt your schedule.