Oracle EDI Integration: EBS and Fusion Order Flow

A retail partner sends their vendor requirements: EDI 850 in, 855 acknowledgment back, 856 ship notice at shipment, 810 invoice for payment. You run Oracle. Which Oracle, E-Business Suite or Fusion Cloud, changes the mechanics completely, because the two platforms handle B2B messaging through different frameworks.

Oracle sells more than one ERP. This guide covers the two most common in a supplier context: Oracle E-Business Suite (EBS), the long-running on-premise suite, and Oracle Fusion Cloud ERP (also called Oracle Cloud ERP), the cloud platform. JD Edwards EnterpriseOne is a separate Oracle product with its own EDI framework, covered in our JD Edwards EDI integration guide. Here we walk through how EBS and Fusion each ingest an 850, and how to connect EDI to them.

Oracle EBS and Oracle Fusion Are Different Platforms

Oracle E-Business Suite and Oracle Fusion Cloud ERP are separate products with different B2B messaging frameworks. Choosing the right EDI approach starts with knowing which one you run.

• Oracle E-Business Suite (EBS) is the mature on-premise (or self-hosted cloud) suite. It processes B2B documents through the XML Gateway and the e-Commerce Gateway.
• Oracle Fusion Cloud ERP is Oracle's SaaS ERP. It handles B2B documents through the Collaboration Messaging Framework, abbreviated CMK.

The two do not share the same integration path, so a solution built for EBS does not carry over to Fusion unchanged. Oracle's documentation at docs.oracle.com is the reference of record for both the EBS gateways and the Fusion CMK setup described below.

EDI in Oracle E-Business Suite

EBS uses the XML Gateway and e-Commerce Gateway to move EDI and XML B2B documents in and out. These are the native EBS components that sit between a translator and the application.

The e-Commerce Gateway (historically the EDI Gateway) handles flat-file EDI transactions, mapping inbound files into the EBS Open Interface tables and extracting outbound data from them. The XML Gateway handles XML-based B2B messages using Oracle's message maps and the transport layer. In practice a translator converts the retailer's X12 EDI into the format the gateway expects, and the gateway loads it into the relevant Open Interface, such as the Order Import interface for sales orders.

For an inbound 850, the flow is:

1. The retailer transmits the EDI 850.
2. A translator converts the X12 into the gateway's expected format.
3. The e-Commerce Gateway or XML Gateway loads it into the Order Import interface.
4. EBS Order Import validates and creates the sales order.
5. EBS returns a 997, and an 855 if the partner requires acknowledgment.

Our EDI 850 purchase order guide breaks down the segments the translator reads, and the free EDI Inspector lets you paste a partner's file to see the parsed structure first.

EDI in Oracle Fusion Cloud ERP

Fusion Cloud ERP uses the Collaboration Messaging Framework (CMK) to exchange B2B documents with trading partners. CMK is the Fusion component that replaces the EBS gateway model.

CMK defines trading partners, message definitions, and delivery methods inside Fusion. An inbound 850 arriving through CMK becomes a sales order in Fusion Order Management. On the outbound side, CMK generates the documents the retailer expects: an 855 purchase order acknowledgment, an 856 advance ship notice, and an 810 invoice. CMK can connect to a translator or B2B service provider that handles the X12-to-CMK conversion, since retailers send X12 while CMK works in its own message formats.

The practical implication: on Fusion you configure trading partners and message flows in CMK rather than in an Open Interface. The concepts map across, but the tooling and setup are different from EBS.

The 855, 856, and 810 Flow Back Out

Outbound 855, 856, and 810 documents are generated from Oracle order, shipment, and invoice records. The return path mirrors the inbound flow on both platforms.

The 855 acknowledgment confirms you accepted the order or flags changes and substitutions. When you ship, Oracle generates an EDI 856 advance ship notice with the carton hierarchy and SSCC-18 labels the retailer requires. Timing is strict: most retailers require the ASN within 24 hours of shipment, and a late one triggers a chargeback. See our EDI 856 ship notice guide.

