inventoryassignment
transactionThe lot/serial detail line: one row per transaction line per inventory number, with the assigned quantity, bin and inventory status.
no expiration date on this record — it lives on the referenced inventorynumber, so any FEFO or shelf-life question needs that join.
Browser page name is inventoryAssignment. Seven columns; the quantity column is typed as a currency on the page but carries units. This is how a lot-tracked movement is tied back to the specific lot consumed.
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
7 fields · 4 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | transaction | Transaction (internal id) | NUMBER | Primary-key field |
| 3 | transactionline | Transaction line (internal id) | NUMBER | Primary-key field |
| 4 | inventorynumber | Lot or serial number assigned (internal id) | NUMBER | Primary-key field |
| 5 | quantity | Assigned quantity | NUMBER | |
| 6 | bin | Bin (internal id) | NUMBER | |
| 7 | inventorystatus | Inventory status (internal id) | NUMBER |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of inventoryassignment 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>, <transaction>, <transactionline>, <inventorynumber>
-- ============================================================
-- Table : inventoryassignment — The lot/serial detail line: one row per transaction line per inventory number, with the assigned quantity, bin and inventory status.
-- Purpose: Column-selected read of inventoryassignment — auto-generated from field metadata
-- Grain : One row per id + transaction + transactionline + inventorynumber
-- Caution: no expiration date on this record — it lives on the referenced inventorynumber, so any FEFO or shelf-life question needs that join.
-- 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.transaction AS "Transaction (internal id)",
t.transactionline AS "Transaction line (internal id)",
t.inventorynumber AS "Lot or serial number assigned (internal id)",
t.quantity AS "Assigned quantity",
t.bin AS "Bin (internal id)",
t.inventorystatus AS "Inventory status (internal id)"
FROM <catalog>.<schema>.inventoryassignment t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.transaction = <transaction>
-- AND t.transactionline = <transactionline>
-- AND t.inventorynumber = <inventorynumber>
-- 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 inventoryassignment.inventorynumber = inventorynumber.idON inventoryassignment.transaction = transaction.idON inventoryassignment.transactionline = transactionline.id
More Inventory tables
- 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.
- inventorynumberThe lot and serial master: one row per lot or serial number per item, with the expiration date and the quantity rollups for that number.