Oracle E-Business Suite and Adobe Commerce integration

What moves between them

Orders and customers move from Adobe Commerce into Oracle E-Business Suite. ml-connector pulls placed orders, reads the embedded buyer, creates the customer through the TCA HZ interface if missing, and inserts order lines into the Receivables AutoInvoice interface so AutoInvoice can generate the AR invoice. Item master changes flow the other way, from EBS into the Commerce product catalog, to keep SKUs and descriptions aligned. Order capture runs on a short polling schedule, or a Commerce webhook can trigger an immediate pull; EBS item reads run on a slower batch cadence during off-peak windows. Adobe Commerce payment data is read from the order and invoice objects, since Commerce has no standalone payments resource.

How ml-connector handles it

The auth bridge is the central job. ml-connector holds Adobe Commerce OAuth 1.0a or IMS credentials and the EBS Basic Auth user, gets a session token from the EBS login service, and reuses the cookie until a 401 forces re-authentication. Commerce orders are read with searchCriteria paging filtered by updated_at; EBS reads page with offset and limit until a short page signals the end. Writes into EBS are asynchronous and two-step: ml-connector POSTs rows into the open interface table, stamps a unique connector SOURCE plus the buyer reference, then confirms the AutoInvoice or relevant concurrent program actually processed the batch rather than trusting the insert 200. Every write includes the correct ctx_orgid operating unit. Duplicates are guarded by the Commerce increment_id matched against the SOURCE and natural key in EBS, plus a BullMQ jobId. EBS has no rate limiter, so syncs stay at low concurrency to avoid degrading the shared server. There is no Commerce GL account resource, so GL coding stays in EBS.

A real-world example

A mid-sized industrial parts distributor with roughly 250 staff runs a B2B Adobe Commerce storefront for dealers while finance lives in Oracle E-Business Suite R12.2. Dealers place large orders online, but a clerk rekeys each one into Receivables, which delays invoicing and creates posting errors at month end. With ml-connector, each placed order pulls into EBS automatically, the dealer is created or matched as a TCA customer, and AutoInvoice builds the AR invoice against the right operating unit, cutting the rekeying and closing the gap between an online order and a posted receivable.

What you can do

• •Capture placed Adobe Commerce orders into the Oracle E-Business Suite Receivables AutoInvoice interface for AR invoice creation.
• •Create or match storefront buyers as Oracle EBS TCA customers before order lines are loaded.
• •Push Oracle E-Business Suite item master changes into the Adobe Commerce product catalog.
• •Bridge Adobe Commerce OAuth and EBS Basic Auth and stamp the correct operating unit on every write.
• •Confirm each EBS concurrent program processed its batch and dedupe on increment_id, SOURCE, and jobId.

Questions

Does Oracle E-Business Suite send webhooks when an order is invoiced?

Not in the modern sense. EBS has an internal Workflow Business Event System, but firing an external callback requires per-event admin setup through Oracle SOA Suite or Oracle Integration Cloud and uses Workflow XML, not a signed JSON webhook. ml-connector therefore polls EBS open interface views on a schedule, while Adobe Commerce can still push order events through its own synchronous webhooks.

How does ml-connector know an invoice was actually created in Oracle EBS?

EBS writes are two-step. The connector inserts order lines into the AutoInvoice interface table, and a 200 response only confirms the row was staged, not that the invoice exists. ml-connector then verifies the AutoInvoice concurrent program processed the batch by reading the base tables, so a stuck or rejected import is surfaced rather than silently lost.

Do I need the Adobe Commerce B2B module for this integration?

Not for the core order and customer sync. Standard orders, invoices, customers, and products are on the base REST surface and cover the storefront-to-EBS flow. The B2B module is only required if you also want to sync companies, purchase orders, or negotiable quotes, which depend on the Magento_PurchaseOrder and related B2B extensions.