The short answer
Oracle E-Business Suite exchanges EDI through e-Commerce Gateway, which imports and exports flat files that an EDI translator converts to and from X12 or EDIFACT. Inbound purchase orders load through Order Import open interface tables and concurrent programs, while outbound transactions extract ship notices and invoices. XML Gateway and Integrated SOA Gateway add XML and web service options.
Read the diagram from top to bottom. E-Business Suite does not exchange X12 itself in this design: the integration layer handles the partner connection and translation, and E-Business Suite creates and posts the business records. Outbound documents are built from what E-Business Suite actually recorded.
How EDI connects to E-Business Suite
Oracle E-Business Suite (EBS) has supported EDI for decades, and many EBS instances run large, mature trading partner programs, often with IBM Sterling or another translator. EBS offers several integration mechanisms; most EDI programs use e-Commerce Gateway and open interface tables, sometimes alongside XML Gateway.
Common transactions
| EDI document | Direction | e-Commerce Gateway transaction | EBS object |
|---|---|---|---|
| 850 purchase order | Inbound | POI | Sales order through Order Import |
| 860 order change | Inbound | POCI | Sales order change through Order Import |
| 855 acknowledgment | Outbound | POAO | Order acknowledgment |
| 856 ship notice | Outbound | DSNO | Ship confirmation |
| 810 invoice | Outbound | INO | Receivables invoice |
Inbound flow: customer orders
- The translator converts the partner’s 850 into an e-Commerce Gateway flat file.
- The e-Commerce Gateway inbound program loads the data into the Order Import open interface tables.
- The Order Import concurrent program validates the data and creates sales orders.
- Records that fail validation stay in the interface with error messages for correction in the Order Import corrections form.
Outbound flow
Outbound programs extract data after the business event, such as ship confirmation for ship notices or Receivables invoice creation for invoices, write flat files and pass them to the translator. Schedule these concurrent programs often enough to meet partner deadlines.
Trading partner setup
- e-Commerce Gateway trading partners link partner identifiers and enabled transactions to customer or supplier sites.
- Customer items and cross-references map customer item numbers to inventory items.
- Code conversions translate partner codes, such as units of measure, to EBS values.
Other integration options
- XML Gateway exchanges XML business documents, including OAGIS-style messages.
- Integrated SOA Gateway exposes EBS business services as REST or SOAP web services for real-time scenarios.
Upgrades and the road ahead
Many EBS customers plan upgrades within release 12.2 or a move to Oracle Fusion Cloud ERP. Keep partner-specific logic in the integration layer and document custom extensions so EDI can move with the ERP. See the ERP migration checklist.
Best practices
- Review Order Import interface errors daily and assign owners.
- Maintain customer item cross-references as part of partner onboarding.
- Use code conversions consistently rather than hard-coding values in maps.
- Monitor end to end, not only concurrent program completion.
- Document customizations to EDI programs and interface tables.