Migrate from Oracle E-Business Suite to Odoo ERP

Oracle GL stores multiple ledgers per legal entity with configurable segment structures across GL_CODE_COMBINATIONS and GL_IMPORT_REFERENCES. We extract the chart of accounts, journal batches, and period balances in standard EBS format. Ledger-level security segments map to Odoo's account groups and analytic accounts. Open period balances migrate with GL_PERIOD_STATUSES respected; closed periods migrate as read-only entries with a flag preventing post-migration modification in Odoo. The Oracle FND_FLEX_VALUES hierarchies for natural account segments require mapping to Odoo's account type and code structure before the account master loads.

AP Supplier records (PO_VENDORS, PO_VENDOR_SITES_ALL) include address book entries, bank accounts, payment terms, and site assignments. Oracle stores supplier sites separately with purchasing_assignments per site. We flatten the site hierarchy into Odoo's vendor model, preserving vendor credit limits, payment terms, and bank account SWIFT codes. Sites with different purchasing or payment configurations become separate vendor addresses in Odoo rather than separate vendor records. Oracle supplier classifications migrate as vendor tags.

Oracle AR Customers are split across RA_CUSTOMERS, RA_ADDRESSES, and HZ_PARTIES. Sites, contacts, and profile classes are stored as separate entities with party-level parent records in HZ_PARTIES. We flatten these into Odoo's partner model with the company flag set and contact sub-records for individual contacts. Oracle profile classes (credit limits, payment terms, dunning plans) map to Odoo's internal notes and custom fields. Any duplicate party records detected during the HZ_PARTIES scan are flagged for customer review before load.

Oracle HRMS employee records span PER_ALL_ASSIGNMENTS_F and PER_PERSONS with effective dates controlling assignment visibility. We extract assignment grades, supervisors, cost centers, and termination dates. Oracle's effective date model means the same employee may have multiple assignment rows over time; we extract the current active assignment for Odoo and archive historical assignments as a related record. Bank account details for payroll migrate to Odoo's employee bank account fields only if the payroll module is activated.

PO_HEADERS_ALL and PO_LINES_ALL carry authorization status and distribution amounts. We flag lines in APPROVED status as eligible for target load; DRAFT, REJECTED, and CANCELLED lines are excluded unless the customer explicitly requests otherwise. Oracle PO schedule distributions map to Odoo purchase order lines with shipment dates and quantities. Pre-approve purchase order configuration in Odoo must be set before import to avoid blocking approved Oracle records with an Odoo approval workflow.

AP_INVOICES_ALL and AR_INVOICES_ALL store invoice headers and lines separately with hold statuses and payment terms. We extract balance-owing amounts and hold statuses, mapping Oracle payment terms (derived from IBY_PAYMENT_TERMS) to Odoo's term definitions. Open invoices (not fully paid) migrate with their remaining balance; paid invoices migrate as reconciled entries with payment registers. Oracle's multiple invoice distributions per line (accrual versus cash) must be consolidated into Odoo's single-line-per-account model, which may require the customer to decide on the primary allocation account.

MST_ORGANIZATIONS defines the org structure; MTL_SYSTEM_ITEMS_B defines the item master with organization-specific on-hand quantities. Subinventory assignments and locator hierarchies require careful mapping to Odoo's warehouse and location model. Oracle inventory organizations represent separate legal entities or costing entities in some deployments; we evaluate each org's role during discovery and decide whether it maps to an Odoo warehouse, a Odoo company, or a warehouse within a multi-company configuration.

MTL_SYSTEM_ITEMS_B stores item definitions across inventory organizations. We consolidate item masters into Odoo product records with organization-specific quantities loaded as warehouse stock quant records. Oracle item templates, category structures, and template assignments map to Odoo's product categories and product templates. Supply vs demand item flags, lot and serial number controls, and shelf-life settings migrate as product configuration fields.

BOM_STRUCTURES_B and BOM_ROUTINGS_B store multi-level BOMs and routing sequences. The explode/implode relationship between BOM levels must be preserved in the correct topological order during load. Odoo's BoM model requires parent product reference, component lines with quantities and bom line type (make_to_order or phantom), and routing operations with work center assignment. Oracle routing operations with parallel paths and alternate resources require flattening or explicit Odoo work center group assignment during mapping. Engineering change orders (ECOs) linked to BOMs are documented for manual review.

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. Oracle's WIP move transactions and resource charges map to Odoo's work order operations and byproducts. Closed and cancelled jobs are excluded from migration unless the customer requests historical closure records. Work order costing from Oracle (actual versus standard) requires mapping to Odoo's real-time costing or standard costing configuration.

PA_PROJECTS_ALL and PA_EXPENDITURES store project headers and costed transaction lines. Resource breakdown structures and billing rates require cross-module mapping to Odoo's project costing engine. Oracle's project types (chargeable, non-chargeable, capitalizable) map to Odoo's billing method on project. Billable rates and employee cost rates from PA_PROJECT_PARTIES migrate as Odoo project pricing rules. Open project contracts migrate as Odoo sales orders linked to the project.

FND_ATTACHED_DOCUMENTS and FND_LOBS store files associated with entities across modules as binary blobs or file paths. We extract the binary content or resolve the file path, map to Odoo's ir_attachment records with the correct res_model and res_id linkage to the migrated parent record. Binary attachments exceeding Odoo's default 115 MB size limit are flagged for alternative storage recommendation. OCR and metadata extraction from attachments is outside scope.