Skip to content
NetSuite Reference

itemmember

control

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.

Module: ItemsNo partition column
Grain note

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

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.

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.

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
2parentitemThe kit, group or assembly this line belongs to (internal id)NUMBER
3itemComponent item (internal id)NUMBER
4linenumberLine id within the parentNUMBER
5quantityMember quantityNUMBER
6bomquantityBOM quantity — the manufacturing quantity, not the member quantityNUMBER
7memberunitUnit of measure as TEXT — not a unit id, so it cannot be joinedVARCHAR
8componentyieldComponent yield percentageNUMBER
9itemsourceHow the component is sourced (internal id)NUMBER
10effectivedateDate this member line takes effectDATE
The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed
11obsoletedateDate this member line goes obsoleteDATE
12effectiverevisionEffective revision (internal id)NUMBER
13obsoleterevisionObsolete revision (internal id)NUMBER
14vsoedeliveredRevenue-allocation flag: default as deliveredVARCHAR
15vsoedeferralRevenue-allocation deferral rule (internal id)NUMBER
16vsoepermitdiscountRevenue-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.

Query parameters

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.

Join details

  • itemmemberitemforeign key · N:1
    ON itemmember.item = item.id
  • itemmemberitemforeign key · N:1
    ON itemmember.parentitem = item.id

Browse more Items tables

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