Oracle E-Business Suite and Orderful integration

What moves between them

The flow runs bidirectionally. Purchase orders created in Oracle EBS are read by ml-connector, translated into EDI 850 purchase order documents, and sent to Orderful with the correct ISA identifiers and stream setting. Orderful distributes the 850s to suppliers via your chosen channels. When suppliers respond, Orderful receives EDI 855 acknowledgments and 810 invoices, which ml-connector converts back into Oracle EBS purchase order update records and AP invoice interface records. The acknowledgments update PO line statuses in EBS, and the invoices create AP_INVOICES_INTERFACE records that the EBS concurrent program imports into AP_INVOICES_ALL.

How ml-connector handles it

ml-connector stores the Oracle EBS ISG hostname, port, and authentication credentials (username, password) encrypted, and uses HTTP Basic Auth to obtain a session token on first request, then stores the token until it expires (typically 30-60 minutes) or returns 401, at which point ml-connector refreshes it. The Orderful API key is also stored encrypted and injected into the orderful-api-key header on every request. ml-connector reads open purchase order records and lines from Oracle EBS on a schedule (e.g., hourly or per procurement cycle), translates them to EDI 850 format with line items, quantities, and requested delivery dates, then POSTs them to Orderful /v4/inbox with the correct ISA identifiers (sender.isaId for EBS, receiver.isaId for the supplier) and stream set to live. On the inbound side, ml-connector either accepts Orderful webhooks via a public HTTP endpoint (preferred) or polls the Orderful /v3/polling-buckets endpoint every 5-10 minutes. Received 855 acknowledgments are parsed and mapped back to EBS PO line numbers and statuses, updating the purchase order confirmation status. Received 810 invoices are parsed, mapped to the original EBS PO, cost center, and GL account, then inserted into AP_INVOICES_INTERFACE with invoice number, amount, and line detail, flagging them for concurrent program import. The entire transaction carries an audit trail with source document IDs, translation errors, and replay capability if a downstream import fails.

A real-world example

A mid-sized manufacturing distributor runs Oracle EBS for procurement and GL, and uses Orderful to manage EDI with 80 regional suppliers via AS2 and SFTP. Before the integration, the procurement team manually exported POs from EBS as CSV, converted them to EDI 850 format using a third-party tool, uploaded them to Orderful, then received supplier 855 confirmations and 810 invoices back from Orderful and re-entered them into EBS by hand, a process that took 4-6 hours per day and introduced manual entry errors. With Oracle EBS and Orderful connected, new POs automatically flow to Orderful as EDI 850s, supplier acknowledgments and invoices flow back automatically as EBS PO updates and AP invoices, and the procurement team focuses on exception handling instead of data entry.

What you can do

• •Create EDI 850 purchase order documents from Oracle EBS purchase orders and send them to Orderful with the correct ISA identifiers and stream settings.
• •Receive EDI 855 purchase order acknowledgments from Orderful and update purchase order line statuses in Oracle EBS.
• •Convert EDI 810 supplier invoices from Orderful into AP invoice interface records in Oracle EBS, mapped to the original PO, cost center, and GL account.
• •Handle Oracle EBS session token refresh on 401, Orderful API key injection, and both webhook and polling ingestion modes from Orderful.
• •Maintain a complete audit trail of all EDI translations and mappings, with replay capability if an EBS import fails.

Questions

How does ml-connector handle Oracle EBS session token expiry?

ml-connector obtains an EBS session token on first request using HTTP Basic Auth against the ISG login endpoint, and stores it until expiry (typically 30-60 minutes) or a request returns 401. When the token expires, ml-connector re-authenticates and retrieves a new token automatically on the next request, so the integration never stalls due to token age.

Can ml-connector receive EDI documents from Orderful via webhook, or does it have to poll?

ml-connector supports both. Orderful can POST incoming EDI documents to a public HTTP endpoint you expose, and ml-connector accepts them and returns 200 to confirm receipt. Alternatively, if a public endpoint is not available, ml-connector polls the Orderful /v3/polling-buckets endpoint every 5-10 minutes to retrieve up to 100 documents per request. Webhooks are faster and more responsive; polling is the fallback for restricted network topologies.

What happens when a supplier sends an EDI 810 invoice through Orderful?

ml-connector receives the 810 from Orderful (via webhook or polling), parses the sender, receiver, invoice number, line items, and amounts, maps the invoice back to the original Oracle EBS purchase order by PO number, retrieves the cost center and GL account from the PO, then inserts a record into AP_INVOICES_INTERFACE with all required fields. The EBS concurrent program then imports it into AP_INVOICES_ALL, and the invoice appears in your AP workbench linked to the original PO.