Oracle JD Edwards and TrueCommerce integration

What moves between them

Inbound EDI documents from trading partners flow into TrueCommerce's SFTP host. ml-connector polls TrueCommerce on a schedule you define (hourly or daily), pulls inbound purchase orders (X12 850), advance ship notices (856), and invoices (810) formatted as flat files, parses the EDI structure into JD Edwards entities, and posts them as purchase order headers/details (F4301/F4311), goods receipts (F0413), and invoice headers (F0401Z1 or equivalent). Outbound orders from JD Edwards can be scheduled to export to TrueCommerce for distribution to suppliers. Reference data such as supplier numbers and item numbers are mapped bidirectionally to keep both systems aligned.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the JD Edwards side, it obtains and refreshes a session token by posting the service account username and password to the tokenrequest endpoint, caches the token, and refreshes when a call returns HTTP 444 (invalid token). On the TrueCommerce side, it connects to integrationftp.truecommerce.com on port 22 using SFTP credentials, polls for new files in a customer-specific inbound folder on your schedule, and retrieves them. For each inbound document, ml-connector parses the EDI format (X12 850 to JD Edwards PO header/detail structure, 856 to goods receipt, 810 to invoice batch), maps supplier and item numbers to their JD Edwards equivalents, and posts via the orchestration endpoint or form service. Every document carries its source EDI control numbers so retransmissions are detected and duplicates discarded. If a JD Edwards post fails, ml-connector retries with exponential backoff; if it succeeds but a downstream allocation fails, the record is flagged in the audit log for manual review. Session tokens are tied to JD Edwards user licenses, so the service account must remain active. TrueCommerce files are left on the SFTP host with a flag or moved to a processed folder to avoid re-processing.

A real-world example

A regional consumer-goods distributor runs JD Edwards for procurement and financials. They source from 40 suppliers, each sending purchase order acknowledgments and advance ship notices via TrueCommerce EDI. Before the integration, the procurement team manually downloaded EDI files from TrueCommerce, converted them to Excel spreadsheets, and typed matching PO numbers and quantities into JD Edwards goods receipts every day. Month-end close was delayed waiting for the accounting team to chase missing invoices and verify that all receipts matched their source orders. With TrueCommerce connected to JD Edwards, inbound EDI documents post as PO acknowledgments and goods receipts automatically, matched to the correct JD Edwards purchase orders by supplier and PO number. The accounting team now starts close with all receipts already recorded and matched, eliminating the manual re-keying and reducing close time by three days.

What you can do

• •Parse inbound EDI purchase orders (X12 850) and post them as JD Edwards purchase order headers and detail lines, mapped to supplier and item numbers.
• •Convert advance ship notices (856) into JD Edwards goods receipts and update PO receipt status automatically.
• •Post supplier invoices (810) as AP invoice batches in JD Edwards, matched to the correct PO and receipt.
• •Maintain a full audit trail of every EDI document received, parsed, and posted, with the source control numbers and JD Edwards document IDs linked for traceability.
• •Sync supplier master and item master between TrueCommerce and JD Edwards so trading partner references resolve correctly on every document.

Questions

How does ml-connector handle the fact that JD Edwards runs on-premises and TrueCommerce is in the cloud?

ml-connector runs as a cloud service that polls TrueCommerce SFTP on your schedule and connects back to your customer-hosted JD Edwards AIS Server via REST. Your AIS Server firewall must allow outbound HTTPS calls to TrueCommerce and inbound connections from ml-connector. JD Edwards session tokens are obtained by posting your service account credentials to the AIS Server tokenrequest endpoint; ml-connector refreshes the token when it receives an HTTP 444 invalid-token response.

What happens if an EDI document fails to post into JD Edwards?

ml-connector logs the failure with the original EDI control number and JD Edwards error details in the audit trail. It retries the post with exponential backoff up to a configurable threshold. If the post succeeds but a subsequent step (like cost allocation) fails, ml-connector flags the record for manual review. The original EDI file is not deleted from TrueCommerce until the post succeeds, so no documents are lost.

Which EDI documents does ml-connector support, and can it handle custom file formats?

ml-connector supports the standard TrueCommerce documents: purchase orders (X12 850), advance ship notices (856), and invoices (810). These map to JD Edwards purchase orders, goods receipts, and AP invoices respectively. If your trading partners send documents in a custom format or use a different document type, mapping rules can be configured per document type during setup. TrueCommerce file naming conventions and inbound folder paths are customer-specific, so those must be confirmed with TrueCommerce operations before deploying the integration.