Skip to content
Fusion Reference

INV_SERIAL_NUMBERS

Product: INVmaster

The serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit, with manufacturing and shipping lifecycle dates

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

The org column is CURRENT_ORGANIZATION_ID — where the unit sits now, part of the primary key — so this catalog does not give the table the inventory-org anchor; filter CURRENT_ORGANIZATION_ID explicitly when you mean one org's serials. CURRENT_STATUS is the lifecycle state; PARENT_ITEM_ID/PARENT_SERIAL_NUMBER carry component genealogy.

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.InvSerialNumbersExtractPVO
    OTBI: Inventory - Inventory Balance Real Time

    Keyed on InventoryItemId + SerialNumber + CurrentOrganizationId, mirroring the serial master's key. In OTBI, serials surface as a dimension of the balance subject area.

    Oracle data-store documentation (opens in new tab)

Fields

15 fields · 3 key

15 fields.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1SERIAL_NUMBERThe serialized unit's numberVARCHAR2
Key
2INVENTORY_ITEM_IDItem the serial belongs toNUMBER
Key
3CURRENT_ORGANIZATION_IDOrg where the unit currently resides — part of the key, and NOT named ORGANIZATION_IDNUMBER
Key
4CURRENT_SUBINVENTORY_CODECurrent subinventory of the unitVARCHAR2
5CURRENT_LOCATOR_IDCurrent locator of the unitNUMBER
6CURRENT_STATUSLifecycle state (defined, in stores, issued…) — a VARCHAR2 code hereVARCHAR2
7STATUS_IDMaterial status id (distinct from the lifecycle state)NUMBER
8LOT_NUMBERLot the unit belongs to, if lot-controlledVARCHAR2
9REVISIONItem revision of the unitVARCHAR2
10INITIALIZATION_DATEWhen the serial was first initializedDATE
11COMPLETION_DATEManufacturing completion dateDATE
12SHIP_DATEWhen the unit shippedDATE
13WIP_ENTITY_IDWork order referenceNUMBER
14PARENT_ITEM_IDParent item for component genealogyNUMBER
15PARENT_SERIAL_NUMBERParent unit's serial in the genealogyVARCHAR2

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of INV_SERIAL_NUMBERS 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

6 parameters not filled: <catalog>, <schema>, <SERIAL_NUMBER>, <INVENTORY_ITEM_ID>, <CURRENT_ORGANIZATION_ID>, <watermark>

-- ============================================================
-- Table  : INV_SERIAL_NUMBERS — The serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit, with manufacturing and shipping lifecycle dates
-- Purpose: Column-selected read of INV_SERIAL_NUMBERS — auto-generated from field metadata
-- Grain  : One row per SERIAL_NUMBER + INVENTORY_ITEM_ID + CURRENT_ORGANIZATION_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.SERIAL_NUMBER AS "The serialized unit's number",
  t.INVENTORY_ITEM_ID AS "Item the serial belongs to",
  t.CURRENT_ORGANIZATION_ID AS "Org where the unit currently resides — part of the key, and NOT named ORGANIZATION_ID",
  t.CURRENT_SUBINVENTORY_CODE AS "Current subinventory of the unit",
  t.CURRENT_LOCATOR_ID AS "Current locator of the unit",
  t.CURRENT_STATUS AS "Lifecycle state (defined, in stores, issued…) — a VARCHAR2 code here",
  t.STATUS_ID AS "Material status id (distinct from the lifecycle state)",
  t.LOT_NUMBER AS "Lot the unit belongs to, if lot-controlled",
  t.REVISION AS "Item revision of the unit",
  t.INITIALIZATION_DATE AS "When the serial was first initialized",
  t.COMPLETION_DATE AS "Manufacturing completion date",
  t.SHIP_DATE AS "When the unit shipped",
  t.WIP_ENTITY_ID AS "Work order reference",
  t.PARENT_ITEM_ID AS "Parent item for component genealogy",
  t.PARENT_SERIAL_NUMBER AS "Parent unit's serial in the genealogy"
FROM <catalog>.<schema>.INV_SERIAL_NUMBERS t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.SERIAL_NUMBER = '<SERIAL_NUMBER>'
  -- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
  -- AND t.CURRENT_ORGANIZATION_ID = <CURRENT_ORGANIZATION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.SERIAL_NUMBER;

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_SERIAL_NUMBERSEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON INV_SERIAL_NUMBERS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND INV_SERIAL_NUMBERS.CURRENT_ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • INV_SERIAL_NUMBERSINV_LOT_NUMBERSforeign key · N:1
    ON INV_SERIAL_NUMBERS.LOT_NUMBER = INV_LOT_NUMBERS.LOT_NUMBER AND INV_SERIAL_NUMBERS.INVENTORY_ITEM_ID = INV_LOT_NUMBERS.INVENTORY_ITEM_ID AND INV_SERIAL_NUMBERS.CURRENT_ORGANIZATION_ID = INV_LOT_NUMBERS.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.