Migrate from Oracle JD Edwards EnterpriseOne to Dolibarr ERP

JDE's Address Book (F0101) is the master entity table for customers, suppliers, employees, and prospects, with contact details in F0111 and phone numbers in F0116. We extract Address Book records with their AN8 (address number) as the primary key and map each to Dolibarr llx_societe (the third-party record) and llx_socpeople (the contact person). Address type (customer vs supplier) maps to Dolibarr's client and fournissor flags on llx_societe. JDE category codes (user-defined fields on F0101) map to Dolibarr custom fields we create during schema setup. Lookup dependencies are resolved by AN8 before contact insert.

JDE GL records (F0901) carry account codes, amounts, fiscal year periods, and company identifiers in a multi-ledger structure. Dolibarr's accounting module stores entries in llx_accounting_bookkeeping with account number, debit/credit, and period. We extract F0901 by fiscal year, map JDE account numbers to Dolibarr's chart of accounts, and split compound journal entries into individual ledger lines. Note that Dolibarr's accounting module is double-entry only; JDE's multi-ledger flexibility does not map directly and may require account number restructuring for organisations with more than one legal entity ledger.

JDE AP records (F0411 for header, F0414 for distribution) store vendor invoices with payment terms, G/L distribution, and receipt matching. We map F0411 document number to Dolibarr llx_facture_fourn, vendor AN8 to the supplier Third Party lookup, and F0414 distribution lines to llx_facturefourn_det. Open AP invoices with outstanding balances carry forward; paid invoices migrate as historical records with a paid status. Note that Dolibarr does not have native three-way matching automation; the matching logic is documented for admin to implement as manual procedures.

JDE AR records (F0311 and F03B11) store customer invoices with open or closed status, payment terms, and aging buckets. We map to Dolibarr llx_facture for invoices and llx_commande for related sales orders. JDE invoice numbers and A/R document numbers become Dolibarr ref and ref_client fields. Open invoices migrate with their outstanding balance; paid invoices migrate with the paid status flag set. JDE's aging buckets (F03B14) are computed on import rather than stored directly since Dolibarr computes aging from invoice due dates.

JDE Item Master records (F4101) carry item number, description, unit of measure, cost, category codes, and stocking type. We map to Dolibarr llx_product with the JDE short item number or second item number used as the product ref. Unit of measure conversions from F41003 migrate as Dolibarr unit-of-measure entries. Cost layers from F4101 (standard, last, and average cost) map to cost fields in llx_product. Category codes become Dolibarr custom fields or tags since the category code hierarchy in JDE (with up to 30 user-defined category code fields) does not have a direct Dolibarr equivalent.

JDE stores branch/plant inventory levels in F4102, with one row per item per branch. Dolibarr stores stock per warehouse in llx_product_stock. If the source JDE environment uses multiple branches, we split each F4102 row into separate llx_product_stock entries, creating Dolibarr warehouses named after the JDE branch/plant identifier (MCU field). Stock quantities, locations, and lot/serial numbers from F4108 migrate to Dolibarr's lot/serial tracking tables.

JDE Sales Order headers (F4211) carry order number, customer AN8, order date, requested date, branch/plant, and order total. We map to Dolibarr llx_commande with the JDE order number preserved in ref_client. Header-level pricing and taxes embedded in F4211 are extracted separately and mapped to order line tax entries. Order status (F4211 SDDOCST field) maps to Dolibarr's ligne_statu values (DRAFT, VALIDATED, SHIPPED, CLOSED, CANCELLED). Parent-account resolution uses AN8 to lookup the customer's llx_societe record.

JDE Sales Order lines (F42119) store item number, quantity ordered, quantity shipped, unit price, discount, branch/plant, and line status. We map to Dolibarr llx_commandedet linked to the parent llx_commande. The JDE item number maps to the Dolibarr product reference; if the item is a kit or assembly, we map the bill of materials lines to separate order lines. Line-level taxes from F42119 transfer to tax lines in llx_commandedet. Quantity delivered in JDE becomes shipped quantity in Dolibarr on a 1:1 basis.

JDE Purchase Orders (F4311) store vendor, line items, quantities, prices, and delivery schedules. F4311's row structure intermingles receipt and invoicing lines, so we extract header, line, and schedule data separately and reconstruct them as Dolibarr llx_commande_fournisseur records. Vendor AN8 resolves to the Dolibarr supplier Third Party. The POLT (line type) field determines whether the line is a standard order line or a miscellaneous charge, which maps to Dolibarr's service vs product line distinction.

JDE Work Orders (F4801) carry routing and operation step data across multiple linked tables (F3112 for operations, F3003 for BOM). Dolibarr does not have native manufacturing work orders; we map work order headers to llx_projet records with work order number as ref and description from F4801. Operations and BOM lines map to llx_projet_task entries with planned hours and dates. Note that Dolibarr's project module does not support routing step sequencing or machine resource scheduling; this is a documented gap for the customer's manufacturing team to address with third-party addons or manual procedures.

JDE Advanced Pricing schedules stored in F4072 carry multi-level, volume-sensitive, and formula-based pricing rules with effective date ranges. Dolibarr has no native equivalent to Advanced Pricing; complex pricing rules do not migrate. We extract the full pricing rule hierarchy during discovery, document every price adjustment group, break quantity tier, and formula, and deliver a written pricing schedule inventory. The customer's admin rebuilds key pricing rules in Dolibarr's product price list module or documents requirements for a third-party pricing addon.

JDE stores attachments, images, and embedded documents in F00165 and the filesystem. Oracle requires running R98MODAT before export to load all media objects into the database table. We run R98MODAT as a pre-export step on Tools Release 9.2.1 and later, then extract F00165 records and their associated binary content. Media objects map to Dolibarr's ECM file management (llx_ecm_files) linked to the relevant parent record (Third Party, Product, Order). We resolve the parent reference by matching JDE's object type and key to Dolibarr's entity and rowid before inserting each file record.

Custom reports (UBEs), custom tables, and other UDOs tracked in JDE's Object Management Workbench have no direct Dolibarr equivalent. We document every UDO project assignment during discovery (using P98401 to identify modified and custom objects), extract UDO metadata, and deliver a written UDO inventory with object type, project reservation, and modification flag. UDOs are not data records and are not migrated. Dolibarr's PHP addon framework is the replacement path for custom business logic.