Oracle E-Business Suite → Oracle Fusion Cloud Financials

EBS and Fusion share a lineage but not a data model — the chart of accounts, ledgers, and subledger structures need deliberate mapping. Balances must reconcile to the cent and the audit trail must survive, or period close and reporting break. This transfer maps the COA and subledgers and reconciles every balance before and after cutover.

Free reference snippet

Yours to use

A working piece from this integration — no sign-up. The full build handles the edge cases, safeguards, and cutover.

Oracle EBS Column	Fusion Cloud API Field	Notes
`VENDOR_NAME`	`vendorName`	Required
`VENDOR_TYPE_LOOKUP_CODE`	`vendorType`	Supplier, Contractor
`SEGMENT1`	`taxRegistrationNumber`	Tax ID / RFC
`PAYMENT_TERMS_LOOKUP_CODE`	`defaultPaymentTermsCode`	Net 30, Net 60
`VENDOR_SITE_CODE`	`SupplierSite[0].siteName`	Site level
`ADDRESS_LINE1 + CITY`	`SupplierSite[0].addressLine1`	Concatenate
`COUNTY + STATE + POSTAL_CODE`	`SupplierSite[0].postalCode`	Mapped in address
`ORG_ID`	`buId`	Business Unit ID

Fusion REST call for supplier creation:

/* POST /fscmRestApi/resources/11.13.18.05/suppliers */
{
  "vendorName": "ACME Supplies Inc",
  "vendorType": "Supplier",
  "taxRegistrationNumber": "12-3456789",
  "defaultPaymentTermsCode": "Net 30",
  "buId": 30000000184952,
  "SupplierSite": [{
    "siteName": "PRIMARY",
    "addressLine1": "123 Main St, Chicago",
    "country": "US",
    "primaryPaySite": true
  }]
}

Implementation pathway

Step by step

How we'd take this from discovery to a production-safe cutover — the phases, the canonical mapping, and the edge cases that bite.

This implementation pathway governs a one-time transfer of core financial master data and balances from Oracle E-Business Suite R12 into Oracle Fusion Cloud Financials. The scope encompasses the general ledger structure, chart of accounts segments, supplier records, and open AP/AR/PO transactions. The approach uses Oracle's recommended FBDI (File-Based Data Import) templates and REST APIs, with a parallel extraction strategy to minimize production cutover windows.

Implementation Phases

Source Environment Assessment (Weeks 1–2). Run diagnostic queries against GL_CODE_COMBINATIONS, GL_BALANCES, GL_PERIOD_STATUS, PO_VENDORS, AP_INVOICES_ALL, and AR_CUSTOMER_TRX_ALL to capture record counts, orphaned combinations, and period-open statuses. Export the current EBS ledger structure and posting date ranges. Validate that the target Fusion ledger has been provisioned with the same accounting calendar and currency.
Chart of Accounts Mapping (Weeks 2–4). Extract all active rows from GL_CODE_COMBINATIONS where summary_flag = 'N'. Map EBS segment values to Fusion value sets using the GL# FBDI template. Reconcile total debit and credit balances by natural account to the EBS GL_BALANCES table at the target migration date. Preserve the code_combination_id as a custom identifier in the External Reference field of Fusion's Accounting Combination object.
Supplier Master Extraction and Transformation (Weeks 3–5). Pull PO_VENDORS joined to PO_VENDOR_SITES_ALL, filtering on VENDOR_NAME, SEGMENT1 (vendor number), and VNDR_LOCATIONS. Map to the SUPP FBDI template, ensuring TAX_REPORTING_FLAG and PAYMENT_METHOD_LOOKUP_CODE are populated. For tax registration numbers, map PO_VENDOR_SITES_ALL.TAX_REFERENCE to the Tax Registration Number field. Stage in Oracle Integration Cloud or a secure file share.
Open Transaction Extraction (Weeks 4–6). Identify open invoices from AP_INVOICES_ALL where PAYMENT_STATUS_FLAG = 'N' and CANCELLED_DATE IS NULL. Pull associated lines from AP_INVOICE_DISTRIBUTIONS_ALL and map to Fusion's APIN (AP Invoices) FBDI template. For open PO receipts awaiting invoicing, extract RCV_SHIPMENT_HEADERS and RCV_TRANSACTIONS. Extract open AR transactions from AR_CUSTOMER_TRX_ALL with STATUS = 'OP'.
FBDI Template Population and Pre-Validation (Weeks 5–7). Populate all FBDI templates with transformed data. Run Oracle's provided spreadsheet validations for each template (GL#, SUPP, APIN, ARIN). Validate accounting date ranges against the target Fusion accounting calendar (FUSION_LEDGER.CALENDAR_CODE). Run referential integrity checks: confirm every CODE_COMBINATION_ID in transaction lines has a corresponding chart-of-accounts entry loaded in Phase 2.
Sandbox Load and Reconciliation (Weeks 6–8). Load all FBDI files into a non-production Fusion environment via the /fscmRestApi/resources/11.13.18.05 import job endpoints. Execute the import process for each template sequentially: Chart of Accounts first, then Ledgers, then Suppliers, then Transactions. Compare EBS source totals (GL_BALANCES by account type, AP_INVOICES sum by vendor) against Fusion reported totals. Log all discrepancies in a shared tracking sheet.
Data Cleansing and Retry Cycles (Weeks 7–9). Address validation failures identified in Phase 6. Common issues include invalid supplier site assignments, duplicate vendor numbers, and accounting flexfield segments exceeding value set lengths. Re-export corrected data from EBS, transform, and reload. Repeat until reconciliation variance is zero at the account level.
Production Cutover Preparation (Week 9–10). Freeze EBS source data: close all open periods at the operating unit level using GL_PERIOD_CLOSE_API.CLOSE_FIRST_OPEN_PERIOD. Perform a final incremental extraction of any transactions entered after the initial extraction timestamp. Lock EBS interfaces to prevent new transaction creation during the delta load window.
Final Load, Validation, and Go-Live (Week 10–11). Load the final delta FBDI package into Fusion production. Execute post-load journal import for GL balances to establish opening balances. Run the ValidateBalances ESS job in Fusion. Confirm that trial balance in Fusion matches the EBS closing trial balance to the penny. Enable Fusion transaction entry and disable EBS modules.

