Oracle PeopleSoft and Looker integration

What moves between them

Financial and transactional data flows from Oracle PeopleSoft into Looker. General ledger accounts, vendor information, purchase orders, supplier invoices, and payment status are read from PeopleSoft via REST polling on a schedule you define. The data is transformed to match Looker's query schema and pushed into Looker dashboards, looks, or scheduled delivery plans (cron-driven) so your finance team can view current metrics without manual export. Data flows one direction: PeopleSoft is the source of truth, Looker is the visualization layer. Looker does not write data back to PeopleSoft.

How ml-connector handles it

ml-connector stores Oracle PeopleSoft credentials (OPRID, password, and the customer's unique hostname and node name) encrypted, and authenticates with HTTP Basic Auth on each REST call. It polls PeopleSoft on a schedule you configure (typically daily or weekly for financial data) using date-range filters to fetch new invoices, GL entries, vendor updates, and payment records. When Looker's 1-hour OAuth2 bearer token expires, ml-connector re-authenticates automatically by exchanging client_id and client_secret for a new token before the next query. The integration maps PeopleSoft financial entities (GL accounts, vendors, invoices, cost centers) to Looker's query parameters and scheduled plan format, so the data lands in the right dashboards. Since PeopleSoft service operations must be activated by an administrator and each customer has a unique hostname and node configuration, ml-connector accepts per-customer PeopleSoft endpoints and validates them against your Integration Broker configuration. Results are batched by date range to respect Looker's 5000-row-per-call limit and to handle PeopleSoft's variable pagination. Failures are retried with exponential backoff, and every record is audited so a failed Looker scheduled plan delivery can be replayed.

A real-world example

A mid-sized financial services firm runs Oracle PeopleSoft for accounting, payables, and vendor management, and Looker for executive dashboards. Before the integration, the accounting team exported vendor invoices, GL account balances, and payment registers from PeopleSoft every week, loaded them into the data warehouse, and refreshed Looker dashboards manually. Month-end close reviews took extra days because dashboard data was 3 to 5 days old. With Oracle PeopleSoft and Looker connected, invoices and GL account updates flow automatically from PeopleSoft into Looker on a daily schedule. Dashboards now show near-current vendor aging, cash position, and expense allocation without the manual export step, so the finance team closes faster and has confidence in the numbers they are reporting.

What you can do

• •Sync general ledger accounts, vendors, purchase orders, and supplier invoices from Oracle PeopleSoft to Looker on a schedule you control.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth and Looker with OAuth2, handling token expiration and re-authentication automatically.
• •Poll Oracle PeopleSoft using date-range filters and per-customer hostnames and node names, respecting each customer's unique PeopleSoft environment.
• •Push financial data into Looker dashboards and scheduled delivery plans (email, S3, SFTP) so your finance team sees current metrics without manual exports.
• •Retry failed queries with exponential backoff and maintain a full audit trail on every financial record for compliance and replay.

Questions

How does the integration handle Oracle PeopleSoft's self-hosted architecture and unique hostnames?

Each Oracle PeopleSoft customer operates their own environment with a unique hostname, port, and node name. ml-connector stores the customer's specific PeopleSoft endpoint (hostname, node name, and RESTListeningConnector path) per cell and validates REST requests against that configuration. This allows the same integration logic to work across all PeopleSoft customers without a shared Oracle-managed API base URL.

What financial records move from Oracle PeopleSoft to Looker, and how often?

General ledger accounts, vendor information, purchase orders, supplier invoices, and payment status move from PeopleSoft to Looker. ml-connector polls PeopleSoft on a schedule you define (typically daily or weekly for financial close cadences) using date-range filters to fetch new or modified records. Data flows one direction only: PeopleSoft is the source of truth, and Looker is the visualization layer. Looker does not write back to PeopleSoft.

How does the integration manage Looker's 1-hour OAuth2 token expiration?

Looker OAuth2 bearer tokens expire after 1 hour with no refresh token endpoint. ml-connector automatically re-authenticates before each Looker API call by exchanging client_id and client_secret for a new token when the current token is near expiration. This ensures that scheduled plans and dashboard refreshes do not fail due to token age.