Migrate from Oracle E-Business Suite to Epicor Prophet 21

Oracle GL stores multiple ledgers per legal entity with configurable segment structures in GL_CODE_COMBINATIONS. We extract the chart of accounts, journal batches, and period balances from GL_BALANCES. Each Oracle Ledger maps to an Epicor Fiscal Year and Ledger combination. Epicor's segment structure uses a different accounting dimension model; we collapse Oracle's N-segment chart (commonly 6-10 segments: company, business unit, account, department, product line, etc.) into Epicor's master data dimension fields and preserve the original Oracle CCID as a reference field for audit.

Oracle PO_VENDORS + PO_VENDOR_SITES_ALL store supplier records with address book entries, bank accounts (IBY_EXT_BANK_ACCOUNTS), payment terms, and site assignments. We flatten Oracle's site-based supplier model into Epicor's Vendor with vendor addresses and bank account records as related entities. Oracle payment terms (POZ_TERMS) map to Epicor Terms records. Purchasing assignments at the vendor-site level are preserved as vendor address defaults.

Oracle AR customers split across RA_CUSTOMERS, RA_ADDRESSES, and HZ_PARTIES: a single party (person or organization) can have multiple customer accounts and multiple address sites. We flatten this into Epicor's Customer entity by joining HZ_PARTIES.PARTY_ID to RA_CUSTOMERS.CUSTOMER_ID, collapsing all party-level contact and address data into one Customer record per operating unit. Profile classes, credit hold statuses, and Collector assignments from AR_CUSTOMER_PROFILES map to Epicor Customer CreditHold and Terms fields.

AP_INVOICES_ALL and AP_INVOICE_LINES_ALL store invoice headers and distributions separately. We extract balance-owing amounts, hold statuses, and payment terms from AP_PAYMENT_SCHEDULES. Oracle's invoice-level and line-level tax records from AP_TAX_LINES migrate to Epicor's InvoiceTax records. Invoice distributions (APInvoiceExpB不要再) map to Epicor APInvoiceExpense records tied to GL accounts.

AR_INVOICES_ALL and AR_RECEIVABLE_LINES_ALL store invoice headers and receivable lines with AR transaction types. We extract balance remaining from AR_RECEIVABLES_TRX and map Oracle's legal-entity org_id to Epicor's Company. Oracle's Remit-To address hierarchy (HZ_PARTIES) migrates as the Epicor customer bill-to and ship-to address records.

PO_HEADERS_ALL and PO_LINES_ALL store PO headers and lines with authorization status and type codes. We flag lines in APPROVED status as eligible for target load; DRAFT and REJECTED lines are excluded unless the customer explicitly requests them. Oracle's schedule-based distributions (PO_DISTRIBUTIONS_ALL) map to Epicor POLineTax and PORel records. PO approval workflows do not migrate; we document approval limits and thresholds as a written inventory for the customer's admin to configure in Epicor approval chains.

MST_ORGANIZATIONS defines Oracle org structure; MTL_SYSTEM_ITEMS_B defines the item master with organization-specific on-hand quantities. Subinventory assignments and locator hierarchies require careful mapping to Epicor's PartBin and warehouse structure. Oracle's org_id maps to Epicor Plant/Site. We extract on-hand quantities from MTL_ONHAND_QUANTITIES_DETAIL and map each org-specific inventory record to Epicor PartBin records. Oracle's revision control (MTL_ITEM_REVISIONS) maps to Epicor PartRev for revision tracking.

BOM_STRUCTURES_B and BOM_ROUTINGS_B store multi-level BOMs and routing sequences. Oracle BOM types (M, A, E, T for manufacturing, phantom, planning, template) must map to Epicor JobMtl and JobOper JobHead records. The explode/implode topology between BOM levels must be preserved in correct topological order during load or the job structure will not nest correctly. We perform a topological sort of the BOM tree before generating Epicor JobMtl records with the correct bill and sequence.

WIP_JOB_SCHEDULE_SCHEDULES stores discrete and process work orders with status codes (pending, released, complete, closed, cancelled). Open and released WIP jobs require material allocations (WIP_MTL_ALLOCATIONS) and routing step sequencing (WIP_OPERATIONS). We extract job start and completion dates, scrap percentages, and alternate routing flags. Closed and cancelled jobs are excluded unless the customer requests historical reporting records. Epicor's JobMtl and JobOper are linked to JobHead; we resolve the JobNum and PartNum references during the transform phase.

PA_PROJECTS_ALL and PA_EXPENDITURES store project headers and costed transaction lines. Resource breakdown structures and billing rates require cross-module mapping to Epicor's project costing engine. Oracle's expenditure type and organization segments map to Epicor ProjectPhase and LaborDtl burden rates. We extract PA_BURDEN_COSTS and PA_REVENUE_COSTS for project-level financial data. Project forecasts and budgets stored in PA_BUDGET_BASE map to Epicor ProjectBudget records.

HRMS employee records span PER_ALL_ASSIGNMENTS_F and PER_PERSONS_F with assignment grades, supervisors, cost centers, and termination dates. Effective dates on assignments require period-aware extraction to preserve the correct employment history in Epicor Employee records. Oracle HRMS functionality requires Epicor Human Capital Management or a separate HRIS integration; we migrate the employee master and cost center assignments only if Epicor HCM is in scope. If the destination is Epicor ERP without HCM, we migrate employee records as a reference table only.

FND_ATTACHED_DOCUMENTS and FND_LOBS store binary files associated with entities across modules. We extract the LOB content or file paths and map them to Epicor's Document Management records linked to the corresponding entity (Customer, Vendor, Part, Job). PDF and Office document attachments migrate as-is; legacy Oracle Report output files (RDF-generated PDFs) require format conversion or are flagged as candidates for Epicor Report Builder rebuild.