Oracle E-Business Suite and BigCommerce integration

What moves between them

The main flow runs from BigCommerce into Oracle E-Business Suite. As orders are placed and paid, ml-connector reads the order, its line items, and its transactions and stages them as Receivables invoices in Oracle through the AutoInvoice interface, mapped to the matching customer and GL accounts; refunds post as credit memos or offsetting journal lines. Storefront customers are matched to Oracle TCA parties and accounts so each invoice lands on the right account. In the other direction, Oracle item and price changes flow out to update the BigCommerce catalog and SKUs. Order webhooks trigger the work as activity happens, and a scheduled poll of Oracle interface tables and BigCommerce orders backfills anything a webhook missed.

How ml-connector handles it

ml-connector stores both credential sets encrypted, sends the BigCommerce X-Auth-Token on every request, and logs into Oracle to obtain a session token, re-authenticating when a call returns 401 because EBS sessions expire after thirty to sixty minutes. It accepts the full Oracle base URL and the deployed service alias per customer, since EBS publishes no shared address and each admin names services differently, and it sends the operating unit org ID on every call so data stays inside the right org. BigCommerce webhooks are verified by recomputing the HMAC-SHA256 signature over the raw body against the client secret before processing, and because the payload is only a type and ID the connector immediately fetches the full order from the REST API. Writes into Oracle are asynchronous: the connector inserts into the open interface table with a unique SOURCE value, then confirms the concurrent program processed the batch rather than trusting the 200. Because EBS has no rate limiter and is shared, calls run at low concurrency on an off-peak window, while BigCommerce throttling returns HTTP 429 with reset headers the connector honors. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized consumer goods maker sells direct to shoppers through a BigCommerce storefront and runs Oracle E-Business Suite R12.2 for inventory, order accounting, and finance across one operating unit. Before the integration, the finance team exported the day's BigCommerce orders and refunds to a spreadsheet and keyed the revenue and tax totals into Oracle Receivables by hand, while the merchandising team re-typed new prices into the storefront whenever Oracle item costs changed. Mismatched SKUs and a one-day lag meant month-end close opened with the storefront deposits not tying to the ledger. With Oracle E-Business Suite and BigCommerce connected, each paid order posts into Receivables automatically against the right customer and GL accounts, refunds post as credit memos, and Oracle price changes update the catalog the same day. The re-keying is gone and close starts from reconciled sales.

What you can do

• •Post BigCommerce orders into Oracle Receivables as invoices through AutoInvoice, mapped to the right customer and GL accounts.
• •Record BigCommerce payments and refunds in Oracle as transactions and credit memos against the correct operating unit.
• •Push Oracle item and price changes out to the BigCommerce catalog and SKUs so the storefront prices from the system of record.
• •Verify BigCommerce HMAC-SHA256 webhooks and bridge the X-Auth-Token to Oracle's session-token login and multi-org context.
• •Poll Oracle interface tables and BigCommerce on a schedule, with low-concurrency pacing, retries, and a full audit trail on every record.

Questions

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

The main flow is BigCommerce into Oracle. Orders, payments, and refunds move from BigCommerce into Oracle Receivables and General Ledger, while customers are matched to Oracle TCA accounts. In the other direction, Oracle item and price changes flow out to keep the BigCommerce catalog priced from the system of record.

Does BigCommerce send purchase orders or GL accounts into Oracle?

No. BigCommerce is an e-commerce platform and has no native vendor, purchase order, or GL account objects. What it provides is order, transaction, refund, customer, and product data, and ml-connector maps that activity into Oracle Receivables invoices and General Ledger journal lines rather than as purchasing documents.

How does the integration handle Oracle's two-step writes and lack of webhooks?

Writes into Oracle stage a row in an open interface table, then a concurrent program such as AutoInvoice or Journal Import posts it, so ml-connector confirms the batch processed rather than trusting the initial 200. Because Oracle has no modern webhooks, it polls the interface tables and base tables by last update date on a schedule, while BigCommerce webhooks drive the inbound order flow in near real time.