itemsupplyplanplanningmessage
transactionThe 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.
no lastmodifieddate — full refresh. messagecode is an integer with no published enumeration: group and filter on it if you like, but read the label from `message` rather than asserting what a code means.
Browser page name is ItemSupplyPlanPlanningmessage (label "Planning Message"). No internal id of its own, and no key is asserted — one plan raises many messages, so the plan column is a parent pointer rather than the grain. transactionid is an id pointer at the document the message is about — a spine row — but the page lists no join for it, so this catalog draws no edge and it is read as an id. The exception backlog every planner actually works from is this record filtered to the message codes their account uses.
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 message belongs to (internal id) — repeats once per message | NUMBER | |
| 2 | messagecode | Action code — an integer with no published enumeration | NUMBER | |
| 3 | message | Message text as the planner reads it | VARCHAR | |
| 4 | transactionid | Document the message is about (internal id) — read as an id, no page-attested join | NUMBER | |
| 5 | quantity | Quantity the message concerns | NUMBER | |
| 6 | receiptdate | Date on the message | DATE | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 7 | rescheduledate | Date the message recommends moving to | DATE | |
| 8 | creationdate | Date the message was generated | DATE |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemsupplyplanplanningmessage 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 : itemsupplyplanplanningmessage — The 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.
-- Purpose: Column-selected read of itemsupplyplanplanningmessage — auto-generated from field metadata
-- Grain : One row per record — see the Fields section for the full key
-- Caution: no lastmodifieddate — full refresh. messagecode is an integer with no published enumeration: group and filter on it if you like, but read the label from `message` rather than asserting what a code means.
-- 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 message belongs to (internal id) — repeats once per message",
t.messagecode AS "Action code — an integer with no published enumeration",
t.message AS "Message text as the planner reads it",
t.transactionid AS "Document the message is about (internal id) — read as an id, no page-attested join",
t.quantity AS "Quantity the message concerns",
t.receiptdate AS "Date on the message",
t.rescheduledate AS "Date the message recommends moving to",
t.creationdate AS "Date the message was generated"
FROM <catalog>.<schema>.itemsupplyplanplanningmessage t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.receiptdate >= DATE '<DATE_FROM>'
-- AND t.receiptdate <= 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 itemsupplyplanplanningmessage.itemsupplyplan = itemsupplyplan.id
More Planning tables
- 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.
- 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.