How does ml-connector handle Oracle JD Edwards on-premises deployment and token expiry?

Since Oracle JD Edwards AIS Server is deployed at customer infrastructure with no shared hostname, ml-connector accepts the full customer-provided AIS Server URL as a credential. Session tokens issued by Oracle JD Edwards are valid for 30 to 60 minutes; ml-connector stores the username and password encrypted, obtains a new token on each poll cycle, and re-authenticates immediately if a call returns HTTP 444 (invalid token). Token expiry never causes an outage because the token is refreshed before use.

What if Oracle JD Edwards supplier IDs or cost codes do not exist in Coupa?

ml-connector validates supplier IDs and cost codes against both systems before posting. A mismatch creates a failed record with a full audit trail, and the operator can correct the mapping in ml-connector's configuration or add the missing supplier or cost code to Coupa before replaying the failed batch. This prevents partial syncs and orphaned invoices.

Oracle JD EdwardsCoupa

Oracle JD Edwards and Coupa integration

Oracle JD Edwards EnterpriseOne runs procurement and finance across your supply chain. Coupa centralizes spend management and supplier collaboration in the cloud. Connecting the two keeps your supplier data, purchase orders, and accounts payable synchronized without manual re-entry. New suppliers in Oracle JD Edwards are available immediately in Coupa, purchase orders flow automatically, and invoice postings from Coupa update your AP ledger in real time.

How Oracle JD Edwards works

Oracle JD Edwards EnterpriseOne is deployed on-premises and exposes suppliers, purchase orders, and accounting ledgers through REST API via a customer-hosted AIS Server at a customer-provided URL. Authentication uses a session token obtained by sending username and password to the tokenrequest endpoint; the token remains valid for 30 to 60 minutes and is passed in the jde-AIS-Auth header on all subsequent requests. Key tables include the F0101 Address Book for vendors and customers, F0401 Supplier Master, F4301 and F4311 for purchase order header and detail, and F0411 for accounts payable ledger entries. Oracle JD Edwards has no native outbound webhooks, so data is retrieved by polling the data service tables with a date filter on the last-updated timestamp and tracking the last successful poll.

How Coupa works

Coupa is a cloud-based procurement platform that exposes suppliers, purchase orders, invoices, and payments through a REST API. Authentication uses OAuth 2.0 client credentials, and all requests carry an X-Coupa-API-Version header to pin the API contract. Coupa supports both pull and push: ml-connector can read existing suppliers and orders, and Coupa sends webhook events for requisitions, purchase orders, invoices, suppliers, and payments. Webhook signatures are verified via HMAC-SHA256, and Coupa enforces a rate limit with HTTP 429 responses and a 30-second request timeout.

What moves between them

Supplier master records flow from Oracle JD Edwards F0401 into Coupa Suppliers; purchase order headers and lines from F4301 and F4311 flow into Coupa PurchaseOrders; open and posted AP ledger entries from F0411 flow into Coupa Invoices. The direction is primarily Oracle JD Edwards to Coupa. Coupa webhook events for invoices and payments flow back to Oracle JD Edwards so that upstream cash applications and payment status updates can post to the F0411 AP ledger. Flows run on a polling schedule tied to your financial close calendar.

How ml-connector handles it

ml-connector stores the AIS Server URL and credentials encrypted. On each poll cycle, it obtains a new session token by sending the stored username and password to the jde-AIS-Auth tokenrequest endpoint, passing the token on all subsequent data service calls, and re-authenticating if a call returns HTTP 444. It reads suppliers, purchase orders, and AP entries using pagination via maxPageSize and the moreRecords flag, filtering by the UPMJ date-updated timestamp to retrieve only changed records since the last poll. Supplier IDs, GL account codes, and cost codes are mapped before posting to Coupa so that invoices land on the correct GL accounts. Coupa webhook events are received at a registered endpoint, verified against the HMAC-SHA256 signature in the webhook header, and applied to the Oracle JD Edwards F0411 AP ledger via named orchestration. Rate limit HTTP 429 responses from Coupa trigger exponential backoff with jitter, and every record carries a full audit trail so failed postings can be replayed once the downstream issue is resolved.

A real-world example

A mid-sized electronics distributor runs Oracle JD Edwards EnterpriseOne on-premises for procurement and general ledger accounting, and uses Coupa to manage supplier contracts and invoice approvals in the cloud. Before the integration, the procurement team exported supplier lists from Oracle JD Edwards weekly, uploaded them to Coupa by hand, received approved invoices from suppliers through Coupa, and forwarded them to accounts payable for manual entry into the GL. With Oracle JD Edwards and Coupa connected, supplier master data stays synchronized automatically, purchase orders created in Oracle JD Edwards are available immediately for matching in Coupa, and approved invoices flow directly to the AP ledger. The manual handoff steps are eliminated, and invoice discrepancies between the two systems are caught immediately.

What you can do

Sync supplier master records from Oracle JD Edwards F0401 to Coupa Suppliers, keeping both systems current with vendor information.
Pull purchase orders from Oracle JD Edwards F4301 and F4311 into Coupa PurchaseOrders for invoice matching and spend visibility.
Post accounts payable ledger entries from Oracle JD Edwards F0411 into Coupa Invoices, mapped to the correct cost codes and GL accounts.
Receive Coupa invoice and payment webhook events and apply them to the Oracle JD Edwards AP ledger via orchestration, closing the loop for cash reconciliation.
Handle Oracle JD Edwards session token refresh and Coupa OAuth 2.0 re-authentication, with retries on rate limits and a full audit trail on every record.

Questions

Which direction does data move between Oracle JD Edwards and Coupa?: The primary flow is from Oracle JD Edwards to Coupa: suppliers, purchase orders, and open invoices sync from Oracle JD Edwards into Coupa. Coupa webhook events for invoices and payments flow back to Oracle JD Edwards so that upstream approvals and cash applications can update the accounts payable ledger. This bi-directional flow keeps both systems in agreement without manual re-entry.
How does ml-connector handle Oracle JD Edwards on-premises deployment and token expiry?: Since Oracle JD Edwards AIS Server is deployed at customer infrastructure with no shared hostname, ml-connector accepts the full customer-provided AIS Server URL as a credential. Session tokens issued by Oracle JD Edwards are valid for 30 to 60 minutes; ml-connector stores the username and password encrypted, obtains a new token on each poll cycle, and re-authenticates immediately if a call returns HTTP 444 (invalid token). Token expiry never causes an outage because the token is refreshed before use.
What if Oracle JD Edwards supplier IDs or cost codes do not exist in Coupa?: ml-connector validates supplier IDs and cost codes against both systems before posting. A mismatch creates a failed record with a full audit trail, and the operator can correct the mapping in ml-connector's configuration or add the missing supplier or cost code to Coupa before replaying the failed batch. This prevents partial syncs and orphaned invoices.

Connect Oracle JD Edwards and Coupa

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started