Oracle Fusion Cloud ERP and TrueCommerce integration

What moves between them

Purchase orders and supplier invoices flow from Oracle Fusion Cloud ERP into TrueCommerce. ml-connector polls Oracle Fusion every 5 to 15 minutes (on a schedule you control) for new or updated purchase orders and invoices, transforms them into X12 850 (Purchase Order) and X12 810 (Invoice) EDI documents, and uploads them to your TrueCommerce SFTP account. Functional acknowledgments from TrueCommerce (X12 997) flow back into Oracle Fusion as audit records. No data flows from TrueCommerce back into Oracle Fusion transactional fields - TrueCommerce remains read-only from Oracle Fusion's perspective.

How ml-connector handles it

ml-connector stores your Oracle Fusion OAuth credentials (client ID and secret) and your TrueCommerce SFTP credentials encrypted and uses them to authenticate on your behalf. For Oracle Fusion, it refreshes the OAuth Bearer token when it is within 5 minutes of expiry, filtering the purchase orders and invoices API by LastUpdateDate to poll only changes since the last run. Each purchase order and invoice is transformed into the correct X12 850 or 810 flat file format, named according to your TrueCommerce integration path convention (which you confirm during setup). ml-connector uploads files to TrueCommerce SFTP and tracks the ISA control number (the X12 message sequence number) to deduplicate functional acknowledgments 997 when they return. If the TrueCommerce SFTP upload fails, it retries with exponential backoff; all records carry a full audit trail so a failed upload can be replayed. TrueCommerce processes the files on its hourly polling cycle (or via Exchange API in near-real-time if configured), and your trading partners receive the PO or invoice in their standard EDI mailbox.

A real-world example

A mid-sized distributor manages supplier relationships and procures through Oracle Fusion Cloud ERP. The distributor must send purchase orders and invoices to a network of 50+ suppliers, many of whom accept EDI X12 only. Before the integration, procurement staff exported purchase orders from Oracle Fusion, manually formatted them in Excel, converted them to X12 files, uploaded them to the TrueCommerce portal, and tracked status manually via email. This consumed 8 hours per week and introduced re-keying errors when terms or supplier IDs changed. With Oracle Fusion and TrueCommerce connected, each new purchase order in Oracle Fusion automatically flows to TrueCommerce and is delivered to the supplier's EDI mailbox within minutes. The distributor's procurement team focuses on negotiations and supplier management rather than file logistics, and supply chain visibility improves because exceptions (failed transforms, missing supplier EDI addresses) surface automatically in the audit trail.

What you can do

• •Automatically publish Oracle Fusion purchase orders to TrueCommerce as X12 850 EDI documents on a schedule you control.
• •Transform Oracle Fusion supplier invoices into X12 810 EDI invoices and upload them to your TrueCommerce SFTP account.
• •Deduplicate EDI functional acknowledgments (X12 997) from TrueCommerce using ISA control numbers so each PO or invoice is confirmed exactly once.
• •Authenticate Oracle Fusion using OAuth 2.0 with automatic token refresh, and TrueCommerce via SFTP credentials, both encrypted at rest.
• •Track every document transformation and upload in a full audit trail so failed transmissions can be replayed and delivery status is always queryable.

Questions

Which documents flow from Oracle Fusion to TrueCommerce, and how often?

Purchase orders (X12 850) and supplier invoices (X12 810) flow from Oracle Fusion to TrueCommerce. ml-connector polls Oracle Fusion every 5 to 15 minutes (on a cadence you configure) for new or updated orders and invoices, filtering by LastUpdateDate to pull only recent changes. Each document is uploaded to TrueCommerce SFTP on the same cycle.

Does the integration support acknowledgments and exception handling?

Yes. When TrueCommerce receives a purchase order or invoice, it returns a functional acknowledgment (X12 997) with an ISA control number. ml-connector deduplicates these using the ISA control number so each PO or invoice is confirmed exactly once. All upload attempts (successful and failed) are logged in the audit trail for replay and troubleshooting.

What credentials and configuration does ml-connector need?

ml-connector needs your Oracle Fusion OAuth client credentials (ID and secret provisioned in your OCI Identity Domain) and your TrueCommerce SFTP username and password (provisioned by TrueCommerce during account setup). You also provide your Oracle Fusion pod URL and confirm your TrueCommerce SFTP path convention during onboarding so file names match your integration's expected layout.