Oracle E-Business Suite and Cin7 integration

What moves between them

Suppliers and purchase orders flow from Cin7 into Oracle E-Business Suite. New suppliers created in Cin7 sync to the EBS vendor master, and purchase orders and receipts flow into the PO module. GL account mappings are aligned in both directions so Cin7 sales and purchase transactions can post to the correct EBS GL accounts and cost centers. The integration polls on a regular schedule that you define, typically tied to your procurement cycle, and can also receive webhook events from Cin7 when they are enabled for purchase and supplier changes.

How ml-connector handles it

ml-connector stores Cin7 API keys encrypted and presents them on every REST request. On the Oracle side, it accepts the customer-specific EBS hostname and port since there is no shared public URL, obtains and caches a session token via the login endpoint, and re-authenticates when a call returns 401 due to token expiry. Because EBS writes to interface tables are asynchronous (the connector inserts into an open interface table and Oracle runs a concurrent program to import into base tables), ml-connector tracks the import status and retries if validation fails. Supplier names and PO line items are mapped between Cin7's format and EBS's expected GL account and cost center dimensions. Cin7's webhook payloads are received, validated per custom header token, and enqueued for processing. EBS rate limiting is not strict, but network timeouts and token refresh race conditions are handled with exponential backoff and full audit trail on every record.

A real-world example

A growing wholesale distributor runs Oracle E-Business Suite on premises for AR, AP, GL, and purchase order management. The company uses Cin7 Core in the cloud to manage inventory, sales orders, and supplier data across two warehouses. Before the integration, the procurement team entered new suppliers into both systems by hand, and received items from Cin7 had to be keyed into EBS PO receipts before the goods were moved to inventory. With Cin7 and Oracle E-Business Suite connected, new suppliers created in Cin7 automatically sync to the EBS vendor master with the correct GL account assignments, and receipt confirmations from Cin7 flow into EBS PO receipts with proper cost center allocation. The team no longer re-enters supplier or receipt data, and month-end matching of inventory movement to GL accounts is faster.

What you can do

• •Sync suppliers created in Cin7 into Oracle E-Business Suite's vendor master with GL account and cost center assignments.
• •Move purchase orders and receipt confirmations from Cin7 into EBS PO headers and lines, with automatic import via concurrent program.
• •Align GL account dimensions between Cin7 and EBS so sales and purchase transactions post to the correct accounts and cost centers.
• •Handle Oracle's session token expiry and re-authentication, and Cin7's custom API key authentication on every request.
• •Poll on a schedule tied to your procurement cycle, with full audit trail and error replay on every record.

Questions

How does ml-connector handle Oracle E-Business Suite's customer-specific hostname?

Because EBS does not publish a shared public URL, ml-connector accepts the full hostname and port per customer during configuration. The connector then discovers available REST services via the Integration Repository and validates that the required endpoints are deployed before attempting reads or writes.

Are EBS writes to interface tables synchronous?

No. When ml-connector inserts data into an EBS open interface table (such as AP_INVOICES_INTERFACE), Oracle runs a concurrent program asynchronously to import and validate the data into base tables. ml-connector tracks the import status and retries if validation fails, with full audit trail on every import attempt.

What if Cin7's webhook events are not enabled?

ml-connector will fall back to polling Cin7 for supplier, purchase, and customer changes on the schedule you configure. Polling is less real-time than webhooks but still reliable for procurement cycles that run daily or weekly. Webhooks can be enabled at any time in Cin7's Automation module without changing the integration.