Skip to content
Fusion Reference

INV_ONHAND_QUANTITIES_SUMMARY

Product: INVtransactionPer inventory org

Pre-aggregated on-hand at the item + location grain, maintained automatically in step with the detail table — the ready-made balance EBS never had

Identity
Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
EBS equivalents (1)
Notes

Every write to the detail table updates the matching summary row, so this is current state, not history. The balance column is plainly named QUANTITY (primary UOM), with stocking- and secondary-UOM twins; LAST_QUANTITY holds the prior balance before the last change.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Fields

16 fields · 1 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1ONHAND_SUMMARY_IDSurrogate key of the summary rowNUMBER
Key
2INVENTORY_ITEM_IDItem on handNUMBER
3ORGANIZATION_IDInventory org holding the stockNUMBER
4SUBINVENTORY_CODESubinventory holding the stockVARCHAR2
5LOCATOR_IDLocator holding the stockNUMBER
6LOT_NUMBERLot, when lot-controlledVARCHAR2
7QUANTITYConsolidated on-hand in the primary UOM — the ready-made balanceNUMBER
8PRIMARY_UOM_CODEPrimary UOM of the balanceVARCHAR2
9SECONDARY_UOM_QUANTITYBalance converted to the secondary UOMNUMBER
10SECONDARY_UOM_CODESecondary UOMVARCHAR2
11STOCKING_UOM_QUANTITYBalance converted to the stocking UOMNUMBER
12STOCKING_UOM_CODEStocking UOMVARCHAR2
13LAST_QUANTITYPrior balance (primary UOM) before the last changeNUMBER
14LOT_CONTROL_CODEItem lot-control setting denormalized onto the rowNUMBER
15SERIAL_NUMBER_CONTROL_CODEItem serial-control setting denormalized onto the rowNUMBER
16REVISION_QTY_CONTROL_CODEItem revision-control setting denormalized onto the rowNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of INV_ONHAND_QUANTITIES_SUMMARY on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <ONHAND_SUMMARY_ID>, <watermark>

-- ============================================================
-- Table  : INV_ONHAND_QUANTITIES_SUMMARY — Pre-aggregated on-hand at the item + location grain, maintained automatically in step with the detail table — the ready-made balance EBS never had
-- Purpose: Column-selected read of INV_ONHAND_QUANTITIES_SUMMARY — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + ONHAND_SUMMARY_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.ONHAND_SUMMARY_ID AS "Surrogate key of the summary row",
  t.INVENTORY_ITEM_ID AS "Item on hand",
  t.ORGANIZATION_ID AS "Inventory org holding the stock",
  t.SUBINVENTORY_CODE AS "Subinventory holding the stock",
  t.LOCATOR_ID AS "Locator holding the stock",
  t.LOT_NUMBER AS "Lot, when lot-controlled",
  t.QUANTITY AS "Consolidated on-hand in the primary UOM — the ready-made balance",
  t.PRIMARY_UOM_CODE AS "Primary UOM of the balance",
  t.SECONDARY_UOM_QUANTITY AS "Balance converted to the secondary UOM",
  t.SECONDARY_UOM_CODE AS "Secondary UOM",
  t.STOCKING_UOM_QUANTITY AS "Balance converted to the stocking UOM",
  t.STOCKING_UOM_CODE AS "Stocking UOM",
  t.LAST_QUANTITY AS "Prior balance (primary UOM) before the last change",
  t.LOT_CONTROL_CODE AS "Item lot-control setting denormalized onto the row",
  t.SERIAL_NUMBER_CONTROL_CODE AS "Item serial-control setting denormalized onto the row",
  t.REVISION_QTY_CONTROL_CODE AS "Item revision-control setting denormalized onto the row"
FROM <catalog>.<schema>.INV_ONHAND_QUANTITIES_SUMMARY t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.ONHAND_SUMMARY_ID = <ONHAND_SUMMARY_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.ONHAND_SUMMARY_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • INV_ONHAND_QUANTITIES_SUMMARYEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON INV_ONHAND_QUANTITIES_SUMMARY.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND INV_ONHAND_QUANTITIES_SUMMARY.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • INV_ONHAND_QUANTITIES_SUMMARYINV_SECONDARY_INVENTORIESforeign key · N:1
    ON INV_ONHAND_QUANTITIES_SUMMARY.SUBINVENTORY_CODE = INV_SECONDARY_INVENTORIES.SECONDARY_INVENTORY_NAME AND INV_ONHAND_QUANTITIES_SUMMARY.ORGANIZATION_ID = INV_SECONDARY_INVENTORIES.ORGANIZATION_ID

Browse more Inventory tables

More Inventory tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.