itemsupplyplanorder
transactionThe 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.
no lastmodifieddate — full refresh. ordercreated is the line between a proposal and a document: rows where it is 'T' have already been raised as real documents on the spine, so counting those as supply on order double-counts them; rows where it is 'F' exist only in the plan.
Browser page name is ItemSupplyPlanOrder (label "Orders"). No internal id of its own, and no key is asserted: one plan holds many planned orders and the page offers no attested discriminator beside the plan pointer, so the plan column is authored as a parent pointer rather than a grain column. ordertype separates a purchase proposal from a work-order or transfer proposal, and — like every other type column in this source — has no published value list; discover the values in your own account. sourcelocation is an id pointer at the site a transfer would come from; the page lists no join table of its own, so it is read as an id rather than joined, and the plan's own location is the anchored one.
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
8 fields
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | itemsupplyplan | Supply plan this order belongs to (internal id) — repeats once per planned order | NUMBER | |
| 2 | ordertype | Proposed order type (internal id) — no public value list | NUMBER | |
| 3 | ordernumber | Order number as displayed | VARCHAR | |
| 4 | orderdate | Date the order should be raised | DATE | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 5 | receiptdate | Date the supply is needed | DATE | |
| 6 | quantity | Proposed quantity | NUMBER | |
| 7 | sourcelocation | Site a transfer would come from (internal id) — read as an id, no page-attested join | NUMBER | |
| 8 | ordercreated | A real document has been raised for this proposal | VARCHAR |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemsupplyplanorder 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 : itemsupplyplanorder — The 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.
-- Purpose: Column-selected read of itemsupplyplanorder — auto-generated from field metadata
-- Grain : One row per record — see the Fields section for the full key
-- Caution: no lastmodifieddate — full refresh. ordercreated is the line between a proposal and a document: rows where it is 'T' have already been raised as real documents on the spine, so counting those as supply on order double-counts them; rows where it is 'F' exist only in the plan.
-- 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.itemsupplyplan AS "Supply plan this order belongs to (internal id) — repeats once per planned order",
t.ordertype AS "Proposed order type (internal id) — no public value list",
t.ordernumber AS "Order number as displayed",
t.orderdate AS "Date the order should be raised",
t.receiptdate AS "Date the supply is needed",
t.quantity AS "Proposed quantity",
t.sourcelocation AS "Site a transfer would come from (internal id) — read as an id, no page-attested join",
t.ordercreated AS "A real document has been raised for this proposal" -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
FROM <catalog>.<schema>.itemsupplyplanorder t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.orderdate >= DATE '<DATE_FROM>'
-- AND t.orderdate <= DATE '<DATE_TO>'
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
;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 itemsupplyplanorder.itemsupplyplan = itemsupplyplan.id
More Planning tables
- 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.
- 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.