Oracle JD Edwards and IBM Sterling integration

What moves between them

Purchase orders flow from JD Edwards into Sterling. When JD Edwards tables F4301 and F4311 (PO header and detail) are updated, ml-connector reads them on a polling schedule, translates them to ANSI X12 850 (EDI Purchase Order) format, and writes them into Sterling mailboxes for outbound delivery to suppliers. When suppliers respond with 810 invoices and 856 shipment notices, ml-connector polls Sterling mailbox messages to extract the EDI documents, translates them back to JD Edwards structure, and writes them into the F0411 (Accounts Payable) table and F0413/F0414 (AP Matching Documents) for GL posting. JD Edwards vendors are pre-mapped to Sterling Trading Partners so outbound documents route to the correct supplier. Reconciliation happens in JD Edwards: matched invoices generate GL postings to F0911 on schedule.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the JD Edwards side, it accepts the customer-provided AIS Server URL and base64-encodes the username and password to obtain a session token, then refreshes the token when the default 30-60 minute window expires or when a 444 response arrives. On the Sterling side, it authenticates with HTTP Basic Auth or OAuth 2.0 Client Credentials and polls mailbox messages at regular intervals, extracting each message payload to read the EDI document. PO translation maps JD Edwards F4301 header fields (ship-to address, terms from F0401 supplier record) to X12 850 syntax and F4311 detail lines (item number from F4101, quantity, unit price) to 850 line items. For inbound invoices (810), ml-connector parses the EDI structure, cross-references the PO number to find the matching JD Edwards purchase order, and writes the invoice detail into F0411 and F0413 (AP Matching) as a batch via the orchestration endpoint or F0411Z1 batch loader. Vendors are matched by EDI Interchange ID in Sterling Trading Partner setup and mapped to the F0401 supplier code in JD Edwards; if mapping is undefined, the record is held for manual review. Because JD Edwards AIS Server may have configured IP allowlists, ml-connector's egress IPs must be whitelisted in advance. Both systems run polling on a fixed schedule (daily, twice-daily, or per shift based on order volume) rather than real-time, since neither supports webhooks. Every record carries an audit trail with timestamp, direction, and matched PO or invoice number for traceability.

A real-world example

A mid-sized discrete parts manufacturer runs Oracle JD Edwards EnterpriseOne for manufacturing, procurement, and finance, and uses IBM Sterling B2B Integrator to manage EDI with 40+ suppliers across automotive and industrial sectors. Before the integration, the procurement team exported purchase orders from JD Edwards every morning, manually converted them to EDI X12 format using a spreadsheet template, loaded them into Sterling, and then manually extracted supplier invoices and ASNs from Sterling, re-keyed them into JD Edwards, and matched them to POs in Accounts Payable (a process taking 3-4 hours per day and producing frequent transcription errors). With JD Edwards and Sterling connected, purchase orders flow automatically from JD Edwards into Sterling on a daily schedule before 6 AM, supplier invoices and shipment notices are extracted and posted into Accounts Payable automatically during the overnight processing window, and month-end close starts with AP reconciled and GL ready for posting. The procurement team now spends that 3-4 hours on exception handling and supplier communication instead of data entry.

What you can do

• •Automatically translate and send JD Edwards purchase orders (F4301 and F4311) to IBM Sterling as ANSI X12 850 EDI documents on a daily or twice-daily schedule.
• •Extract supplier invoices (X12 810) and advance shipment notices (X12 856) from Sterling mailbox messages and post them into JD Edwards Accounts Payable (F0411) for matching and GL posting.
• •Map JD Edwards vendor master records (F0401) to Sterling Trading Partners by EDI Interchange ID so outbound orders route to the correct supplier.
• •Manage JD Edwards AIS Server session token refresh across the default 30-60 minute expiry window and handle 444 token-invalid responses automatically.
• •Provide a complete audit trail of every PO sent to Sterling, every invoice received, and every GL posting generated for month-end reconciliation and exception handling.

Questions

How does ml-connector handle JD Edwards AIS Server authentication and token refresh?

ml-connector stores the AIS Server URL, username, and password encrypted. It obtains a session token by POSTing to the tokenrequest endpoint and includes the token in the jde-AIS-Auth header on all data service calls. Token lifetimes default to 30-60 minutes; ml-connector refreshes the token before expiry and handles 444 responses (invalid token) by re-authenticating automatically. If the customer has IP allowlists configured on the AIS Server, ml-connector's egress IPs must be whitelisted in advance.

What happens when a supplier invoice arrives in Sterling but the purchase order is not found in JD Edwards?

ml-connector matches incoming 810 invoices by PO number extracted from the EDI X12 document (field PO1). If the PO is not found in JD Edwards F4301, the invoice record is held in a manual review queue with the original EDI payload and the missing PO number flagged. The procurement team can then investigate the discrepancy (PO not yet created, typo in supplier EDI, vendor sent invoice for wrong customer) and either correct JD Edwards, re-send the EDI to the supplier, or skip the record.

Does the integration support both X12 and EDIFACT, or only one EDI standard?

IBM Sterling supports both X12 and EDIFACT as well as non-EDI file protocols (SFTP, FTP, AS2). The integration is built around X12 (850 Purchase Orders, 810 Invoices, 856 Shipment Notices) as the most common North American standard. If your suppliers use EDIFACT or require file-based protocols instead, the mapping and translation can be reconfigured per supplier using Sterling's trading partner and document profile setup, and ml-connector will extract and process them the same way.