Oracle Fusion Cloud ERP and Orderful integration

What moves between them

The primary flow moves purchase orders from Oracle Fusion into Orderful. When a purchase order is created or modified in Oracle Fusion, ml-connector polls the REST API, extracts the order details (supplier DUNS, items, quantities, prices), and creates a new 850 Purchase Order EDI document in Orderful with the correct sender and receiver ISA identifiers (ISA Id) and stream set to live. Inbound documents flow the opposite direction: ml-connector polls Orderful for 855 Purchase Order Acknowledgments and 810 Invoices, translates them from EDI to Oracle Fusion purchase order receipt and supplier invoice records, and inserts them into Oracle Fusion. This two-way polling keeps both systems in sync without real-time webhooks.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the Oracle Fusion OAuth 2.0 client ID and secret (for JWT bearer token generation) and the Orderful API Key. On the Oracle Fusion side, it accepts the customer-specific pod URL and polls the REST API endpoint with OData filters (e.g., ?q=LastUpdateDate>=2024-01-01T00:00:00Z) to retrieve only new and changed purchase orders. It translates each Oracle Fusion purchase order into the Orderful 850 EDI structure, extracting the supplier DUNS number from Oracle Fusion supplier records to populate the Orderful sender.isaId and receiver.isaId fields. On the Orderful side, ml-connector polls the polling-buckets endpoint every 5 to 10 minutes, retrieves up to 100 inbound EDI documents per request, parses 855 acknowledgments and 810 invoices, and translates them back into Oracle Fusion purchase order receipt and supplier invoice records. Since Oracle Fusion has no outbound webhooks for external use, polling is the only option; ml-connector tracks the last poll timestamp to avoid duplicates and stores the Orderful transaction Id in the Oracle Fusion source system reference field for traceability. Retries on timeouts or rate limits use exponential backoff, and every record carries a full audit trail showing the original EDI, the translation, and the Oracle Fusion record it created.

A real-world example

A mid-sized manufacturing and distribution company uses Oracle Fusion Cloud ERP for procurement and finance across three warehouses and uses Orderful to translate and deliver orders to a network of hundreds of suppliers via EDI. Before the integration, the procurement team created purchase orders in Oracle Fusion, manually exported them as spreadsheets or CSV files, then logged into Orderful to re-enter each order as a new 850 document. Inbound supplier acknowledgments arrived in Orderful but were not automatically matched to the original orders in Oracle Fusion, causing reconciliation delays and inventory visibility gaps. After connecting Oracle Fusion and Orderful, purchase orders flow directly from Oracle Fusion into Orderful without manual entry, suppliers receive X12 EDI within minutes, and acknowledgments and invoices automatically post back into Oracle Fusion as receipts and payables. Month-end reconciliation now takes hours instead of days, and the procurement team focuses on exceptions instead of data entry.

What you can do

• •Automatically translate purchase orders from Oracle Fusion to X12 or EDIFACT EDI and deliver them through Orderful to suppliers.
• •Retrieve inbound 855 Purchase Order Acknowledgments and 810 Invoices from Orderful and post them as purchase order receipts and supplier invoices in Oracle Fusion.
• •Map Oracle Fusion supplier DUNS numbers to Orderful ISA identifiers so orders route to the correct trading partners.
• •Poll both Oracle Fusion and Orderful on a schedule you control, with exponential backoff retries and a complete audit trail on every record.
• •Track every EDI document, translation, and Oracle Fusion record created, so you can replay a failed sync or debug a mismatch in minutes.

Questions

Why does ml-connector poll instead of using Oracle Fusion webhooks?

Oracle Fusion Business Events can push events only to Oracle Integration Cloud (OIC) middleware, not directly to external URLs. ml-connector uses the REST API polling pattern recommended by Oracle, filtering by LastUpdateDate every 5 to 15 minutes to capture new and changed purchase orders without requiring an additional Oracle license or middleware platform.

How does ml-connector match inbound Orderful EDI documents to the original Oracle Fusion purchase orders?

ml-connector stores the Orderful transaction Id in the Oracle Fusion source system reference field on each purchase order receipt or invoice it creates. When a new 855 acknowledgment or 810 invoice arrives from Orderful, ml-connector uses the sender and receiver ISA identifiers to determine which supplier sent it, then matches it to the corresponding Oracle Fusion purchase order and supplier master record by supplier DUNS number.

What happens if Oracle Fusion or Orderful is unavailable during a poll cycle?

ml-connector backs off with exponential jitter and retries up to a configurable limit (typically 2-3 retries) before surfacing the failure to the audit log and alerting the integration owner. The next poll cycle will retry from where the previous cycle left off, ensuring no records are skipped or duplicated. Every transaction is idempotent by Orderful transaction Id, so a replayed sync is safe.