itemlocationconfiguration
masterSubsidiary-scopedLocation-scopedThe per-item-per-location planning parameters: reorder point, safety stock, preferred stock level, lead times, demand and supply time fences, supply type and the lot-sizing rule that decides how much a planned order covers.
no lastmodifieddate — full refresh. This record holds the POLICY at an item/location; the balances at the same grain are on inventoryitemlocations, and the two records overlap on reorder point and safety stock — decide which one your models read and stay on it.
Browser page name is itemLocationConfiguration. Thirty-nine columns on the page, curated here to the planning parameters; the store-pickup, cycle-count and cost-history columns are left out as adjacent rather than analytic. Both anchors are active — item, location and subsidiary are scalar page-attested selects. The supply-type, lot-sizing, periods-of-supply and demand-source pointers all resolve to small decode records this catalog does not carry, so they land as ids; see quirks #display-values.
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
20 fields · 3 key
20 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | item | Item (internal id) | NUMBER | Primary-key field |
| 3 | location | Location (internal id) | NUMBER | Primary-key field |
| 4 | subsidiary | Subsidiary (internal id) | NUMBER | |
| 5 | supplytype | How supply is created for this item at this site (internal id) | NUMBER | |
| 6 | demandsource | What demand the plan is driven from (internal id) | NUMBER | |
| 7 | reorderpoint | Reorder point | NUMBER | |
| 8 | safetystocklevel | Safety stock level | NUMBER | |
| 9 | preferredstocklevel | Preferred stock level | NUMBER | |
| 10 | leadtime | Replenishment lead time in days | NUMBER | |
| 11 | atpleadtime | Lead time used for available-to-promise | NUMBER | |
| 12 | buildtime | Work-order lead time | NUMBER | |
| 13 | demandtimefence | Demand time fence in days | NUMBER | |
| 14 | supplytimefence | Planning time fence in days | NUMBER | |
| 15 | supplylotsizingmethod | Lot-sizing rule (internal id) — decides how much a planned order covers | NUMBER | |
| 16 | fixedlotsize | Fixed lot size | NUMBER | |
| 17 | periodiclotsizetype | Periods-of-supply type (internal id) | NUMBER | |
| 18 | periodiclotsizedays | Periods-of-supply increment in days | NUMBER | |
| 19 | iswip | Item is work in process at this site | VARCHAR | |
| 20 | cost | Standard cost at this site | NUMBER |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemlocationconfiguration 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>, <subsidiary_id>, <location_id>, <id>, <item>
-- ============================================================
-- Table : itemlocationconfiguration — The per-item-per-location planning parameters: reorder point, safety stock, preferred stock level, lead times, demand and supply time fences, supply type and the lot-sizing rule that decides how much a planned order covers.
-- Purpose: Column-selected read of itemlocationconfiguration — auto-generated from field metadata
-- Grain : One row per id + item + location
-- Caution: no lastmodifieddate — full refresh. This record holds the POLICY at an item/location; the balances at the same grain are on inventoryitemlocations, and the two records overlap on reorder point and safety stock — decide which one your models read and stay on it.
-- 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.location AS "Location (internal id)",
t.subsidiary AS "Subsidiary (internal id)",
t.supplytype AS "How supply is created for this item at this site (internal id)",
t.demandsource AS "What demand the plan is driven from (internal id)",
t.reorderpoint AS "Reorder point",
t.safetystocklevel AS "Safety stock level",
t.preferredstocklevel AS "Preferred stock level",
t.leadtime AS "Replenishment lead time in days",
t.atpleadtime AS "Lead time used for available-to-promise",
t.buildtime AS "Work-order lead time",
t.demandtimefence AS "Demand time fence in days",
t.supplytimefence AS "Planning time fence in days",
t.supplylotsizingmethod AS "Lot-sizing rule (internal id) — decides how much a planned order covers",
t.fixedlotsize AS "Fixed lot size",
t.periodiclotsizetype AS "Periods-of-supply type (internal id)",
t.periodiclotsizedays AS "Periods-of-supply increment in days",
t.iswip AS "Item is work in process at this site", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.cost AS "Standard cost at this site"
FROM <catalog>.<schema>.itemlocationconfiguration t
WHERE
t.subsidiary = <subsidiary_id> -- OneWorld partition — see quirks guide #oneworld
AND t.location = <location_id> -- location scope — see quirks guide #oneworld
-- AND t.id = <id>
-- 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.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 itemlocationconfiguration.item = item.idON itemlocationconfiguration.location = location.idON itemlocationconfiguration.subsidiary = subsidiary.id
More Planning tables
- itemsupplyplanThe supply plan header: one row per item and location the planning engine produced supply for, with the unit of measure the plan is stated in.
- itemsupplyplanorderThe planned orders a supply plan generated: one row per proposed order, with its type, order and receipt dates, quantity, source location and whether it has been turned into a real document yet.
- itemsupplyplanplanningmessageThe planning engine's action messages: one row per recommendation — reschedule in, reschedule out, cancel — with the message text, the quantity, the dates involved and the order it refers to.
- itemdemandplanThe demand plan header: one row per item and location being planned, with the projection method, interval, duration and start date that define the plan's time buckets.
- itemdemandplandemandplandetailThe demand plan's time buckets: one row per bucket, with its row number, start and end dates and the planned quantity.