Migrate from Oracle JD Edwards EnterpriseOne to Odoo ERP

JDE's Address Book is the master entity table for customers, suppliers, employees, and prospects, stored across F0101 (header), F0111 (contact info), and F0116 (phone numbers). We extract by address type code (AT1 = customer, AT2 = supplier, E = employee) to set Odoo's partner_type field and is_company flag. Parent-child relationships in F0101 (AN8 and ABO) map to Odoo's parent_id on res.partner. Tax IDs and category codes in F0101 map to Odoo's vat field and category_id many2many. Address records with no corresponding AN8 are held for reconciliation against employee and prospect records.

JDE GL account structures use business unit, object account, and subsidiary segments concatenated into a single account code (BU.OBJ.SUB). We extract the full F0901 chart of accounts, parse the segment structure, and map to Odoo's account.account with the correct account_type (asset, liability, equity, revenue, expense). Account balances from F0902 migrate to Odoo's account.move and account.move.line records. Multi-currency ledgers in JDE map to Odoo's account.account with foreign_currency_revaluation enabled.

JDE stores open AP invoices in F0411 with payment terms in F0414. Each invoice line is a separate F0411 row with G/L distribution. We reconstruct invoices as Odoo account.move records of type in_invoice, with line items linked to the vendor partner (res.partner), the AP account, and the corresponding GL account from F0901. Outstanding invoice balances carry forward as Odoo lines in draft state until the customer's AP team reconciles and posts.

Open AR invoices in F0311 and F03B11 map to Odoo account.move records of type out_invoice. JDE's invoice number and batch number become Odoo's ref and invoice_origin fields. Credit memos (document type DM) map to out_refund. Open receivable amounts are preserved as line-level balance values, and Odoo's reconciled flag is set false until the customer's AR team posts payments against the migrated invoices.

JDE item master records in F4101 carry description, unit of measure, cost, and stocking type. Branch plant data in F4102 carries on-hand quantities and location assignments per warehouse. We split F4101 into Odoo's product.template (name, default_code, list_price, standard_price) and product.product variants if lot/serial tracking is active. Each F4102 branch plant becomes an Odoo stock.warehouse with its own location hierarchy. Category codes in F4101 map to Odoo's categ_id and product_tags.

JDE sales order headers live in F4211 with pricing, branch plant, and order date embedded at the line level. We extract order headers separately, map order status codes (970 = cancelled, 999 = held) to Odoo's state values (cancel, sale_order), and preserve the original JDE order number as the Odoo name field. Customer and branch plant references resolve to the migrated res.partner and stock.warehouse lookups before insertion.

JDE order lines in F42119 are distinct rows with pricing, taxes, branch plant, and schedule dates embedded per line. We extract each F42119 row, resolve the product.product reference from F4101 mapping, map the F4211 header key (DOCO, KCOO, DCTO) as the parent sale.order, and create Odoo sale.order.line with qty_delivered and qty_invoiced preserved for open orders. Lines attached to cancelled orders are excluded from migration.

JDE purchase orders use F4311 with a complex row structure where receipt and invoicing lines intermingle. We extract PO headers and lines separately, map line-level branch plant and G/L class to the corresponding Odoo stock.location and account.account. Open POs migrate as purchase.order records in state 'purchase' with lines in purchase.order.line. Closed or received POs migrate in state 'done'.

JDE manufacturing work orders store routing operations in F3112 and BOM components in F3003 as separate tables linked to the F4801 header. We extract the complete work order assembly and split into Odoo's mrp.production (the work order), mrp.bom (the bill of materials from F3003), and mrp.routing.workcenter (operations from F3112). BOM type codes in JDE (M = manufacturing, D = kit) map to Odoo's type field on mrp.bom. Work order status codes (91 = released, 97 = closed) map to Odoo's state on mrp.production.

JDE pricing schedules in F4072 store break quantities, adjustment types, effective dates, and commodity table references. Each F4072 schedule maps to an Odoo product.pricelist with a corresponding product.pricelist.item row per pricing rule. Volume breaks, effective date ranges, and customer-specific pricing all become Odoo pricelist rules with different applied_on and compute_price settings. Complex formula-based pricing in JDE is documented for Odoo partner configuration during the migration acceptance phase.

JDE media objects including attachments, images, and embedded documents are stored in the F00165 table and related filesystem paths. Oracle recommends running the R98MODAT utility to load all media objects into F00165 before export. We invoke R98MODAT as a pre-export step, extract media objects with their F00165 keys, and map each to Odoo's ir.attachment with res_model and res_id pointing to the migrated parent record (res.partner, product.product, sale.order) based on the object type stored in F00165's subject field.

JDE UDOs — custom UBEs, custom tables, and extended business objects tracked in the Object Management Workbench — have no direct Odoo equivalent. UDOs reserved to a specific JDE project are reassigned to the user's default project during export; we document all UDO project assignments, data schemas, and field definitions in a written inventory that the customer's Odoo partner uses to rebuild equivalent custom modules in Python. We do not write Odoo custom module code as part of the standard migration scope.