itemmember
controlThe generic component record — analytics label "Members": one row per member line of a parent item, carrying the component, its parent, the quantity, the component yield and the effective/obsolete revision window. It is the shape the kit, item-group and assembly member records all repeat.
both `item` and `parentitem` point at the item master, so a readable component list joins item TWICE under two aliases — one for the component, one for the parent.
Browser page name is itemMember. The per-type clones of this shape — the kit, item-group and assembly member records, all verified to exist — are deliberately not cataloged: the generic record covers the analytics need, the same verdict itemsubsidiarymap carries. memberunit is TEXT, not a unit id, so it cannot be joined to the units records; read it as a label. bomquantity and quantity are different numbers on the same row — the manufacturing quantity and the member quantity.
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
16 fields · 1 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | parentitem | The kit, group or assembly this line belongs to (internal id) | NUMBER | |
| 3 | item | Component item (internal id) | NUMBER | |
| 4 | linenumber | Line id within the parent | NUMBER | |
| 5 | quantity | Member quantity | NUMBER | |
| 6 | bomquantity | BOM quantity — the manufacturing quantity, not the member quantity | NUMBER | |
| 7 | memberunit | Unit of measure as TEXT — not a unit id, so it cannot be joined | VARCHAR | |
| 8 | componentyield | Component yield percentage | NUMBER | |
| 9 | itemsource | How the component is sourced (internal id) | NUMBER | |
| 10 | effectivedate | Date this member line takes effect | DATE | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 11 | obsoletedate | Date this member line goes obsolete | DATE | |
| 12 | effectiverevision | Effective revision (internal id) | NUMBER | |
| 13 | obsoleterevision | Obsolete revision (internal id) | NUMBER | |
| 14 | vsoedelivered | Revenue-allocation flag: default as delivered | VARCHAR | |
| 15 | vsoedeferral | Revenue-allocation deferral rule (internal id) | NUMBER | |
| 16 | vsoepermitdiscount | Revenue-allocation discount rule (internal id) | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemmember 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>, <id>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : itemmember — The generic component record — analytics label "Members": one row per member line of a parent item, carrying the component, its parent, the quantity, the component yield and the effective/obsolete revision window. It is the shape the kit, item-group and assembly member records all repeat.
-- Purpose: Column-selected read of itemmember — auto-generated from field metadata
-- Grain : One row per id
-- Caution: both `item` and `parentitem` point at the item master, so a readable component list joins item TWICE under two aliases — one for the component, one for the parent.
-- 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.parentitem AS "The kit, group or assembly this line belongs to (internal id)",
t.item AS "Component item (internal id)",
t.linenumber AS "Line id within the parent",
t.quantity AS "Member quantity",
t.bomquantity AS "BOM quantity — the manufacturing quantity, not the member quantity",
t.memberunit AS "Unit of measure as TEXT — not a unit id, so it cannot be joined",
t.componentyield AS "Component yield percentage",
t.itemsource AS "How the component is sourced (internal id)",
t.effectivedate AS "Date this member line takes effect",
t.obsoletedate AS "Date this member line goes obsolete",
t.effectiverevision AS "Effective revision (internal id)",
t.obsoleterevision AS "Obsolete revision (internal id)",
t.vsoedelivered AS "Revenue-allocation flag: default as delivered", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.vsoedeferral AS "Revenue-allocation deferral rule (internal id)",
t.vsoepermitdiscount AS "Revenue-allocation discount rule (internal id)"
FROM <catalog>.<schema>.itemmember t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.effectivedate >= DATE '<DATE_FROM>'
-- AND t.effectivedate <= 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.
More Items tables
- itemsubsidiarymapThe item-to-subsidiary bridge: two columns, one row per item per subsidiary the item is available in. This is the item side of OneWorld scoping.
- itemvendorThe item sourcing sublist: one row per item, vendor and subsidiary, with the vendor's part code, preferred flag and purchase price.
- unitstypeThe units-of-measure header: one row per UOM family (weight, each, volume). The individual units and their conversion rates hang off the joined unitstypeuom record.
- unitstypeuomThe individual units inside a units-of-measure family: name, abbreviation, the base-unit marker and the conversion rate that turns this unit into the family's base unit.
- itemThe unified item master: one row for every item type — inventory, non-inventory, service, kit, assembly — discriminated by itemtype and subtype, carrying costing, pricing, planning parameters and global quantity rollups.