Oracle JD Edwards and Orderful integration

What moves between them

The flow runs from JD Edwards into Orderful. ml-connector polls JD Edwards purchase order headers and lines on a regular schedule and translates them into Orderful EDI 850 (purchase order) transactions, mapping JD Edwards vendor master records to Orderful ISA identifiers. Approved invoices and AP line items are translated into EDI 810 (invoice) transactions. Purchase order changes (EDI 860) are generated when JD Edwards PO quantities or dates change. Orderful handles the translation to X12 or EDIFACT format and delivery to each trading partner based on their configured channel (AS2, SFTP, or HTTP).

How ml-connector handles it

ml-connector stores the JD Edwards AIS Server URL and credentials (username and password) encrypted and uses them to request a session token on each poll cycle. If a token expires (indicated by HTTP 444), ml-connector re-authenticates without manual intervention. Because JD Edwards tokens have a 30 to 60 minute lifetime by default, the connector refreshes them proactively to avoid interruption. ml-connector queries the JD Edwards F4301 (PO Header) and F4311 (PO Detail) tables with a date filter on the UPMJ (updated date) field to retrieve only new or changed orders since the last poll. Purchase orders are mapped to Orderful purchase order transactions using the vendor master (F0401) to determine ISA identifiers; line-item GL accounts are preserved in the EDI output where partner systems consume them. API calls to Orderful include the static orderful-api-key header and specify the stream field as 'test' in development or 'live' in production to ensure transactions go to the correct partner channel. JD Edwards has no documented explicit rate limits, but practical limits depend on the AIS Server JVM heap and thread pool; ml-connector spaces out requests and backs off if the server responds slowly. Every transaction is logged with its poll timestamp, record counts, and translation status, so failed conversions can be replayed once the underlying issue is fixed.

A real-world example

A mid-sized discrete manufacturer runs JD Edwards for procurement, manufacturing, and finance, and ships products to 40 trading partners globally. Before the integration, the procurement team exported purchase orders from JD Edwards each week, manually formatted them as X12 850 EDI messages, and uploaded them to partner portals or sent them via email, a process that took 6 hours per cycle and introduced manual entry errors. With JD Edwards and Orderful connected, each new purchase order is automatically translated into the EDI 850 format required by each partner and delivered via their preferred channel (AS2, SFTP, or HTTP portal). Partners confirm receipt via EDI 855 acknowledgments, which ml-connector tracks in the audit log. Invoice corrections and cancellations flow the same way, keeping partners informed in real time and eliminating the weekly manual export and upload step.

What you can do

• •Translate JD Edwards purchase orders into Orderful EDI 850 transactions and deliver them to trading partners via their preferred channel.
• •Map JD Edwards vendor master records and GL accounts to Orderful ISA identifiers so each trading partner receives orders in the correct format.
• •Refresh JD Edwards session tokens automatically when they expire so polling continues without manual re-authentication.
• •Poll JD Edwards purchase order headers and lines on a schedule and track the last-polled timestamp to avoid re-processing the same records.
• •Preserve a complete audit trail of every JD Edwards transaction pulled, every EDI translation performed, and every Orderful delivery, with the ability to replay any transaction if a downstream call fails.

Questions

How does the connector handle JD Edwards session tokens expiring during a polling cycle?

JD Edwards session tokens expire every 30 to 60 minutes by default. ml-connector checks the HTTP status code on each request; if it receives HTTP 444 (invalid token), it immediately re-authenticates by calling /jderest/v2/tokenrequest with the stored username and password to obtain a fresh token and retry the failed request. This happens transparently without pausing the polling cycle.

How are JD Edwards vendors and GL accounts mapped to Orderful EDI format?

ml-connector queries the JD Edwards F0401 (Supplier Master) and F0901 (Account Master) tables to retrieve vendor and GL account details. Vendor records are mapped to Orderful ISA identifiers (sender/receiver codes) so that each purchase order is routed to the correct trading partner. GL account codes are preserved in the EDI line-item detail where partner systems require them for cost allocation.

What happens if a JD Edwards purchase order changes after the initial EDI 850 is sent to a trading partner?

ml-connector polls the UPMJ (updated date) field in the F4301 and F4311 tables on each cycle. If a purchase order quantity, date, or price changes, the connector detects the change, generates an EDI 860 (Purchase Order Change) transaction, and sends it to Orderful for delivery. The trading partner receives the change notification and can update their internal record to match JD Edwards.