itemsupplyplan
transactionSubsidiary-scopedLocation-scopedThe 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.
no lastmodifieddate — full refresh. Seven columns only: the planned orders are on itemsupplyplanorder and the action messages on itemsupplyplanplanningmessage.
Browser page name is itemSupplyPlan. The demand plan's counterpart, with the same anchor pattern — item, location and subsidiary are scalar page-attested selects, so both anchors are active.
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 · 1 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | item | Item being planned (internal id) | NUMBER | |
| 3 | location | Location being planned (internal id) | NUMBER | |
| 4 | subsidiary | Subsidiary (internal id) | NUMBER | |
| 5 | units | Unit of measure (internal id) — resolves to unitstypeuom.internalid | NUMBER | |
| 6 | memo | Memo | VARCHAR | |
| 7 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemsupplyplan 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.
5 parameters not filled: <catalog>, <schema>, <subsidiary_id>, <location_id>, <id>
-- ============================================================
-- Table : itemsupplyplan — The 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.
-- Purpose: Column-selected read of itemsupplyplan — auto-generated from field metadata
-- Grain : One row per id
-- Caution: no lastmodifieddate — full refresh. Seven columns only: the planned orders are on itemsupplyplanorder and the action messages on itemsupplyplanplanningmessage.
-- 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 being planned (internal id)",
t.location AS "Location being planned (internal id)",
t.subsidiary AS "Subsidiary (internal id)",
t.units AS "Unit of measure (internal id) — resolves to unitstypeuom.internalid",
t.memo AS "Memo",
t.externalid AS "External ID"
FROM <catalog>.<schema>.itemsupplyplan 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>
-- 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 itemsupplyplan.item = item.idON itemsupplyplan.location = location.idON itemsupplyplan.subsidiary = subsidiary.idON itemsupplyplan.units = unitstypeuom.internalidON itemsupplyplanorder.itemsupplyplan = itemsupplyplan.idON itemsupplyplanplanningmessage.itemsupplyplan = itemsupplyplan.id
More Planning tables
- 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.
- itemlocationconfigurationThe 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.