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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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 →
Fields
15 fields · 3 key
| # | 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_NUMBERSon 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.
-- ============================================================
-- 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 partition column 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;6 parameters not filled: <catalog>, <schema>, <SERIAL_NUMBER>, <INVENTORY_ITEM_ID>, <CURRENT_ORGANIZATION_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. 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