Oracle E-Business Suite and TrueCommerce integration

What moves between them

Outbound: Oracle EBS purchase orders and purchase order changes flow from EBS REST to ml-connector, are transformed into X12 850 and 860 documents, and are delivered to TrueCommerce SFTP or managed Exchange API on a daily or intra-day schedule. Inbound: X12 855 purchase order acknowledgments, 810 invoices, and 856 advance ship notices are retrieved from TrueCommerce SFTP, parsed and normalized by ml-connector, and posted into Oracle EBS AP_INVOICES_INTERFACE and PO_INTERFACE tables for import by concurrent programs. Reference data such as vendor accounts and item numbers are aligned bidirectionally so trading partner and EBS records stay in sync. Cadence is polling-based, scheduled according to your trading partner needs.

How ml-connector handles it

ml-connector stores the Oracle EBS ISG hostname, port, and HTTP Basic Auth credentials encrypted, and includes the required context headers (responsibility, application, organization, language) on every REST call to EBS. It polls EBS purchase orders and vendors on a schedule and transforms them to X12 format using the order and line data from PO_HEADERS_ALL and PO_LINES_ALL. On the inbound side, it polls TrueCommerce SFTP on schedule, retrieves EDI documents, parses them (X12 855, 810, 856), and normalizes them to match EBS open interface tables. Vendor names, purchase order numbers, item numbers, and GL code combinations are mapped so that when EBS concurrent programs import the interface data, the records reference valid vendors, items, and GL accounts. TrueCommerce returns no formal rate limits, so ml-connector implements exponential backoff on connection errors and tracks whether EBS REST calls are succeeding or returning 401 (requiring re-auth with a fresh session token). EDI deduplication is handled via ISA control numbers returned by TrueCommerce. Every record carries an audit trail with timestamps, credentials used, transformation details, and import status.

A real-world example

A mid-sized manufacturing distributor runs Oracle EBS for procurement and order management, and uses TrueCommerce to send EDI documents to major customers and receive orders from strategic suppliers via their own EDI implementations. Before the integration, the procurement team exported purchase orders from EBS into CSV, manually formatted them as X12 EDI, uploaded them to TrueCommerce via SFTP, and then manually downloaded 855 acknowledgments and 810 invoices, parsed them by hand, and re-entered the changes into EBS to update delivery dates and invoice amounts. With EBS and TrueCommerce connected, each purchase order generated in EBS automatically transforms to X12 and lands in the TrueCommerce outbox, and inbound acknowledgments and invoices are automatically parsed and posted to EBS interface tables for import without human intervention. The procurement cycle shrinks from days to hours.

What you can do

• •Export Oracle EBS purchase orders and changes as X12 850 and 860 documents and deliver them to TrueCommerce SFTP or managed Exchange API on a defined schedule.
• •Retrieve X12 855 acknowledgments, 810 invoices, and 856 advance ship notices from TrueCommerce and post them into EBS AP_INVOICES_INTERFACE and PO_INTERFACE for concurrent program import.
• •Transform EDI documents between X12 flat file format and EBS REST API JSON payloads, with full field mapping and entity matching.
• •Authenticate Oracle EBS via HTTP Basic Auth with required context headers (responsibility, application, organization, language), and retrieve credentials from encrypted storage.
• •Poll both Oracle EBS and TrueCommerce SFTP on a schedule you define, with error handling, exponential backoff, deduplication by ISA control number, and a complete audit trail for every document.

Questions

Which direction do purchase orders and invoices flow between Oracle EBS and TrueCommerce?

Outbound: purchase orders flow from Oracle EBS to TrueCommerce as X12 850 documents. Inbound: 855 purchase order acknowledgments, 810 invoices, and 856 advance ship notices flow from TrueCommerce back into EBS. Vendor reference data is synchronized in both directions so trading partner records and EBS vendor master stay aligned.

Does ml-connector handle the X12 EDI transformation, or do you need a separate EDI tool?

ml-connector handles the complete transformation. It reads EBS purchase orders from REST, transforms them to X12 850 format, and delivers them to TrueCommerce. On the return, it retrieves X12 documents from TrueCommerce SFTP, parses them, and transforms them into the exact schema required by EBS open interface tables. No separate EDI tool is needed.

What happens if an inbound TrueCommerce invoice cannot be matched to an EBS purchase order?

ml-connector posts the invoice to the EBS AP_INVOICES_INTERFACE table with the best matching vendor and order information from EBS, along with a detailed audit log entry noting the match status and any data discrepancies. An EBS concurrent program then attempts to import the record; if the match fails, the concurrent program rejects it with a standard EBS error, which is logged in the audit trail and can be reviewed to resolve the mismatch.