Fusion Reference
Oracle Fusion Cloud SCM Reference Database
With Fusion Cloud you don’t own the database — so this reference maps the tables AND the BICC/OTBI surfaces that reach them. Built for supply chain and analytics practitioners landing Fusion data in a lakehouse.
Free & ungated · docs release 26C · Last verified September 2026
85
Tables
11
Modules
9
Quirks
How this is scoped
- Scope: the supply-chain core, building out from the foundation, the product master, and inventory toward order management, procurement, manufacturing, and financials — with the BICC/OTBI extract surface mapped alongside every table. A concept-level EBS → Fusion migration map shows where each E-Business Suite concept lives here.
- Verification: field names, keys, and structural facts are curated against each table’s own page in Oracle’s Tables and Views books (docs release 26C); extract data stores and subject areas are checked against the BICC and OTBI books, and every description is original wording. Last verified September 2026.
- Built for analytics: relationships focus on the joins you’ll actually write — header/line pairs, the ORGANIZATION_ID equality on every item-level join, language-filtered translation joins — and the generated SQL targets the BICC-landed lakehouse copy, because there is no SQL path to the SaaS database.
Frequently Referenced Tables
The workhorses of Fusion supply-chain analytics — the item master, on-hand balances, the transaction ledger, and the foundation tables every other join resolves through.
- EGP_SYSTEM_ITEMS_BThe item master — one row per item per inventory organization, carrying the item number as a real column plus status, type, unit of measure, and the control flags for every functional area; every balance, transaction, and order line joins back to it on INVENTORY_ITEM_ID + ORGANIZATION_ID
- INV_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, and lot, consumed in FIFO order as material issues
- INV_MATERIAL_TXNSThe material transaction ledger — one row per inventory movement or cost update, classified by transaction type, action, and source type, with quantity, date, and the document reference that caused it; the reconciliation backbone for every stock question
- DOO_FULFILL_LINES_ALLFulfillment lines — the executable, shippable unit of an order line and the correct analytics grain for order-to-ship reporting, with the quantity lifecycle, schedule/actual dates, fulfillment org, and amounts
- PO_HEADERS_ALLPurchasing document headers — one row per purchase order or agreement (standard, blanket, contract), with supplier, buyer, currency, and the document status; striped by the procurement business unit
- WSH_DELIVERY_DETAILSThe atomic shipment line — one row per shippable unit of demand, tracking the source order line, item, warehouse, and the requested/picked/shipped quantity lifecycle through pick, stage, and ship confirm
- RCV_TRANSACTIONSThe receiving event ledger — one immutable row per receiving action (receive, inspect, transfer, deliver, correct, return), chained to its prior step by parent transaction id; the event-grain truth behind every receipt quantity
- POZ_SUPPLIERSThe supplier master — one row per supplier with the supplier number, type, business relationship level, and tax attributes, backed by the trading community architecture through its party id
- WIE_WORK_ORDERS_BThe work order header — the primary product being built, the work definition version it was created from, the build quantity, status, and planned/actual execution dates
- CST_COST_DISTRIBUTION_LINESThe debit and credit lines under each cost distribution — per cost element, with entered and ledger amounts and both the user-entered and final SLA-derived GL accounts
- INV_RESERVATIONSFirm reservations tying a demand source (a sales order line, most commonly) to a supply source (on-hand or expected supply) for an item in an org, optionally pinned down to subinventory, locator, and lot
- INV_TRANSFER_ORDER_LINESTransfer order lines — the actionable grain carrying item, source and destination organizations, the requested/shipped/received/delivered quantity lifecycle, dates, and the transfer price
- INV_LOT_NUMBERSThe lot master — definition, genealogy (parent lot), grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot number
- INV_ORG_PARAMETERSInventory organization parameters — one row per inventory org, holding the short org code, the item-master org it points to, its business unit and legal entity, and the org's locator/lot/serial control defaults; the org list every ORGANIZATION_ID resolves against
- FUN_ALL_BUSINESS_UNITS_VThe delivered view that enumerates business units — the BU domain later waves' documents stripe on — with the legal entity, primary ledger, and default set each BU resolves to
- GL_CODE_COMBINATIONSEvery chart-of-accounts segment combination (CCID) stored once — the account string behind each SEGMENTn set; accounting distributions and journal lines reference accounts through CODE_COMBINATION_ID
- FND_LOOKUP_VALUESThe generic lookup view — every seeded and user-defined code list (lookup type + code) with its meaning and description, one row per code per installed language; the decode target for coded columns across every module
- HZ_PARTIESThe party master — one row per person, organization, or group in the trading community, with the party number, type, status, and a denormalized identifying address and primary contact point; the top of the four-layer customer model
- RA_CUSTOMER_TRX_ALLReceivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit striped
- AP_INVOICES_ALLPayables invoice headers — one row per supplier invoice, prepayment, or credit/debit memo, with the supplier, invoice number, amounts, payment status, and approval state; business-unit striped
The Fusion quirks guide
The modeling traps that make a first Fusion extract wrong in ways that look right. Each links to a worked Databricks SQL pattern.
Read all 9 quirksGetting Fusion data into your lakehouse
The extraction guide covers existing BICC estates — offerings and data stores, full vs incremental extract mechanics, UCM and OCI Object Storage delivery, PVO-header mapping, and an incremental MERGE pattern — while separating Oracle’s Data Extraction direction for new bulk work. Every table page carries the BICC data store (PVO) and OTBI subject areas that reach it; the BICC-to-business- object mapping is migration evidence, not a complete DET crosswalk.
Read the extraction guideBrowse by Module
Organized by functional area. Click a module to see its tables.
- FoundationBusiness units, the organization master, ledgers, account combinations, and the generic FND lookup table every module decodes through — the layer every ORG_ID and ORGANIZATION_ID resolves against6 tables
- Product MasterThe item master and its satellites — translations, revisions, categories, catalogs, and item structures — that every balance, order, and movement points back to; owned by the Product Model (EGP)8 tablesSupply chain
- InventoryInventory org parameters, subinventories and locators, on-hand balances at detail and summary grain, the material transaction ledger, lots, serials, reservations, movement requests, and transfer orders13 tablesSupply chain
- Order ManagementSales order headers, lines, and fulfillment records across the order-to-cash cycle — owned by Distributed Order Orchestration (DOO)6 tablesSupply chain
- Shipping & DeliveriesDelivery details, deliveries, and shipment records between order lines and the customer dock3 tablesSupply chain
- ProcurementPurchase orders, requisitions, and supplier records across the procure-to-pay cycle8 tablesSupply chain
- ReceivingReceipt headers, lines, and the receiving transaction ledger between the supplier shipment and stores3 tablesSupply chain
- ManufacturingWork definitions, work orders, and shop-floor execution records for production — owned by the manufacturing products (WIE/WIS)11 tablesSupply chain
- Cost ManagementCost accounting records — item costs, cost distributions, and the cost-processing layer margin analytics draw from12 tablesSupply chain
- Customers (TCA)The trading community model — parties, customer accounts, and sites — that order and receivables records resolve to6 tables
- FinancialsReceivables, payables, and general-ledger journal records the supply-chain subledgers post into9 tables
Sources & further reading
Table structure and behavior are authoritative only at source. Use these references to verify before building on any claim in this reference.
Show all 21 sources
Primary sources
- Tables and Views for SCM (26C) (opens in new tab) — the official column-level authority for the INV and EGP tables; every field row in this reference was checked against its table's own page.
- Tables and Views for Financials (26C) (opens in new tab) — GL ledgers and code combinations, and the business units view.
- Tables and Views for Procurement (26C) (opens in new tab) — the column-level authority for the PO, requisition, and supplier tables, which Oracle documents in the Procurement book rather than the SCM book.
- Tables and Views for HCM (opens in new tab) — the date-effective HR organization master every org id resolves to.
- Tables and Views for Common Features (26C) (opens in new tab) — FND_LOOKUP_VALUES and its physical _B/_TL base pair.
- Tables and Views for Sales, Fusion Service, and Field Service (opens in new tab) — the HZ/TCA customer tables' column-level authority; Fusion documents the trading community in the CX book.
- Creating a Business Intelligence Cloud Extract (26C) (opens in new tab) — the BICC extract mechanics behind the #no-sql and #pvo-drift quirks and the incremental watermark caveat.
- Data Extraction Tool — Map BICC Data to Business Object Data (opens in new tab) — Oracle's migration mapping for estates moving from BICC PVOs to Data Extraction business objects and extraction views.
- Oracle SCM Cloud Applications Readiness (opens in new tab) — the current quarterly-release provenance used to check this reference's deliberate 26C documentation pin.
- Extract Data Stores for SCM (26B) (opens in new tab) — the PVO data-store keys behind every entry in the extract map.
- Extract Data Stores for Financials (26B) (opens in new tab) — the GL and business-unit PVO keys behind the foundation extract-map entries.
- Extract Data Stores for Procurement (26B) (opens in new tab) — the purchasing, requisition, and supplier PVO keys behind the procurement extract-map entries.
- Extract Data Stores for Sales and Fusion Service (opens in new tab) — the CrmAnalyticsAM PVO keys behind the customers module's extract-map entries.
- Subject Areas for Transactional Business Intelligence in SCM (26B) (opens in new tab) — the OTBI subject-area names shown in the extract map, spelled exactly as Oracle documents them.
- Subject Areas for Transactional Business Intelligence in Financials (26B) (opens in new tab) — the Receivables, Payables, and General Ledger subject-area names behind the financials extract-map entries.
- Subject Areas for Transactional Business Intelligence in Procurement (26C) (opens in new tab) — the Procure To Pay, Purchasing, Requisitions, and Supplier subject-area names behind the procurement extract-map entries.
- Subject Areas for Transactional Business Intelligence in Sales (opens in new tab) — the CRM Customers and Contacts subject-area name behind the customers extract-map entries.
- Implementing Common Features for Financials — Reference Data Sets (opens in new tab) — the reference-data-set sharing model behind the #set-id quirk and the SET_ID-striped TCA tables.
- Implementing Receivables — Customer and Party Structure (opens in new tab) — the four-layer party → account → account site → site use model behind the #tca-layers quirk.
- Databricks Auto Loader (opens in new tab) — the documented cloud-storage ingestion path the extraction guide lands BICC files through.
- Databricks — Upsert into Delta with MERGE (opens in new tab) — the idempotent-upsert pattern behind the extraction guide's incremental section.