Oracle E-Business Suite and Procore integration

What moves between them

The main flow runs from Oracle E-Business Suite into Procore. Purchase order headers, vendors, and GL code combinations are read from EBS on a configurable schedule and written as purchase order contracts and vendors in Procore. When a requisition is created in Procore against a purchase order, ml-connector can post the matched cost back to EBS as a GL journal entry if needed, keeping procurement and accounting in sync. Vendor master data is one-directional from EBS to Procore, so vendors created in Procore do not flow back to Oracle.

How ml-connector handles it

ml-connector accepts the hostname and port for your Oracle E-Business Suite instance and stores HTTP Basic Auth credentials encrypted. It logs in once per polling cycle, obtains the session token, and adds the required application context headers (organization ID, responsibility, security group, language) to every REST call. On the Procore side, it exchanges client credentials for an OAuth2 bearer token at login.procore.com, stores both credentials encrypted, and refreshes the token every 1.4 hours before expiry. The connector maps EBS GL code combinations (account plus cost center plus department segments) to Procore cost codes during the first sync, so every requisition and purchase order allocation lands on a valid project dimension. Because EBS is on-premises and polling only, ml-connector polls purchase orders and vendors on a schedule you control, typically nightly or weekly. Procore webhooks are registered for real-time cost and change-order updates so urgent budget changes reach EBS quickly. The connector tracks EBS session timeout (typically 30-60 minutes) and re-authenticates without manual intervention when the session expires.

A real-world example

A regional construction company runs Oracle E-Business Suite for accounting and procurement across four branch offices. Procore is their system of record for project costs and budget tracking across 40 active projects. Before the integration, the office manager exported approved purchase orders from Oracle weekly, manually re-entered them as commitments in Procore, and then at month-end spent days matching project costs in Procore against the GL postings in Oracle. With Oracle E-Business Suite and Procore connected, new purchase orders flow into Procore automatically within hours, mapped to the correct project cost codes. Month-end close now starts with project costs already reconciled to the general ledger, eliminating the manual matching step.

What you can do

• •Sync vendors and purchase order headers from Oracle E-Business Suite into Procore as vendors and purchase order contracts.
• •Map Oracle GL code combinations to Procore cost codes so project charges land on valid accounting dimensions.
• •Read requisitions and cost changes from Procore and post matched costs back to Oracle E-Business Suite as GL journal entries.
• •Authenticate Oracle E-Business Suite via HTTP Basic Auth and session tokens, and Procore via OAuth2, with automatic token refresh.
• •Poll Oracle on a schedule you control with session timeout handling, and receive real-time cost updates from Procore webhooks.

Questions

How does ml-connector handle Oracle E-Business Suite session tokens and HTTP Basic Auth?

ml-connector stores the EBS hostname, port, username, and password encrypted. At the start of each polling cycle, it authenticates via HTTP Basic Auth to the login endpoint, receives a session token in XML, and adds the required application context headers (organization ID, responsibility, security group, language) to every subsequent REST call. If the session expires (typically after 30-60 minutes), the connector re-authenticates automatically on the next poll without manual intervention.

How are Oracle GL accounts mapped to Procore cost codes?

During the initial sync, ml-connector reads GL code combinations from Oracle E-Business Suite (combining the account segment, cost center, and department segments per your GL structure). These are mapped to Procore cost codes by name or numeric ID. On subsequent syncs, requisitions created in Procore are checked against the mapping to ensure costs post to the correct GL account when returned to Oracle E-Business Suite.

Does data flow both directions between Oracle E-Business Suite and Procore?

The main flow is from Oracle into Procore: vendors and purchase orders sync from EBS to Procore. Costs and change orders flow from Procore back to EBS as GL journal entries when matched to purchase orders. Vendor master data is one-directional from EBS only, so vendors created in Procore do not flow back to Oracle.