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. A searchable reference for Oracle Fusion Cloud SCM tables, fields, and relationships, built for supply chain and analytics practitioners landing Fusion data in a lakehouse — with the extract data store (PVO) and OTBI subject area for each table, and a quirks guide for the SaaS data path, the business-unit striping shift, item-org striping, and date-effective tables.
Free & ungated · docs release 25D · Last verified August 2026
Coverage is building out module by module — 3 of 11 so far.
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.
- Verification: field names, keys, and structural facts are curated against each table's own page in Oracle's Tables and Views books (docs release 25D); extract data stores and subject areas are checked against the BICC and OTBI books, and every description is original wording. Last verified August 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
- 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
- EGP_ITEM_CAT_ASSIGNMENTSThe item-to-category assignment — one row per item, organization, catalog (category set), and category; the bridge every category rollup crosses
- 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
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.
Fusion Cloud is SaaS — the tables are real and documented, but data leaves only through BICC extracts, OTBI, BIP, or REST.
BICC CSV headers are ViewObject attribute names (InventoryItemId), not table columns (INVENTORY_ITEM_ID) — map names back before modeling.
ORG_ID on Fusion tables is the business unit, not the EBS operating unit — the same column name changed meaning in the migration.
Items repeat per inventory organization with a master org defined in setup, and extended attributes live in EGO extensible flexfields.
_F tables carry one row per effectivity window (EFFECTIVE_START_DATE / EFFECTIVE_END_DATE) — filter to the current row or joins multiply.
Getting Fusion data into your lakehouse
Every table page carries an Extract access panel naming the BICC extract data store (PVO) and the OTBI subject areas that reach the table, with provenance links into Oracle’s own books — and each module page rolls those up into an extraction map. A full extraction guide covering the BICC → object storage → Databricks path ships in a later release.
Start with the #no-sql quirk →Browse 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
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.
- Tables and Views for SCM (25D) — 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 (25D) — GL ledgers and code combinations, and the business units view.
- Tables and Views for HCM — the date-effective HR organization master every org id resolves to.
- Tables and Views for Common Features (25D) — FND_LOOKUP_VALUES and its physical _B/_TL base pair.
- Creating a Business Intelligence Cloud Extract — the BICC extract mechanics behind the #no-sql and #pvo-drift quirks and the incremental watermark caveat.
- Extract Data Stores for SCM (26B) — the PVO data-store keys behind every entry in the extract map.
- Extract Data Stores for Financials (26B) — the GL and business-unit PVO keys behind the foundation extract-map entries.
- Subject Areas for Transactional Business Intelligence in SCM (26B) — the OTBI subject-area names shown in the extract map, spelled exactly as Oracle documents them.