Migrate from Oracle JD Edwards EnterpriseOne to Microsoft Dynamics 365 Business Central

JDE Address Book (F0101) is a single master entity table for customers, suppliers, employees, and prospects differentiated by Address Book type codes (ECST). We split by ABAN8 address number and the AT1-AT3 alpha name fields: entities with type Customer become D365 CustCustomerV2 entities; type Supplier become VendVendorV2 entities; type Employee become HcmWorkerV2 or DirPerson entities depending on D365 HR module scope. F0111 contact info and F0116 phone numbers attach as Contact Info records linked to the respective Customer or Vendor. We resolve address book numbers (ABAN8) as the dedupe key during import and map JDE category codes to D365 Customer Groups and Vendor Groups.

JDE GL uses object-account structure (Company.OBJ.SUB in F0901) where Company maps to a business unit. We translate each JDE object account into a D365 Main Account and generate Financial Dimension sets from the JDE Company and Subsidiary (SUB) values. D365 requires a Chart of Accounts configuration before any GL data loads; we build the COA as a parallel workstream during migration scoping. Budget and actual amounts from F0901 load into GeneralLedgerAccountSummary with fiscal period sliced by the JDE fiscal date patterns.

F0411 invoice headers and F0414 payment history carry open AP balances that must reconcile to the penny post-import. We extract the vendor address number, invoice number, invoice date, due date, gross amount, and currency from F0411 and F0414, then create D365 VendInvoiceJournalHeader and VendInvoiceJournalLine records with the open amount preserved in PaymentTermsReference. JDE invoice numbers become D365 InvoiceNumbers; we flag duplicates against existing D365 vendor invoices during load.

F0311 invoice headers and F03B11 receipt history carry open AR balances. We map F0311 document number to D365 InvoiceNumber, invoice date to InvoiceDate, and outstanding balance to PaymentTermsReference on the CustomerInvoiceEntity. Receipt records from F03B11 become D365 CashDisc and PaymentJournal records linked to the customer account. Currency conversion rates from F0015 (currency exchange rates) are pre-loaded into D365 ExchangeRateProvider before AR import.

F4101 item master records map to D365 Released Products with item number, description, unit of measure (from F41002), and stocking type preserved. JDE stocking type codes (STKT) map to D365 ProductType (Item vs Service) and InventoryModelGroup. Cost layers from F4101 (LandedCost factors) translate to D365 CostingVersion and CostGroup assignments. JDE category codes (CTRY, PCTR, LOCN) become D365 Product Categories linked via CategoryHierarchy.

F4102 branch/plant records map to D365 Warehouses (inventLocationId from JDE MPLN or branch plant code) and InventOnHand entities. Quantity on hand at the time of migration freeze date is extracted from F4102 and loaded into D365 InventSum with the corresponding site and warehouse references resolved. Serial and lot numbers from F4108 and F41L08 load as D365 InventSerial and InventLot entities linked to the on-hand records.

F4211 order headers and F42119 order detail lines are the most structurally complex JDE tables because pricing, taxes, and branch/plant assignments are embedded directly in the line record. We extract header fields (document type, order number, customer address number, order date) and line fields (item number, quantity ordered, unit price, extended amount, branch/plant) separately, then reconstruct them as D365 SalesOrderHeaderEntity and SalesOrderLineEntity records. JDE order status codes (STAJ) map to D365 SalesOrderStatus with held orders flagged as SalesOrderHoldStatus.

F4311 uses a complex row structure where receipt and invoicing lines are intermingled with order lines under the same document number. We extract purchase order headers, lines, and schedule dates as separate queries, then reconstruct them as D365 PurchTable and PurchLine entities. Receipt schedules (F43121) map to D365 PurchReceiptSchedule. JDE document types (DCTO) map to D365 PurchTableOriginDocumentType.

JDE Work Orders (F4801) carry routing and operation data in F3112 and BOM assembly lines in F3003 as three separate linked tables. We extract the complete work order assembly hierarchy, resolve the parent F4801 WO number, and reconstruct it as a D365 ProductionOrder with routes (from F3112 operation sequences and work centres) and bill of materials (from F3003 component lines) as sub-components. JDE work order status (WOST) maps to D365 ProductionOrderStatus. We flag any F3111 route revisions for manual review post-import.

JDE Advanced Pricing schedules in F4072 store effective dates, break quantities, adjustment types, and formula-based pricing. We extract the full pricing hierarchy and map price adjustment rules to D365 Trade Agreements (SalesPrice and PurchasePrice) and PriceGroup entities. JDE pricing formulas requiring calculation logic that cannot map to D365 trade agreement conditions are flagged in the pricing inventory document for manual rebuild in the D365 pricing page or a pricing extension.

Media objects stored in F00165 (attachments, images, embedded documents) require R98MODAT to be run as a pre-export step to load filesystem-attached files into the database. Without this utility, attachments are silently excluded from the JDE export. We run R98MODAT before extraction and then migrate media objects as D365 attachments linked via the SharePoint document management integration or the Dataverse annotation entity depending on the target D365 workload.

JDE UDOs (custom reports/UBEs, custom tables, custom business functions) tracked in the Object Management Workbench are not end-user data and do not have a direct D365 equivalent. UDOs reserved to a specific development project are reassigned to the user's default project during the JDE export process; we document every UDO project assignment pre-export and re-reserve in the target environment post-import. Custom UBEs cannot be compiled for D365; we deliver a written UDO inventory with each object's purpose, last-modified date, and the recommended D365 rebuild path (Power BI for reports, AL extensions for custom tables).