Oracle Fusion Cloud ERP integration patterns: REST, BI Publisher and FBDI

When to use REST APIs, bulk FBDI file loads, BI Publisher extracts or Oracle Integration Cloud to move data in and out of Fusion Cloud ERP.

Fusion Cloud ERP gives you no database access, so every integration goes through one of four sanctioned doors. Choosing the wrong one is the usual reason a project misses its cutover window.

The four patterns

1. REST APIs — small, real-time, transactional

Best for single-record create/update, lookups and orchestration. Rate limits and per-call overhead make them unsuitable for six-figure row counts.

curl -u "$USER:$PASS" \
  -H 'Content-Type: application/json' \
  -X POST "https://$POD.fa.ocs.oraclecloud.com/fscmRestApi/resources/11.13.18.05/suppliers" \
  -d '{"Supplier":"Acme Ltd","TaxOrganizationTypeCode":"CORPORATION"}'

2. FBDI — bulk inbound

File-Based Data Import remains the workhorse for mass loads: fill the Oracle-provided CSV template, zip it, upload via the ERP Integration Service, then run the Load Interface File and the target import job. Everything is asynchronous, so build status polling and error-file retrieval into your process from day one.

3. BI Publisher reports — bulk outbound

A data model plus an eText/CSV/XML template turned into a scheduled extract, delivered to UCM, SFTP or fetched over the ERP Integration Service. This is how most downstream reporting and reconciliation feeds are built.

4. Oracle Integration Cloud (OIC) — orchestration

Adapters, mapping, error handling and scheduling in one place. Use it when several of the above must be chained, or when a non-Oracle system is on the other end.

Choosing quickly

Operational advice

• Create a dedicated integration user with only the required roles, and rotate credentials — do not reuse a named human account.
• Always capture the RequestId from asynchronous submissions; it is the only way to fetch the error log later.
• Test against a P2T-refreshed test pod; quarterly Oracle updates can change payloads, so re-run your regression suite each release.
• Design idempotency into inbound loads — duplicate FBDI submissions after a timeout are common.