Migrate your Oracle JD Edwards EnterpriseOne data

The Address Book is JDE's master entity table for customers, suppliers, employees, and prospects. We export from F0101 and related tables (F0111 for contact info, F0116 for phone numbers) and map to the destination's equivalent contact/account entity. Multi-address and role-based records require splitting into separate destination records.

We migrate General Ledger accounts (F0901), Accounts Payable (F0411, F0414), and Accounts Receivable (F0311, F03B11) records. Open AP/AR transactions carry outstanding balances and payment terms that must be preserved to maintain audit continuity in the destination system.

Item master records and branch/plant inventory records are stored in F4101 and F4102 respectively. We preserve unit of measure conversions, cost layers, stocking types, and category code assignments. Bill of Materials (F3002, F3003) and work center definitions (F3006, F3009) are migrated as separate but related objects.

Sales order headers land in F4211 and detail lines in F42119. JDE embeds pricing, taxes, and branch/plant assignments directly in these tables. We map order statuses and line types to the destination's pipeline stage equivalents, flagging any held or pending orders that require manual review before activation in the new system.

Purchase orders use F4311 with a complex row structure where receipt and invoicing lines are often intermingled. We extract purchase order headers, lines, and schedule dates separately and reconstruct them in the destination, preserving approval workflow status where applicable.

Manufacturing work orders carry routing and operation step data that JDE stores across multiple linked tables (F4801, F3112 for operations, F3003 for BOM). We extract the complete work order assembly structure and map production status to the destination's equivalent project or work-order lifecycle stage.

Advanced Pricing schedules are stored in F4072 with effective dates, break quantities, and adjustment types. We extract the full pricing hierarchy and map price adjustment rules to the destination's pricing engine, noting any unsupported adjustment types that require manual reconfiguration.

Custom reports (UBEs), custom tables, and other UDOs are tracked in JDE's Object Management Workbench. During migration, UDOs reserved to a specific project are reassigned to the user's default project. We flag any custom business functions that depend on C++ compiled code, as these may not be portable across platform architectures.

Media objects — attachments, images, embedded documents — are stored in the F00165 table and related tables. Oracle recommends running the R98MODAT utility before export to load all media objects into the database. We extract and re-attach them in the destination, preserving any retention or classification metadata.

Table Conversions are JDE's internal migration tooling for applying schema changes during version upgrades. They are not end-user data records and are not relevant to cross-ERP data migration. We do not migrate TC definitions; they are regenerated as part of the target JDE environment's upgrade process.