Skip to content
NetSuite Reference

itemdemandplan

transactionSubsidiary-scopedLocation-scoped

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

Module: PlanningSubsidiary- and location-scoped
Grain note

no lastmodifieddate on this record — full-refresh the plans. The quantities are NOT here: they are the bucket rows on itemdemandplandemandplandetail, and projectioninterval is what tells you how wide each bucket is.

Notes

Browser page name is itemDemandPlan. Both anchors are active: item, location and subsidiary are all scalar selects with page-attested joins, so this is one of the few records a site-level planning filter works on directly. The month pointer targets a key record this catalog does not carry.

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.
Used in the library

Fields

16 fields · 1 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2itemItem being planned (internal id)NUMBER
3locationLocation being planned (internal id)NUMBER
4subsidiarySubsidiary (internal id)NUMBER
5unitsUnit of measure (internal id) — resolves to unitstypeuom.internalidNUMBER
6demandplanidPlan identifier as displayedVARCHAR
7demandplantypePlan type (internal id)NUMBER
8projectionmethodForecast method as textVARCHAR
9projectionintervalBucket width as text — what the detail rows are stated inVARCHAR
10projectiondurationNumber of buckets projectedNUMBER
11projectionstartdateFirst day of the projectionDATE
The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed
12analysisdurationLength of history the projection was fitted onNUMBER
13alternatesourceitemItem whose history stands in for this one, as textVARCHAR
14demandplancalendartypeCalendar the plan is viewed on, as textVARCHAR
15memoMemoVARCHAR
16externalidExternal IDVARCHAR

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

7 parameters not filled: <catalog>, <schema>, <subsidiary_id>, <location_id>, <id>, <DATE_FROM>, <DATE_TO>

-- ============================================================
-- Table  : itemdemandplan — The 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.
-- Purpose: Column-selected read of itemdemandplan — auto-generated from field metadata
-- Grain  : One row per id
-- Caution: no lastmodifieddate on this record — full-refresh the plans. The quantities are NOT here: they are the bucket rows on itemdemandplandemandplandetail, and projectioninterval is what tells you how wide each bucket is.
-- 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.demandplanid AS "Plan identifier as displayed",
  t.demandplantype AS "Plan type (internal id)",
  t.projectionmethod AS "Forecast method as text",
  t.projectioninterval AS "Bucket width as text — what the detail rows are stated in",
  t.projectionduration AS "Number of buckets projected",
  t.projectionstartdate AS "First day of the projection",
  t.analysisduration AS "Length of history the projection was fitted on",
  t.alternatesourceitem AS "Item whose history stands in for this one, as text",
  t.demandplancalendartype AS "Calendar the plan is viewed on, as text",
  t.memo AS "Memo",
  t.externalid AS "External ID"
FROM <catalog>.<schema>.itemdemandplan 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.projectionstartdate >= DATE '<DATE_FROM>'
  -- AND t.projectionstartdate <= 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

  • itemdemandplanitemforeign key · N:1
    ON itemdemandplan.item = item.id
  • itemdemandplanlocationforeign key · N:1
    ON itemdemandplan.location = location.id
  • itemdemandplansubsidiaryforeign key · N:1
    ON itemdemandplan.subsidiary = subsidiary.id
  • itemdemandplanunitstypeuomforeign key · N:1
    ON itemdemandplan.units = unitstypeuom.internalid
  • itemdemandplandemandplandetailitemdemandplanforeign key · N:1
    ON itemdemandplandemandplandetail.itemdemandplan = itemdemandplan.id

Browse more Planning tables

More Planning 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.