Migrate from Oracle E-Business Suite to Microsoft Dynamics 365 Business Central

Oracle GL stores multiple ledgers per legal entity with configurable segment structures (up to 30 segments) defined in GL_SETS_OF_BOOKS. We extract the chart of accounts, journal batch headers and lines, and period balances. Segment values from FND_FLEX_VALUES map to Dynamics 365 Financial Dimensions (F&O) or Dimensions (Business Central). Ledger-level security assignments migrate as security role mappings against the legal entity or company in the destination.

AP Supplier records include vendor headers (PO_VENDORS), site assignments (PO_VENDOR_SITES_ALL), bank accounts (AP_SUPPLIER_SITES_ALL with IBAN/SWIFT), payment terms, and purchasing assignments. We map all supplier sites to Dynamics vendor addresses, preserving the primary site flag and purchasingBU. Pay-by flag and payment priority migrate as vendor attributes. Supplier contacts flatten into vendor contact records.

Oracle AR customers split across RA_CUSTOMERS (header), RA_ADDRESSES (site), and HZ_PARTIES (party). Sites, contacts, and profile classes are stored separately. We flatten these into Dynamics customer records with addresses and contact persons. The HZ_PARTIES party_id becomes the customer number or external reference in the destination. Customer profile class balances and credit limits migrate as credit limit settings.

HRMS employee records span PER_PERSONS, PER_ALL_ASSIGNMENTS_F, and PER_PAYMENT_METHODS. Assignment grades, supervisors, cost centers, and termination dates are extracted. Effective dates on assignments require daterange-aware transforms because Dynamics stores valid-from and valid-to on employment records. If the destination is Business Central, HCM data requires integration via Human Resources module or a third-party HCM connector; F&O has native HRM integration.

AP_INVOICES_ALL stores invoice headers and AP_INVOICE_LINES_ALL stores lines. We extract balance-owing amounts and hold statuses, mapping payment terms to the destination's due date calculation. Only invoices in OPEN or UNPAID status migrate; CANCELLED and PAID records are excluded from the transactional migration. Prepayment invoices and adjustments require separate handling based on the invoice type code.

AR_INVOICES_ALL stores invoice headers with RA_CUSTOMER_TRX_LINES for lines. We extract open receivables with status = 'OP' and balance owing amounts. Credit memos and debit memos migrate separately with their respective reversal flags. Dunning letter history and AR adjustments are documented but not imported as transactional records in the standard scope.

PO_HEADERS_ALL and PO_LINES_ALL carry authorization status. We flag lines in APPROVED status as eligible for target load; DRAFT, REJECTED, and CANCELLED lines are excluded unless the customer requests closed-period history. PO distributions map to financial dimension combinations in F&O or cost category assignments in Business Central. Blanket agreements and contract purchase orders migrate as unconfirmed purchase orders in the destination.

ORG_ORGANIZATION_DEFINITIONS and MTL_PARAMETERS define inventory org structure. MTL_SYSTEM_ITEMS_B defines the item master with organization-specific on-hand quantities. Subinventory assignments and locator hierarchies (MTL_ITEM_LOCATIONS) require careful mapping to Dynamics sites and location codes. Multiple EBS inventory organizations may map to a single Dynamics warehouse depending on the customer's organizational structure.

MTL_SYSTEM_ITEMS_B stores item masters with planning parameters, costing attributes, and BOM flags. We extract unit of measure conversions (MTL_UOM_CONVERSIONS), inventory on-hand quantities (MTL_ONHAND_QUANTITIES), and category assignments (MTL_CATEGORY_SETS). Planning methods (MPS/MRP) and replenishment types migrate as item planning settings. Costing method (standard, average, FIFO) from MTL_COSTS maps to the destination cost method.

BOM_STRUCTURES_B and BOM_REVISIONS_B store multi-level BOMs with component items, quantities per assembly, and operation step references. The explode/implode relationship between BOM levels must be preserved in correct topological order during load, or components reference parent assemblies that have not yet been created. We sequence BOM loads level-by-level starting from leaf nodes. BOM common items and engineering BOMs require separate categorization in the destination.

BOM_ROUTINGS_B stores routing sequences with operation sequence, work center assignments, and resource requirements. We map routing operations to work centers defined in the destination and preserve queue time, run time, and setup time per operation. Resource group assignments from BOM_ROUTING_RESOURCES map to work center capacity groups. Overlapping operations and phantom routings require flag-level transforms.

WIP_JOB_SCHEDULE_SCHEDULES stores discrete and process work orders with status codes (RELEASED, COMPLETE, CLOSE). Open and released WIP jobs require material allocations and routing step sequencing. Closed and cancelled jobs are archived as historical records. We flag status codes that require routing re-assignment because work center IDs in EBS may not match the destination's resource IDs. Component issue and completion transactions migrate as inventory transactions against the production order.

PA_PROJECTS_ALL stores project headers with project types, billing methods, and organizational assignments. PA_PROJECT_PARTIES maps team members and roles. We extract project status, start and finish dates, and template flags. Projects with the TEMPLATE flag map to project templates in the destination. Cross-module billing rates and work breakdown structure (WBS) levels migrate to the project costing engine, with rate type mapping (Burdened vs Non-Burdened) handled per customer rate schedule.

PA_EXPENDITURES and PA_EXPENDITURE_ITEMS store costed transaction lines with expenditure type, organization, and labor or burden multipliers. Resource breakdown structures from PA_RESOURCE_ASSIGNMENTS map to project team roles. Expenditure categories map to project transaction categories in the destination. Only COSTED or BILLED items migrate; DRAFT expenditures are excluded unless the customer requests full history.

FND_ATTACHED_DOCUMENTS and FND_LOBS store files associated with entities across modules. We extract the binary blobs or file paths and map them to Dynamics document attachment records. Document category mapping from FND_DOCUMENT_ENTITIES to the destination entity type preserves attachment context. Attachments over 25 MB may require chunked migration or external blob storage with link references.

CE_BANK_ACCOUNTS and CE_PAYMENT_DOCUMENTS store bank accounts and payment format templates. Bank account numbers, SWIFT codes, and IBAN values migrate to the destination bank account record. Payment format remittance layouts and check stock configurations require re-configuration in the destination because payment format templates are system-specific. Positive pay file configurations are documented but require manual setup in the destination.