Migrate your Oracle E-Business Suite data

Oracle GL stores multiple ledgers per legal entity with configurable segment structures. We extract the chart of accounts, journal batches, and period balances in standard EBS format. Ledger-level security rules are preserved as role mappings in the target system.

AP Supplier records include address book entries, bank accounts, payment terms, and site assignments. We map all supplier sites to the destination's vendor structure, preserving purchasing_assignments and remit-to hierarchies.

AR Customers are split across RA_CUSTOMERS, RA_ADDRESSES, and HZ_PARTIES. Sites, contacts, and profile classes are stored separately. We flatten these into the destination's account model and flag profile-level credit limits for manual review before go-live.

HRMS employee records span per_persons, per_assignments, and per_payment_methods. We extract assignment grades, supervisors, cost centers, and termination dates. Effective dates on assignments require chronological ordering during load to maintain correct seniority.

PO_HEADERS and PO_LINES with schedule distributions carry authorization status. We flag lines in APPROVED status as eligible for target load; DRAFT and REJECTED lines are excluded unless the customer requests otherwise. Line types and sourcing rules require value mapping.

AP_INVOICES_ALL and AR_INVOICES_ALL store invoice headers and lines separately. We extract balance-owing amounts and hold statuses, mapping payment terms to the destination's calendar-based due-date engine. Invoices on internal holds must be released before migration or carried as open in the target.

MST_ORGANIZATIONS defines org structure; MTL_SYSTEM_ITEMS_B defines the item master with organization-specific on-hand quantities. Subinventory assignments and locator hierarchies require careful mapping because EBS locators are often user-defined and destination locators may follow a different naming convention.

BOM_STRUCTURES_B and BOM_ROUTINGS_B store multi-level BOMs and routing sequences. The explode/implode relationship between levels must be preserved in the correct topological order during load, or the destination will reject component associations on phantom assemblies.

WIP_JOB_SCHEDULE_SCHEDULES stores discrete and process work orders with status codes. Open and released WIP jobs require material allocations and routing step sequencing. Closed and cancelled jobs are archived rather than migrated to avoid cluttering the target ERP.

PA_PROJECTS_ALL and PA_EXPENDITURES store project headers and costed transaction lines. Resource breakdown structures and billing rates require cross-module mapping to the target's project costing engine.

Oracle EBS stores custom fields in XX_ prefix tables and extended attributes on standard tables (FND_DESCRIPTIVE_FLEXS). There is no standard export mechanism for these. We document the table names and column definitions during discovery so the customer can build a separate extraction job; FlitStack AI does not migrate custom objects as part of the standard migration.

FND_ATTACHED_DOCUMENTS and FND_LOBS store files associated with entities across modules. We extract the binary blobs or file paths and map them to the destination's document management linkage table. Large attachments (over 10 MB) may require separate file-transfer handling.

CE_BANK_ACCOUNTS and CE_PAYMENT_DOCUMENTS store bank accounts and associated payment format templates. Bank account numbers and SWIFT codes are migrated but payment format remittance layouts require reconfiguration in the target ERP.