Oracle E-Business Suite and Procurify integration

What moves between them

Purchase orders and requisitions approved in Procurify are read by ml-connector on a daily or weekly schedule tied to your approval process, then written into EBS PO_HEADERS_INTERFACE and PO_LINES_INTERFACE as REST POST calls. A concurrent program job in EBS then imports these interface records into the base PO_HEADERS_ALL and PO_LINES_ALL tables. Vendor master records are synced in both directions so a new supplier in Procurify updates the EBS vendor table, and changes to EBS vendors are reflected back into Procurify so both systems see the same vendor codes, names, and payment terms.

How ml-connector handles it

ml-connector stores the EBS hostname, port, username, and password encrypted, then constructs the Integrated SOA Gateway URL per customer and obtains a session token via HTTP Basic Auth against the login endpoint. On the Procurify side, it exchanges the OAuth client credentials for a bearer token and refreshes it before expiry. When reading purchase orders from Procurify, it filters by creation and modification dates and maps the Procurify vendor code and order items to the matching EBS vendor and line details. When writing to EBS, it posts the transformed order to the PO interface table and calls the EBS Concurrent Manager REST endpoint to trigger the POXPOIIN import job, then polls the job completion API. If the token expires on either system, ml-connector re-authenticates on the next request. Rate limits on Procurify are unspecified, so ml-connector uses exponential backoff on 429 or timeout responses and tracks the EBS session expiry based on customer timeout settings.

A real-world example

A mid-sized manufacturing company uses Oracle E-Business Suite for order management and accounting, and has deployed Procurify as their cloud procurement workspace for internal teams and suppliers to request and approve orders. Before the integration, the procurement team entered approved orders from Procurify into EBS by hand each morning, matching vendor codes and cost centers, then re-keyed any vendor changes into Procurify the next time they updated supplier terms. With Oracle E-Business Suite and Procurify connected, each approved order flows into EBS automatically allocated to the correct cost center, vendors are mastered once and synced both ways, and procurement staff focus on strategy instead of data re-entry.

What you can do

• •Write approved purchase orders from Procurify into Oracle E-Business Suite PO interface tables and trigger the concurrent program import job.
• •Sync vendor codes, names, and payment terms between Procurify and Oracle E-Business Suite so both systems see the same supplier master.
• •Map Procurify cost centers and departments to Oracle E-Business Suite GL account combinations so orders land on valid dimensions.
• •Authenticate Procurify with OAuth 2.0 client credentials and Oracle E-Business Suite with HTTP Basic Auth and session tokens routed to the customer-hosted ISG.
• •Poll Procurify on a schedule tied to your approval workflow, with exponential backoff on rate limits and a full audit trail on every order.

Questions

Which direction does data move between Oracle E-Business Suite and Procurify?

The primary flow is from Procurify into Oracle E-Business Suite. Approved purchase orders and requisitions move from Procurify into EBS PO interface tables, then a concurrent program imports them into the base tables. Vendor master records are synced in both directions so each system reflects the other supplier updates.

How does ml-connector handle the EBS ISG requiring a customer-hosted hostname and port?

ml-connector accepts the full EBS hostname and port per customer, since there is no fixed ISG URL. It constructs the Integrated SOA Gateway URL dynamically and obtains a session token via HTTP Basic Auth against the customer ISG login endpoint on every session.

What happens after a purchase order is written to the EBS interface table?

ml-connector calls the EBS Concurrent Manager REST endpoint to submit the POXPOIIN concurrent program, which validates the interface records and imports them into PO_HEADERS_ALL and PO_LINES_ALL asynchronously. ml-connector polls the job completion endpoint and reports the outcome in the audit trail.