Skip to content
NetSuite Reference

inventoryitemlocations

masterLocation-scoped

The 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.

Module: InventoryLocation-scoped
Grain note

on-hand VALUE (onhandvaluemli) is a costing output, not a transaction sum — under Average, FIFO, LIFO or Standard costing you cannot reconstruct it by summing transaction amounts; see quirks #costing.

Notes

Browser page name is inventoryItemLocations (label "Locations"). Grain is item + location and it exposes no id of its own. This is the table inventory dashboards should read, not the rollup columns on item.

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.

Structural facts — how the record is partitioned, not a trap by itself

Subsidiary-scoped
The record carries a subsidiary column 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 location column — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way.

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field, and the T/F chip marks a check-box column Connect returns as a 'T'/'F' string.

Fields

18 fields · 2 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1itemItem (internal id)NUMBER
Primary-key field
2locationLocation (internal id)NUMBER
Primary-key field
3quantityonhandQuantity on hand at this locationNUMBER
4quantityavailableQuantity availableNUMBER
5quantitycommittedQuantity committed to ordersNUMBER
6quantitybackorderedQuantity back orderedNUMBER
7quantityintransitQuantity in transitNUMBER
8quantityonorderQuantity on orderNUMBER
9reorderpointReorder pointNUMBER
10preferredstocklevelPreferred stock levelNUMBER
11safetystocklevelSafety stock levelNUMBER
12onhandvaluemliOn-hand value — a costing output, not a transaction sumNUMBER
13averagecostmliAverage cost at this locationNUMBER
14lastpurchasepricemliLast purchase price at this locationNUMBER
15costStandard costNUMBER
16leadtimeReplenishment lead time in daysNUMBER
17lastinvtcountdateLast cycle-count dateDATE
18nextinvtcountdateNext scheduled count dateDATE

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the Connect-landed copy of inventoryitemlocations 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.

Query parameters

4 parameters not filled: <catalog>, <schema>, <location_id>, <item>

-- ============================================================
-- Table  : inventoryitemlocations — The 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.
-- Purpose: Column-selected read of inventoryitemlocations — auto-generated from field metadata
-- Grain  : One row per item + location
-- Caution: on-hand VALUE (onhandvaluemli) is a costing output, not a transaction sum — under Average, FIFO, LIFO or Standard costing you cannot reconstruct it by summing transaction amounts; see quirks #costing.
-- 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.item AS "Item (internal id)",
  t.location AS "Location (internal id)",
  t.quantityonhand AS "Quantity on hand at this location",
  t.quantityavailable AS "Quantity available",
  t.quantitycommitted AS "Quantity committed to orders",
  t.quantitybackordered AS "Quantity back ordered",
  t.quantityintransit AS "Quantity in transit",
  t.quantityonorder AS "Quantity on order",
  t.reorderpoint AS "Reorder point",
  t.preferredstocklevel AS "Preferred stock level",
  t.safetystocklevel AS "Safety stock level",
  t.onhandvaluemli AS "On-hand value — a costing output, not a transaction sum",
  t.averagecostmli AS "Average cost at this location",
  t.lastpurchasepricemli AS "Last purchase price at this location",
  t.cost AS "Standard cost",
  t.leadtime AS "Replenishment lead time in days",
  t.lastinvtcountdate AS "Last cycle-count date",
  t.nextinvtcountdate AS "Next scheduled count date"
FROM <catalog>.<schema>.inventoryitemlocations t
WHERE
  t.location = <location_id>  -- location scope — see quirks guide #oneworld
  -- AND t.item = <item>
  -- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.item;

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

  • inventoryitemlocationsitemforeign key · N:1
    ON inventoryitemlocations.item = item.id
  • inventoryitemlocationslocationforeign key · N:1
    ON inventoryitemlocations.location = location.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 or NetSuite. NetSuite is a registered trademark of Oracle and/or its affiliates.