Oracle E-Business Suite and ServiceNow integration

What moves between them

Invoice, purchase order, and vendor data flows from Oracle EBS into ServiceNow Source-to-Pay staging tables. The primary flow pulls open invoices, POs, and active vendors from EBS on a daily schedule, validates them against ServiceNow supplier and GL account masters, and stages them for approval in ServiceNow's procurement and AP modules. Vendor synchronization works bidirectionally, so new suppliers registered in ServiceNow can be reflected in EBS vendor masters. GL account mappings are maintained so EBS cost centers and GL combinations match ServiceNow cost centers, ensuring accurate charge allocation during invoice posting.

How ml-connector handles it

ml-connector stores EBS credentials and retrieves a session token from the ISG login endpoint, presenting Basic Auth and the required application context headers on every request. Tokens expire after 30-60 minutes, so ml-connector re-authenticates on any 401 response. On the ServiceNow side, it uses OAuth 2.0 client credentials to obtain a 30-minute bearer token. Since both systems are pull-only, ml-connector polls EBS for new invoices and POs filtered by LAST_UPDATE_DATE at offset and limit pagination, then maps vendors to ServiceNow supplier records and GL combinations to ServiceNow cost centers. Open interface table writes in EBS are asynchronous, so ml-connector tracks the status of concurrent program imports and retries if they fail. Every record carries a full audit trail, and if a ServiceNow write fails mid-flow, the staging record can be replayed once the issue is resolved.

A real-world example

A mid-sized manufacturing company runs Oracle EBS for procurement and finance across three plants, and uses ServiceNow for incident management and Source-to-Pay request automation. Before the integration, the procurement team received approved requisitions in ServiceNow, manually created purchase orders in EBS, and waited for supplier invoices to arrive in EBS AP before ServiceNow could calculate payment terms. The finance team then matched EBS invoice GL postings to ServiceNow records by hand, a time-consuming error-prone process. With EBS and ServiceNow connected, approved requisitions in ServiceNow trigger PO creation in EBS, vendor master changes sync between systems, and invoices from EBS stage directly in ServiceNow for review and payment, eliminating manual re-entry and mismatches.

What you can do

• •Pull invoices, purchase orders, and vendors from Oracle EBS and stage them in ServiceNow Source-to-Pay for approval and payment.
• •Map EBS vendors to ServiceNow suppliers and EBS GL combinations to ServiceNow cost centers so financial charges land on valid accounts.
• •Handle EBS ISG session token refresh and ServiceNow OAuth 2.0 token expiry on every request cycle.
• •Poll on a daily schedule, filtering EBS records by last update date, with full retries and audit trails on every document.
• •Synchronize vendor master records bidirectionally between EBS and ServiceNow so procurement and finance stay aligned.

Questions

Which direction does data move between Oracle EBS and ServiceNow?

The primary flow is from Oracle EBS into ServiceNow. Invoices, purchase orders, and vendors are pulled from EBS and staged in ServiceNow Source-to-Pay for approval and payment. Vendor master synchronization works both directions, so new suppliers registered in ServiceNow can update EBS vendor records. GL account mappings align cost centers so charges post to the right accounts in both systems.

How does ml-connector handle Oracle EBS session token expiry and the application context headers?

ml-connector retrieves a session token from the EBS ISG login endpoint using HTTP Basic Auth and the required application context headers for responsibility, organization, and language. Tokens expire after 30-60 minutes, so ml-connector re-authenticates on any 401 response and retries the failed request. This ensures that long-running poll cycles do not fail mid-stream due to token expiry.

How does the integration work around the lack of webhooks in Oracle EBS and ServiceNow?

Both systems are pull-only, so ml-connector polls on a daily schedule. On the EBS side, it filters records by LAST_UPDATE_DATE with limit and offset pagination to find new invoices and POs. On the ServiceNow side, it queries the staging tables using sys_updated_on filters. If a concurrent program import in EBS fails, ml-connector tracks the status and retries, ensuring no records are lost.