Skip to content
Fusion Reference

INV_SECONDARY_INVENTORIES

Product: INVmasterPer inventory org

The subinventory master — each row a named section of stock within an organization (stores, staging, receiving, rejects) with its asset/expense nature, tracking and reservability controls, and replenishment source

Identity
Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
Notes

The name column is SECONDARY_INVENTORY_NAME (VARCHAR2(10)) — other tables reference it as SUBINVENTORY_CODE, so the join pairs those two names plus ORGANIZATION_ID. Flag columns (ASSET_INVENTORY, QUANTITY_TRACKED, RESERVABLE_TYPE) are NUMBER codes, not Y/N characters. Translated descriptions live on INV_SECONDARY_INVENTORIES_TL (not yet cataloged).

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.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.ScmExtractAM.InvBiccExtractAM.InventorySubinventoryExtractPVO
    OTBI: Inventory Organization Real Time

    Keyed on OrganizationId + SecondaryInventoryName, mirroring the subinventory master's key. OTBI exposure is browse-only inside the organization subject area (no Inventory - prefix on that name).

    Oracle data-store documentation (opens in new tab)

Fields

16 fields · 2 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1SECONDARY_INVENTORY_NAMEThe subinventory code — other tables reference it as SUBINVENTORY_CODEVARCHAR2
Key
2ORGANIZATION_IDOwning inventory org — the other half of the keyNUMBER
Key
3DESCRIPTIONSubinventory description (untranslated copy)VARCHAR2
4ASSET_INVENTORYAsset vs expense subinventory — a NUMBER code, not Y/NNUMBER
5QUANTITY_TRACKEDWhether on-hand is tracked here — a NUMBER codeNUMBER
6AVAILABILITY_TYPEWhether stock here nets and is availableNUMBER
7RESERVABLE_TYPEWhether hard reservations are allowedNUMBER
8INVENTORY_ATP_CODEInclude in ATP or notNUMBER
9LOCATOR_TYPELocator control level for the subinventoryVARCHAR2
10PICKING_ORDERPick-sequencing priorityNUMBER
11DISABLE_DATEWhen the subinventory stops being usableDATE
12SOURCE_TYPEReplenishment source type (inventory vs supplier)VARCHAR2
13SOURCE_ORGANIZATION_IDReplenishment source orgNUMBER
14SOURCE_SUBINVENTORYReplenishment source subinventoryVARCHAR2
15STATUS_IDMaterial status id of the subinventoryNUMBER
16SUBINVENTORY_TYPEStorage vs receiving subinventoryVARCHAR2

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of INV_SECONDARY_INVENTORIES 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>, <SECONDARY_INVENTORY_NAME>, <watermark>

-- ============================================================
-- Table  : INV_SECONDARY_INVENTORIES — The subinventory master — each row a named section of stock within an organization (stores, staging, receiving, rejects) with its asset/expense nature, tracking and reservability controls, and replenishment source
-- Purpose: Column-selected read of INV_SECONDARY_INVENTORIES — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + SECONDARY_INVENTORY_NAME
-- 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.SECONDARY_INVENTORY_NAME AS "The subinventory code — other tables reference it as SUBINVENTORY_CODE",
  t.ORGANIZATION_ID AS "Owning inventory org — the other half of the key",
  t.DESCRIPTION AS "Subinventory description (untranslated copy)",
  t.ASSET_INVENTORY AS "Asset vs expense subinventory — a NUMBER code, not Y/N",
  t.QUANTITY_TRACKED AS "Whether on-hand is tracked here — a NUMBER code",
  t.AVAILABILITY_TYPE AS "Whether stock here nets and is available",
  t.RESERVABLE_TYPE AS "Whether hard reservations are allowed",
  t.INVENTORY_ATP_CODE AS "Include in ATP or not",
  t.LOCATOR_TYPE AS "Locator control level for the subinventory",
  t.PICKING_ORDER AS "Pick-sequencing priority",
  t.DISABLE_DATE AS "When the subinventory stops being usable",
  t.SOURCE_TYPE AS "Replenishment source type (inventory vs supplier)",
  t.SOURCE_ORGANIZATION_ID AS "Replenishment source org",
  t.SOURCE_SUBINVENTORY AS "Replenishment source subinventory",
  t.STATUS_ID AS "Material status id of the subinventory",
  t.SUBINVENTORY_TYPE AS "Storage vs receiving subinventory"
FROM <catalog>.<schema>.INV_SECONDARY_INVENTORIES t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.SECONDARY_INVENTORY_NAME = '<SECONDARY_INVENTORY_NAME>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.SECONDARY_INVENTORY_NAME;

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_MATERIAL_TXNSINV_SECONDARY_INVENTORIESforeign key · N:1
    ON INV_MATERIAL_TXNS.SUBINVENTORY_CODE = INV_SECONDARY_INVENTORIES.SECONDARY_INVENTORY_NAME AND INV_MATERIAL_TXNS.ORGANIZATION_ID = INV_SECONDARY_INVENTORIES.ORGANIZATION_ID
  • INV_ONHAND_QUANTITIES_DETAILINV_SECONDARY_INVENTORIESforeign key · N:1
    ON INV_ONHAND_QUANTITIES_DETAIL.SUBINVENTORY_CODE = INV_SECONDARY_INVENTORIES.SECONDARY_INVENTORY_NAME AND INV_ONHAND_QUANTITIES_DETAIL.ORGANIZATION_ID = INV_SECONDARY_INVENTORIES.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
  • INV_SECONDARY_INVENTORIESINV_ORG_PARAMETERSforeign key · N:1
    ON INV_SECONDARY_INVENTORIES.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • INV_ITEM_LOCATIONSINV_SECONDARY_INVENTORIESforeign key · N:1
    ON INV_ITEM_LOCATIONS.SUBINVENTORY_CODE = INV_SECONDARY_INVENTORIES.SECONDARY_INVENTORY_NAME AND INV_ITEM_LOCATIONS.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.