The EBS → Fusion Migration Map

Org parameters + the HR org master on both sides. Fusion's HR org master is date-effective (_F — dedupe on the effectivity window before joining), and the operating-unit layer is replaced by business units (FUN_ALL_BUSINESS_UNITS_V).

Both sides stripe items per inventory organization with a _B/_TL split. Fusion moves the item number out of the SEGMENT1 flexfield into a real EGP_SYSTEM_ITEMS_B.ITEM_NUMBER column, and the description lives ONLY on the TL side.

Assignment bridge + category master + category set (catalog) definitions on both sides. Fusion's assignment table is EGP_ITEM_CAT_ASSIGNMENTS — the familiar EGP_ITEM_CATEGORIES name is a view over it — and Fusion category codes are real columns, not flexfield segments.

EBS UOM master is language-striped with no _B base; conversions carry the item-0 standard-row convention. The Fusion UOM tables are not yet cataloged.

Both sides keep receipt-level slices needing aggregation at the detail grain; Fusion adds a system-maintained summary table (INV_ONHAND_QUANTITIES_SUMMARY) EBS never had.

The movement ledger plus its type decode on both sides. Fusion splits the type's name to a _TL companion, types are keyed the same way, and lot/serial detail moves fully to child tables.

Lot masters key by item + org + lot number on both sides. Fusion's per-transaction lot detail table is not yet cataloged.

Same trap on both sides: the org column is CURRENT_ORGANIZATION_ID (the unit's current position), not ORGANIZATION_ID.

Near-identical demand-source/supply-source models; Fusion keeps the same column vocabulary (RESERVATION_ID, DEMAND_SOURCE_*, SUPPLY_SOURCE_*).

Fusion-only: the transfer order replaces EBS internal requisitions/internal sales orders as the document for org-to-org moves. The header is deliberately thin — status, orgs, and quantities live on the lines.

EBS: headers and lines plus the order/line type dimension, operating-unit striped. Fusion adds a third tier — the fulfillment line is the analytics grain — and the ORG_ID stripe now means business unit. Fusion has no order-type _TL dimension table in this catalog.

EBS splits instance, source criteria, and definition; Fusion's hold instance carries level-specific parent pointers (order, line, fulfillment line) directly, and definitions live in a hold-codes table not yet cataloged.

EBS models modifier applications; Fusion replaces them with a price waterfall — charges classify, components carry the money. The nearest concept pair, not a column-for-column match.

The order-line to requisition/PO bridge.

The three core tables carry their EBS names into Fusion — but there are no legs (the trip layer is gone), no container rows (packing goes through license plates), and the detail table's ORG_ID changes meaning from operating unit to business unit (see the quirks guide's #all-means-bu).

EBS-only: the trip layer was not carried into Fusion Shipping — trip-level attributes (carrier, ship method, waybill, actual departure) live directly on the Fusion delivery header, and multi-stop planning is a transportation-management concern.

The four-level document keeps its names and shape — but the stripe changes from ORG_ID to named BU columns (PRC_BU_ID/REQ_BU_ID), and there is no releases table: agreements release through the same document tables.

Requisitions moved to the Self Service Procurement (POR) product family; the number is a real column (no SEGMENT1) and lines still point forward at the PO they became.

Suppliers moved to the POZ family: the master keeps VENDOR_ID but loses its name column (the display name lives on the TCA party), and sites stripe per procurement BU with the documented _M-suffixed base table.

All three receiving tables carry their EBS names and shape into Fusion — including the insert-only event ledger and the parent-transaction chain.

EBS: the physical _B pair plus two compatibility views. Fusion moves item structures into the product model (EGP) and keys the assembly item through text-typed OBJ_NAME/PK1_VALUE/PK2_VALUE columns rather than a real item-id column.

Fusion replaces routings with work definitions, which bind the item structure directly (BILL_SEQUENCE_ID) and version through dated snapshots; operations date-slice rather than carrying version keys.

EBS departments become Fusion work centers (inside work areas), and the resource master moves to WIS — capacity lives on the many-to-many work-center-resource assignments, not the masters.

Fusion collapses the entity registry + job detail into one work-order header; statuses become user-definable rows mapped to system statuses, and accounting classes give way to cost management.

The same four concerns map cleanly: operation position counters, material requirements, the product-move ledger (dispatch-state pairs replace move steps), and the resource-charge ledger.

The EBS org + cost-type model becomes cost org + cost book (+ cost profile): standard and perpetual-average costs live in separate method-specific tables, and cost elements replace the fixed EBS element columns.

Forecast and MDS/MPS name masters plus their date-grain entries, with consumption/relief semantics.

ASCP plan registry, the plan-scoped item copy, and the supply/demand output; item ids bridge to EBS only through the source-item column.

All three layers carry their EBS names into Fusion — party, party site, and location, shared by customers and suppliers alike. Fusion documents location time zones in TIMEZONE_CODE and moves TCA's documentation into the CX book; this crosswalk does not assert a one-to-one EBS source-field rename.

Same three commercial layers, same names — but the stripe changed: the _ALL tables carry NO ORG_ID in Fusion; they stripe by SET_ID (reference data set). Fusion also drops the EBS order-defaulting columns from site uses.

Header and mixed-kind lines keep their EBS names and shape; ORG_ID now means business unit, and the type/batch-source FKs became *_SEQ_ID columns. The AR → order-management link stays text-typed on both sides.

Both tables carry over by name, including the shared schedule table for transactions and receipts and the 31-DEC-4712 open-item sentinel dates.

All three levels keep their names, with the PO/receipt match pointers intact. Fusion quirk: SET_OF_BOOKS_ID survives on the AP tables as the LEDGER id, and invoice-number uniqueness per supplier + BU is database-enforced (it was application-enforced in EBS).

Ledger-scoped journal headers and debit/credit lines carry over name-for-name — LEDGER_ID on headers and lines, no org striping on either side.