After invoicing, Oracle produces an EDI 810 that must reconcile to the original 850, including allowances and freight. Mismatches drive payment disputes. Our EDI 810 invoice guide covers the reconciliation, and every inbound document should draw a 997 functional acknowledgment.

Integration Methods for Oracle EDI

Oracle Integration Cloud (OIC) is the standard middleware for connecting a translator to EBS or Fusion. OIC provides adapters and orchestration between Oracle applications and external systems, including EDI translators and B2B service providers.

You have three realistic paths, each with a different cost and maintenance profile.

Approach	Setup Time	Who Maintains Mapping	Non-EDI Orders	Best Fit
EDI provider with Oracle connector	3-6 months	Vendor (ticket queue)	No	Suppliers with many retail partners
OIC + XML Gateway / CMK	3-6 months	Your team or SI	No	Shops with Oracle technical staff
Managed service (OrderSync)	1-3 weeks	OrderSync	Yes (EDI + PDF + email)	Distributors at realistic scale

The provider route brings a trading-partner network and compliance monitoring at higher monthly cost. The OIC route gives full control over the gateway or CMK mappings if you have the internal Oracle expertise and time for a longer project. Both assume every order arrives as clean EDI, which rarely holds for a real distributor.

How OrderSync Brings Orders Into Oracle

OrderSync creates Oracle sales orders from any order format, connecting through Oracle's supported interfaces. The inbound 850 becomes a sales order in EBS Order Management or Fusion Order Management. Order, shipment, and invoice records flow back out as 855, 856, and 810 documents. When a retailer changes their spec, we update the mapping. To connect orders to EBS or Fusion with OrderSync, see the Oracle integration page.

Distributors choose a service over a pure translator because of the orders that never arrive as EDI. Independent accounts email PDF purchase orders, send spreadsheets, or use buyer portals. A translator alone leaves those for your team to key by hand. OrderSync reads EDI 850s, PDF POs, and email orders through one pipeline and writes them all into Oracle, which fits distributors running a mix of large EDI partners and smaller manual accounts. See multi-format order processing and how the ERP integration connects to Oracle.

Running other systems too? Our related guides cover JD Edwards EDI integration for EnterpriseOne, EDI NetSuite integration, Infor EDI integration, and Sage EDI integration.

Confirm which Oracle you run before scoping anything. EBS work centers on the XML/e-Commerce Gateway and Open Interfaces; Fusion work centers on CMK trading partners and message definitions. The two are not interchangeable.

Frequently Asked Questions

Does Oracle have native EDI support?

Oracle provides B2B messaging frameworks rather than a raw X12 translator. E-Business Suite uses the XML Gateway and e-Commerce Gateway; Fusion Cloud ERP uses the Collaboration Messaging Framework (CMK). A translator or B2B service converts the retailer's X12 EDI into the format these frameworks expect, then Oracle creates the order.

What is the difference between Oracle EBS and Fusion for EDI?

EBS routes EDI through the e-Commerce Gateway and XML Gateway into Open Interface tables like Order Import. Fusion Cloud ERP routes B2B documents through the Collaboration Messaging Framework, where you configure trading partners and message definitions. The concepts are similar, but the tooling and setup differ between the two platforms.

How does an EDI 850 become a sales order in Oracle?

A translator converts the X12 850 into the format the Oracle framework expects. On EBS, the gateway loads it into the Order Import interface, which validates and creates the sales order. On Fusion, CMK receives the message and creates a sales order in Order Management. Both then generate outbound 855, 856, and 810 documents.

Is JD Edwards EDI the same as Oracle EBS EDI?

No. JD Edwards EnterpriseOne is a separate Oracle product with its own EDI framework, system 47, using F47xxx interface tables. Oracle EBS uses the XML and e-Commerce Gateways, and Fusion uses CMK. See our JD Edwards EDI integration guide for that platform's specifics.

Can OrderSync process non-EDI orders into Oracle?

Yes. OrderSync reads EDI 850s alongside PDF, email, and spreadsheet purchase orders and writes all of them into Oracle EBS or Fusion as sales orders through the same pipeline. Accounts that do not send EDI do not need a separate system or manual entry.