Field Mapping

EBS Source Object	EBS Identifier	Fusion Target Object	Fusion Identifier	Notes
Chart of Accounts	`GL_CODE_COMBINATIONS.SEGMENT1–N`	Accounting Combination	`FBDI: GL# Account Combination Segment Value`	Map each EBS segment to a Fusion value set; preserve `CODE_COMBINATION_ID` in `External Reference`
GL Balances	`GL_BALANCES.ENTERED_DR`, `ENTERED_CR`, `TRANSLATED_FLAG`	GL Interface / Opening Balances Import	`FBDI: GL# Period Balance`	Load as opening journal entries; debits must equal credits at the ledger level
Supplier Master	`PO_VENDORS.SEGMENT1` (vendor number)	Supplier	`FBDI: SUPP Supplier Number`	Vendor number must be unique; map inactive vendors to `Status = INACTIVE`
Supplier Site	`PO_VENDOR_SITES_ALL.VENDOR_SITE_CODE`	Supplier Site	`FBDI: SUPP Supplier Site Code`	Ensure `ORG_ID` maps to the correct Fusion Business Unit
AP Invoice Header	`AP_INVOICES_ALL.INVOICE_NUM`, `INVOICE_AMOUNT`	AP Invoice	`FBDI: APIN Invoice Number, Invoice Amount`	Only open invoices (`PAYMENT_STATUS_FLAG = 'N'`); map `INVOICE_DATE` to `Invoice Date`
AP Invoice Distribution	`AP_INVOICE_DISTRIBUTIONS_ALL.DIST_CODE_COMBINATION_ID`	AP Invoice Lines	`FBDI: APIN Account Combination`	Join to `GL_CODE_COMBINATIONS` to resolve segment values; must exist in Fusion prior to invoice load
AR Transaction	`AR_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID`, `TRX_NUMBER`	AR Invoice	`FBDI: ARIN Transaction Number`	Filter on `STATUS_CODE = 'OP'`; map `PRIMARYSalesrep_ID` to Fusion resource ID
Ledger Setup	`GL_LEDGERS.LEDGER_ID`, `NAME`	Ledger	`FBDI: LEDGER Primary Ledger Name`	Ledger must be provisioned in Fusion before any data load; match `LEDGER_ID` to `Source Ledger ID`

Edge Cases

Orphaned account combinations. Combinations in GL_CODE_COMBINATIONS with no balances and no transactions will fail Fusion validation if value set lengths differ. Filter to combinations referenced by GL_BALANCES or AP_INVOICE_DISTRIBUTIONS_ALL before loading.
Duplicate supplier numbers. EBS allows duplicate SEGMENT1 values across operating units. Fusion requires unique supplier numbers per enterprise. De-duplicate by selecting the most recent VENDOR_ID or merging sites under one supplier record.
Foreign-currency open transactions. Invoices in non-functional currencies require EXCHANGE_RATE and EXCHANGE_RATE_TYPE populated in the FBDI. Missing rates from GL_DAILY_RATES will cause import rejection.
Locked or closed periods. If any source period in EBS is already closed and locked via GL_PERIOD_CLOSE_API, the corresponding Fusion period must be closed or in "Never Opened" status before opening-balance journals can post. Mismatched period status causes journal rejection error JRNL_INVALID_PERIOD.
Multi-org EBS structures. Transactions tied to specific ORG_ID values must map to the correct Fusion Business Unit. Failing to join AP_INVOICES_ALL.ORG_ID to the appropriate HZ_PARTIES site will orphan supplier-site assignments.
Tax registration format mismatches. EBS stores tax IDs with dashes or prefixes; Fusion validates against country-specific formats. Attempting to load a US EIN in the wrong format triggers TAX_REG_NUMBER_INVALID.
Chart-of-accounts segment count divergence. EBS may use 6 segments where Fusion is configured for 4. Segments beyond the Fusion structure must be concatenated into a single segment value using a delimiter or mapping table during transformation.

Cutover

Cutover must be executed within a single maintenance window with a verified rollback path. Prior to the final load, export the complete EBS dataset as immutable snapshot files stored in Oracle Object Storage or an encrypted on-premise repository. At cutover, execute the delta FBDI load first (transactions dated after the initial extraction), then run the opening-balance journal import for all prior periods. Immediately after loading, execute the Fusion ValidateBalances ESS job and compare the output trial balance to the EBS closing trial balance by account type and currency. If variance exceeds zero at any level, halt transaction entry in Fusion and reload corrected data from the snapshot. Once balance reconciliation passes, lock the EBS database using FND_USER disablement and CONCURRENT_PRIORITY locks on关键的并发请求类型, then enable Fusion transaction entry. Retain the EBS read-only environment for 90 days post-cutover to support audit inquiries. Schedule a 30-day post-go-live reconciliation comparing weekly transaction counts and cumulative balances between systems until the audit trail is fully validated in Fusion.

What a full implementation includes

Canonical mapping between Oracle E-Business Suite and Oracle Fusion Cloud Financials, to the field level.
The edge cases that corrupt data at cutover — identified, handled, and tested.
Production-safe rollout: reversible, phased, with reconciliation checks.
Handover documentation your team can operate from.