Migrate from Oracle E-Business Suite to Infor CloudSuite Corporate

Oracle GL stores multiple ledgers per legal entity with configurable segment structures in GL_SETS_OF_BOOKS. The chart of accounts (COA segments, flex values, cross-validation rules) migrates to Infor CloudSuite's Ledger structure. Journal batches and period balances are extracted from GL_BALANCES and GL_JE_BATCHES, with accounting date preservation and currency conversion rates loaded to maintain period-closing integrity. Segment structures require mapping to Infor's account code definition because the segment count and delimiter conventions differ between platforms.

AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and AP_SUPPLIER_BANKS store Oracle vendor records with address book linkage via HZ_PARTIES. Sites, payment terms, bank accounts, and purchasing assignment flags migrate to Infor CloudSuite's Vendor entity. Oracle's supplier-level hold status and invoice hold flags map to Infor's vendor approval workflow status. Address records with multiple sites require flattening to Infor's site-of-record structure, with primary-site designation preserved.

Oracle AR splits customer data across RA_CUSTOMERS (header), RA_ADDRESSES (sites), HZ_CONTACTS (contacts), HZ_PARTIES (name and classification), and RA_CUSTOMER_PROFILES (credit terms). We flatten these into Infor CloudSuite's Customer entity with contact and site sub-records. Profile class credit limits, payment terms, and dunning profiles migrate to Infor's customer financial settings. Customer type (person vs organization) is preserved from HZ_PARTIES.PARTY_TYPE.

Oracle HRMS stores employees across PER_ALL_PEOPLE_F (personal information), PER_ASSIGNMENTS_F (job, grade, department, cost center, supervisor), and PER_PAYMENT_METHODS (payroll costing). Effective dates on assignments require date-range filtering at migration time to extract the current active assignment. Termination dates and historical assignments are preserved as prior-period records in Infor for audit completeness. Organization hierarchies from HR_ORGANIZATION_UNITS map to Infor's operating unit structure.

AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL store Oracle payables with header-line-detail structure, payment terms, hold status, and distribution accounting code combinations. We extract open invoices (not fully paid) and map Oracle's terms-date-based due date calculation to Infor's calendar-based due date engine. Oracle's invoice hold flags (budget hold, matching hold) require mapping to Infor's approval workflow states.

RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL store Oracle receivables invoices (transaction headers) with transaction type, gl_date, and amount. Balance-owing amounts and aging buckets migrate to Infor's AR transaction records. Receipt records (AR_CASH_RECEIPTS) migrate separately as payment applications. Oracle's remittance bank account and payment method map to Infor's cash application rules.

PO_HEADERS_ALL, PO_LINES_ALL, and PO_DISTRIBUTIONS_ALL store Oracle purchasing documents with authorization status. Lines in APPROVED status are migrated as eligible; DRAFT, REJECTED, and CANCELLED lines are excluded unless the customer explicitly requests otherwise. Schedule-level quantities and promized dates migrate to Infor PO schedule lines. Ship-to organization references require mapping to Infor's inventory organization structure.

MST_ORGANIZATIONS defines Oracle inventory org structure; MTL_SYSTEM_ITEMS_B defines the item master with organization-specific on-hand quantities. Subinventory assignments, locator hierarchies (MTL_ITEM_LOCATIONS), and lot/serial control parameters migrate to Infor CloudSuite's warehouse and inventory structure. Oracle's org-level security (MOAC) maps to Infor's operating unit and warehouse access controls. Multi-org inventory requires mapping each Oracle org_id to the corresponding Infor warehouse entity.

MTL_SYSTEM_ITEMS_B stores Oracle item masters with template-based attributes, category assignments, lot/serial controls, and costing information. Items are extracted by inventory organization and mapped to Infor's item master, preserving the primary unit of measure, category assignments, and costing method (standard, average, FIFO). Template-driven attributes from Oracle's item template are resolved to Infor's item attribute groups.

BOM_STRUCTURES_B and BOM_COMPONENTS_B store multi-level BOMs with common bill and alternate bill variants. The explode/implode relationship between levels requires topological sort before migration to avoid circular reference errors in Infor's BOM loading. We sequence parent items before component items, extract the full BOM hierarchy, and map Oracle's bill type (M, A, E for manufacturing, option, engineering) to Infor's bill classification. Routing-linked BOMs require BOM-Routing co-migration because Infor resolves the relationship at load time.

BOM_ROUTINGS_B and BOM_ROUTING_OPERATIONS store multi-step manufacturing routings with work center assignments, queue time, run time, and operation sequences. We map Oracle work center codes to Infor work center entities and resolve the routing-bill linkage by item number and alternate bill sequence. Routing steps require sequential operation numbering that preserves the original Oracle sequence to maintain Infor's scheduling accuracy.

WIP_JOB_SCHEDULE_SCHEDULES stores discrete and process work orders with status codes (RELEASED, UNRELEASED, CLOSED, CANCELLED, COMPLETE). Open and released WIP jobs migrate to Infor production orders with material allocation and routing step sequencing. Closed and cancelled jobs are migrated as historical records with actual costing data. Oracle's WIP entity type (discrete vs repetitive vs project) maps to Infor's production order type classification.

PA_PROJECTS_ALL and PA_EXPENDITURES store Oracle project costing with project headers, phases, tasks, resource breakdown structures, and costed transaction lines. Top-down and bottom-up budgeting structures require separate mapping passes. Billing rates, worktype assignments, and expenditure organization references migrate to Infor's project costing module. Capital vs expense project classification is preserved from PA_PROJECT_TYPES.

FA_ASSETS_B and FA_ASSET_BOOKS store Oracle fixed assets with book-specific depreciation methods, asset categories, and asset registers. Multiple asset books (tax, GAAP, management) are mapped to Infor's asset book structure. Depreciation conventions (half-year, mid-month) and asset life parameters migrate to preserve the depreciation schedule in the target system.

FND_ATTACHED_DOCUMENTS and FND_LOBS store files associated with entities across Oracle EBS modules. Binary LOB data or file paths are extracted and mapped to Infor CloudSuite's document management linkage table. We preserve the original document category and entity linkage so that documents attach to the correct Infor entity. Large binary attachments (over 50MB per file) may require separate handling for Infor's document storage limits.