itemdemandplandemandplandetail
transactionThe demand plan's time buckets: one row per bucket, with its row number, start and end dates and the planned quantity.
no lastmodifieddate — full refresh. Bucket WIDTH is a property of the parent plan (its projectioninterval), not of the row, so summing quantities across plans mixes weekly and monthly buckets in one number — group inside a plan, or convert deliberately.
Browser page name is ItemDemandPlanDemandplandetail (label "Demand"). No internal id of its own: the plan plus the row number is the grain, and the row number orders the buckets. The edge back to the header is listed on the header's page, not here.
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
5 fields · 2 key
5 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | itemdemandplan | Plan this bucket belongs to (internal id) | NUMBER | Primary-key field |
| 2 | demandrownumber | Bucket number within the plan | NUMBER | Primary-key field |
| 3 | startdate | First day of the bucket | DATE | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 4 | enddate | Last day of the bucket | DATE | |
| 5 | quantity | Planned demand quantity for the bucket | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemdemandplandemandplandetail 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.
4 parameters not filled: <catalog>, <schema>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : itemdemandplandemandplandetail — The demand plan's time buckets: one row per bucket, with its row number, start and end dates and the planned quantity.
-- Purpose: Column-selected read of itemdemandplandemandplandetail — auto-generated from field metadata
-- Grain : One row per itemdemandplan + demandrownumber
-- Caution: no lastmodifieddate — full refresh. Bucket WIDTH is a property of the parent plan (its projectioninterval), not of the row, so summing quantities across plans mixes weekly and monthly buckets in one number — group inside a plan, or convert deliberately.
-- 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.itemdemandplan AS "Plan this bucket belongs to (internal id)",
t.demandrownumber AS "Bucket number within the plan",
t.startdate AS "First day of the bucket",
t.enddate AS "Last day of the bucket",
t.quantity AS "Planned demand quantity for the bucket"
FROM <catalog>.<schema>.itemdemandplandemandplandetail t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.startdate >= DATE '<DATE_FROM>'
-- AND t.startdate <= 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.itemdemandplan;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 itemdemandplandemandplandetail.itemdemandplan = itemdemandplan.id
More Planning tables
- 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.
- 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.