Oracle EBS to Fusion Cloud Migration: API Changes, Data, and Coexistence

TL;DR

• Bottom line: Migrating from Oracle EBS to Fusion Cloud requires replacing PL/SQL-based integrations with REST APIs, FBDI for bulk data, and Oracle Integration Cloud (OIC) for orchestration — there is no in-place upgrade path.
• Key limit: Fusion Cloud has no direct database access; all data operations must go through REST (max 500 records/POST), SOAP, or FBDI (max 250 MB ZIP, max 5 concurrent imports).
• Watch out for: Custom PL/SQL procedures, open interface tables, and concurrent programs have no direct equivalents in Fusion — each must be redesigned.
• Best for: Organizations on EBS 12.2 planning a phased or big-bang move to Oracle Cloud ERP with 12-36 month timeline.
• Authentication: Fusion Cloud uses OAuth 2.0 (JWT bearer for server-to-server) or SAML/IDCS; EBS ISG uses username/password or token-based auth through SOA Gateway.

System Profile

This card covers the technical migration path from Oracle E-Business Suite 12.2 (on-premise, all editions) to Oracle Fusion Cloud ERP (Release 24B/25A). It addresses the API surface changes, data migration methods, integration middleware options, and coexistence architecture during the transition period.

API Surfaces & Capabilities

The fundamental API shift from EBS to Fusion Cloud is the elimination of direct database access. In EBS, integrations commonly used PL/SQL procedures, open interface tables, and concurrent programs. None of these are available in Fusion Cloud.

Rate Limits & Quotas

Per-Request Limits

Rolling / Daily Limits

Authentication

Authentication Gotchas

• EBS ISG must have SOA Gateway configured and specific services deployed before OIC EBS Adapter can connect [src4]
• Fusion Cloud OAuth tokens are scoped to the integration user’s role — ensure the integration user has all required data roles [src1]
• OIC Connectivity Agent must run on an on-premise VM or OCI compute to bridge EBS with cloud [src4]

Constraints

• No direct SQL access to Fusion Cloud database — all PL/SQL, open interface tables, and custom SQL must be redesigned
• FBDI templates are fixed and cannot be modified — map data to Oracle’s predefined column structure
• Concurrent Programs do not exist in Fusion Cloud — replace with ESS scheduled processes or BIP reports
• Custom Forms (Oracle Forms) have no equivalent — redesign using VBCS or REST API integrations
• Data migration requires full data cleansing before import — Fusion Cloud enforces stricter validation
• EBS flexfield structures may not map 1:1 to Fusion Cloud extensible flexfields

Integration Pattern Decision Tree

START — Migrating from Oracle EBS to Fusion Cloud
├── What needs to migrate?
│   ├── Master Data (customers, suppliers, items, COA)
│   │   ├── Volume < 100K → FBDI (single batch per entity)
│   │   ├── Volume > 100K → FBDI with chunking (split into 100K batches)
│   │   └── Ongoing sync needed? → OIC with EBS Adapter (event-driven or scheduled)
│   ├── Open Transactions (POs, invoices, journals)
│   │   ├── Convert in-flight? → Complete in EBS first, migrate as history
│   │   └── Historical data? → FBDI for balances, BIP extract for detail
│   ├── Integrations (with external systems)
│   │   ├── EBS PL/SQL interface → Redesign to Fusion REST API + OIC
│   │   ├── EBS Open Interface Tables → Redesign to FBDI or REST API
│   │   ├── Concurrent Programs → Redesign to ESS Jobs or BIP reports
│   │   └── Custom Forms → Redesign to VBCS pages or REST API
│   └── Custom Reports → Redesign to OTBI, BIP, or FDI
├── Coexistence needed?
│   ├── YES → See oracle-erp-cloud-coexistence-patterns/2026
│   └── NO → Big-bang cutover with parallel run
└── Timeline?
    ├── < 12 months → Focus on core modules, defer customizations
    ├── 12-24 months → Standard phased approach
    └── > 24 months → Module-by-module coexistence

Quick Reference

EBS to Fusion Cloud API Mapping

Step-by-Step Integration Guide

1. Assess EBS Environment and Catalog Integrations

Document all active integrations, customizations, and data volumes. [src5]

-- Query active ISG integrations
SELECT service_name, service_type, direction, status
FROM fnd_soa_services
WHERE status = 'DEPLOYED'
ORDER BY service_type;

Verify: Every integration has a Fusion Cloud replacement method assigned in inventory spreadsheet.

2. Configure Fusion Cloud Integration User and OAuth

Create dedicated integration user with appropriate data roles, set up IDCS OAuth application. [src1]

curl -X POST "https://<idcs-url>/oauth2/v1/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials&scope=urn:opc:resource:consumer::all" \
  -u "<client_id>:<client_secret>"

Verify: GET /fscmRestApi/resources/latest/ledgers returns your chart of accounts.

3. Migrate Master Data via FBDI

Extract from EBS, transform to FBDI format, upload to UCM, trigger import. [src2]

import requests, base64
FUSION_URL = "https://<pod>.fa.us2.oraclecloud.com"
# Upload FBDI ZIP then trigger importBulkData
resp = requests.post(
    f"{FUSION_URL}/fscmRestApi/resources/latest/erpintegrations",
    json={"OperationName": "importBulkData", "DocumentId": doc_id,
          "JobName": "/oracle/apps/ess/.../SupplierImportJob"},
    headers=headers)

Verify: ESS job status shows SUCCEEDED.

4. Set Up OIC for Coexistence Sync

Configure OIC with EBS Adapter (on-premise via connectivity agent) and ERP Cloud Adapter for bidirectional data flow. [src4]

Verify: Test end-to-end flow with a single record — verify record appears in both systems.

