inventorynumber
masterThe lot and serial master: one row per lot or serial number per item, with the expiration date and the quantity rollups for that number.
Analytics label is "Serial/Lot Number". Expiration date lives HERE, which is why shelf-life analysis joins from inventoryassignment back to this record rather than reading the assignment line alone.
What the badges mean
- master
- Data class: what the record holds — master data, transaction documents, control/configuration, or a documented convenience record. NetSuite has no product-family or schema axis, so this is the whole classification.
- Subsidiary-scoped
- The record carries a
subsidiarycolumn that partitions its rows, so the generated SQL anchors it. On a few records the column is a multiselect rather than a scalar foreign key — the table notes say which (see the quirks guide). - Location-scoped
- The record carries a
locationcolumn — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way. - View
- A documented convenience record rather than a stored one. Land the records it stands in for instead of assuming it extracts as-is — the table notes say where the rows actually live.
Structural facts — how the record is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
'T'/'F' string.Fields
10 fields · 2 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | item | Item (internal id) | NUMBER | Primary-key field |
| 3 | inventorynumber | The lot or serial number itself | VARCHAR | |
| 4 | expirationdate | Expiration date — the only place it is recorded | DATE | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 5 | quantityonhand | Quantity on hand for this number | NUMBER | |
| 6 | quantityavailable | Quantity available | NUMBER | |
| 7 | quantityintransit | Quantity in transit | NUMBER | |
| 8 | quantityonorder | Quantity on order | NUMBER | |
| 9 | memo | Memo | CLOB | |
| 10 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of inventorynumber on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. This record carries no modification stamp, and the snippet says so where the watermark would otherwise go. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
6 parameters not filled: <catalog>, <schema>, <id>, <item>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : inventorynumber — The lot and serial master: one row per lot or serial number per item, with the expiration date and the quantity rollups for that number.
-- Purpose: Column-selected read of inventorynumber — auto-generated from field metadata
-- Grain : One row per id + item
-- Notes : Auto-generated skeleton for NetSuite data landed in your lakehouse from a SuiteAnalytics Connect (or SuiteQL) extract — it never addresses live NetSuite. Identifiers are lowercase as NetSuite2.com renders them. Select-type columns hold numeric internal ids: BUILTIN.DF() display resolution exists only at extraction time, so decode ids by joining the landed list records; see quirks #display-values. Check-box columns arrive as 'T'/'F' strings; see quirks #tf-booleans.
-- ============================================================
SELECT
t.id AS "Internal ID",
t.item AS "Item (internal id)",
t.inventorynumber AS "The lot or serial number itself",
t.expirationdate AS "Expiration date — the only place it is recorded",
t.quantityonhand AS "Quantity on hand for this number",
t.quantityavailable AS "Quantity available",
t.quantityintransit AS "Quantity in transit",
t.quantityonorder AS "Quantity on order",
t.memo AS "Memo",
t.externalid AS "External ID"
FROM <catalog>.<schema>.inventorynumber t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.item = <item>
-- AND t.expirationdate >= DATE '<DATE_FROM>'
-- AND t.expirationdate <= DATE '<DATE_TO>'
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.id;Verified August 2026 · Analytics Browser 2021.1 · corroborated 2025.2
Select columns hold internal ids, not display text — see decoding display values.
Relationships
Diagram of 1-hop neighbors — join details below. Document-link edges are highlighted; they chain one document to the next and are the joins newcomers most often get wrong.
Join details
ON inventorynumber.item = item.idON inventoryassignment.inventorynumber = inventorynumber.id
More Inventory tables
- inventoryassignmentThe lot/serial detail line: one row per transaction line per inventory number, with the assigned quantity, bin and inventory status.
- inventoryitemlocationsThe per-item-per-location balance and policy record: on hand, available, committed, back-ordered and in-transit quantities alongside the reorder point, safety stock, lead times and the location's cost basis.