INV_SERIAL_NUMBERS
Product: INVmasterThe serial number master — definition and current position (status, org, subinventory, locator, lot) of every serialized unit, with manufacturing and shipping lifecycle dates
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.
- 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 withINVENTORY_ITEM_IDon 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_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin 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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.InvSerialNumbersExtractPVOOTBI: 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.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | SERIAL_NUMBER | The serialized unit's number | VARCHAR2 | Key |
| 2 | INVENTORY_ITEM_ID | Item the serial belongs to | NUMBER | Key |
| 3 | CURRENT_ORGANIZATION_ID | Org where the unit currently resides — part of the key, and NOT named ORGANIZATION_ID | NUMBER | Key |
| 4 | CURRENT_SUBINVENTORY_CODE | Current subinventory of the unit | VARCHAR2 | |
| 5 | CURRENT_LOCATOR_ID | Current locator of the unit | NUMBER | |
| 6 | CURRENT_STATUS | Lifecycle state (defined, in stores, issued…) — a VARCHAR2 code here | VARCHAR2 | |
| 7 | STATUS_ID | Material status id (distinct from the lifecycle state) | NUMBER | |
| 8 | LOT_NUMBER | Lot the unit belongs to, if lot-controlled | VARCHAR2 | |
| 9 | REVISION | Item revision of the unit | VARCHAR2 | |
| 10 | INITIALIZATION_DATE | When the serial was first initialized | DATE | |
| 11 | COMPLETION_DATE | Manufacturing completion date | DATE | |
| 12 | SHIP_DATE | When the unit shipped | DATE | |
| 13 | WIP_ENTITY_ID | Work order reference | NUMBER | |
| 14 | PARENT_ITEM_ID | Parent item for component genealogy | NUMBER | |
| 15 | PARENT_SERIAL_NUMBER | Parent unit's serial in the genealogy | VARCHAR2 |
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.
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
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_IDON 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
More Inventory tables
- INV_TRANSACTION_TYPES_BThe transaction type list — seeded and user-defined types, each mapping to the transaction action and source type that together classify material transactions
- INV_TRANSFER_ORDER_HEADERSTransfer order headers — the orchestration document for internal material moves within or between organizations, carrying the order number, originating process, and requisitioning business unit
- 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_TXN_REQUEST_HEADERSMovement request (move order) headers — the user-visible request number, type, status, and required date for requests to move material within an organization
- INV_TXN_REQUEST_LINESMovement request lines — each row requests moving a quantity of an item from a source to a destination subinventory (or account), individually statused, allocated (quantity detailed), and delivered
- INV_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the human-readable locator name, capacity limits, and pick sequencing