Code Examples

Python: Bulk Supplier Migration via FBDI

# Input:  EBS supplier extract (CSV)
# Output: FBDI-formatted ZIP ready for Fusion import

import csv, zipfile, io

def transform_ebs_to_fbdi(ebs_csv_path, fbdi_output_path):
    COLUMN_MAP = {
        "VENDOR_NAME": "Supplier",
        "VENDOR_TYPE_LOOKUP_CODE": "SupplierType",
        "SEGMENT1": "SupplierNumber",
    }
    rows = []
    with open(ebs_csv_path, "r") as f:
        for row in csv.DictReader(f):
            rows.append({v: row.get(k, "") for k, v in COLUMN_MAP.items()})
    buf = io.StringIO()
    writer = csv.DictWriter(buf, fieldnames=list(COLUMN_MAP.values()))
    writer.writeheader()
    writer.writerows(rows)
    with zipfile.ZipFile(fbdi_output_path, "w", zipfile.ZIP_DEFLATED) as zf:
        zf.writestr("PozsupplierInt.csv", buf.getvalue())
    print(f"Created FBDI ZIP with {len(rows)} suppliers")

cURL: Test Fusion Cloud REST API Connectivity

# Get OAuth token and test API
TOKEN=$(curl -s -X POST "https://<idcs-url>/oauth2/v1/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "grant_type=client_credentials&scope=urn:opc:resource:consumer::all" \
  -u "<client_id>:<client_secret>" | jq -r '.access_token')

curl -s "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/businessUnits" \
  -H "Authorization: Bearer $TOKEN" | jq '.items[].BusinessUnitName'

Data Mapping

Field Mapping Reference (Suppliers)

Data Type Gotchas

• EBS stores amounts in ledger currency with explicit exchange rates; Fusion Cloud uses centrally managed exchange rates [src1]
• EBS flexfield segments must be mapped to Fusion extensible flexfield contexts — fundamentally different structure [src1]
• EBS date fields use database server timezone; Fusion REST API returns dates in UTC [src2]

Error Handling & Failure Points

Common Error Codes

Failure Points in Production

• FBDI partial success is silent: Jobs may succeed at job level but reject rows. Fix: Always check ESS output file for row-level errors. [src2]
• OIC Connectivity Agent disconnects: Agent loses connection during network maintenance. Fix: Deploy agent in HA mode with 2+ instances. [src4]
• Character encoding mismatch: EBS uses WE8MSWIN1252; Fusion uses AL32UTF8. Fix: Convert all data to UTF-8 before FBDI generation. [src5]
• EBS sequence gaps: Database sequence gaps after migration cause confusion. Fix: Reset Fusion sequences to start after max EBS value + buffer. [src5]

Anti-Patterns

Wrong: Using REST API for bulk data migration

# BAD — REST API limited to 500 records per POST
for supplier in all_suppliers:  # 50,000 suppliers
    requests.post(f"{FUSION_URL}/.../suppliers", json=supplier, headers=headers)
    # Takes hours with 50,000 individual API calls

Correct: Use FBDI for bulk data, REST for real-time only

# GOOD — FBDI handles up to 100,000 records per batch
create_fbdi_zip(all_suppliers, "SupplierImport.zip")  # Single file
upload_and_import(zip_path="SupplierImport.zip")       # Minutes not hours

Wrong: Replicating EBS PL/SQL logic in Fusion Cloud

-- BAD — No direct database access in Fusion Cloud
BEGIN
  INSERT INTO po_headers_interface (...) VALUES (...);
  COMMIT;
END;
-- This does NOT work in Fusion Cloud

Correct: Use Fusion Cloud REST API

# GOOD — Use REST API for PO creation
requests.post(f"{FUSION_URL}/.../purchaseOrders",
              json=po_payload, headers=headers)

Common Pitfalls

• Underestimating integration redesign: Every PL/SQL-based integration must be redesigned — budget 40-60% of total effort. Fix: Catalog every integration point; estimate 2-4 weeks per complex integration. [src1]
• FBDI template versioning: Templates change with each quarterly update. Fix: Download fresh templates from the target environment before each run. [src2]
• Not testing with production volumes: 1,000-record tests don’t reveal bulk import issues. Fix: Test with production-scale data in non-production pod. [src2]
• Assuming same security model: EBS responsibilities vs Fusion roles + data roles — fundamentally different. Fix: Map EBS responsibilities to Fusion roles early. [src5]

Diagnostic Commands

# Check Fusion Cloud REST API availability
curl -s -o /dev/null -w "%{http_code}" \
  "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/" \
  -H "Authorization: Bearer $TOKEN"
# Expected: 200

# Check FBDI import job status
curl -s "https://<pod>.fa.us2.oraclecloud.com/fscmRestApi/resources/latest/erpintegrations?finder=ESSJobStatusRF;requestId=<REQ_ID>" \
  -H "Authorization: Bearer $TOKEN" | jq '.items[0].RequestStatus'

# Verify OIC Agent connectivity
curl -s "https://<oic-url>/ic/api/integration/v1/monitoring/agents" \
  -H "Authorization: Bearer $OIC_TOKEN" | jq '.items[].status'
# Expected: "CONNECTED"

Version History & Compatibility

When to Use / When Not to Use

Important Caveats

• EBS 12.2 Premier Support extended through at least 2035 — no forced migration deadline, but new features are cloud-only
• Migration timelines vary: lightly customized EBS 12-18 months; heavily customized 24-36 months
• Fusion Cloud is multi-tenant SaaS — performance differs from dedicated on-premise EBS databases
• FBDI templates and REST API endpoints change every quarter — test after each update
• Oracle and third-party accelerators can reduce effort by 30-40% but do not eliminate integration redesign