Skip to content
NetSuite Reference

bom

master

The bill-of-materials header: one row per BOM, naming it and setting which assemblies, locations and subsidiaries it may be used on. The component lines live on the revision, not here.

Module: ManufacturingNo partition column
Grain note

this record exposes no lastmodifieddate — there is no watermark column here, so incremental extraction must full-refresh the BOM headers. And a BOM header holds no components: quantities live on bomrevisioncomponent, one revision down.

Notes

Browser page name is bom (label "Bill of Materials"). hasSubsidiary is false by design: `subsidiary` is a MULTISELECT (a BOM can be shared across subsidiaries), so `subsidiary = <id>` would silently drop every shared BOM — the location/department/classification verdict again. The availability columns are multiselects for the same reason and are authored for completeness only. One spelling to expect: the browser page's own field id for "Available For Subsidiaries" is availableforsubisidiaries, misspelled at source, and it is authored here exactly as Connect renders it. The page's only join targets a BOM-to-subsidiary map record this catalog does not carry, so this record ships with no edges of its own — the revision below is where the joins start.

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

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2nameBOM nameVARCHAR
3memoMemoVARCHAR
4legacybomforassemblyAssembly this BOM was migrated from (internal id)NUMBER
5usedonassemblyBOM is used on at least one assemblyVARCHAR
6usecomponentyieldComponent yield is applied when this BOM is explodedVARCHAR
7includechildrenAvailable to child subsidiariesVARCHAR
8availableforallassembliesUsable on every assemblyVARCHAR
9availableforalllocationsUsable at every locationVARCHAR
10restricttoassembliesAssemblies the BOM is restricted to — MULTISELECTVARCHAR
11restricttolocationsLocations the BOM is restricted to — MULTISELECTVARCHAR
12availableforlocationsLocations the BOM is available at — MULTISELECTVARCHAR
13availableforsubisidiariesSubsidiaries the BOM is available in — MULTISELECT, and the id is misspelled on the record page itselfVARCHAR
14subsidiarySubsidiaries — MULTISELECT, not a scalar foreign keyVARCHAR
15bomrevisionRevisions of this BOM — MULTISELECT; the queryable rows are on bomrevisionVARCHAR
16isinactiveInactiveVARCHAR
17createddateDate createdTIMESTAMP
18externalidExternal IDVARCHAR

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the Connect-landed copy of bom 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

3 parameters not filled: <catalog>, <schema>, <id>

-- ============================================================
-- Table  : bom — The bill-of-materials header: one row per BOM, naming it and setting which assemblies, locations and subsidiaries it may be used on. The component lines live on the revision, not here.
-- Purpose: Column-selected read of bom — auto-generated from field metadata
-- Grain  : One row per id
-- Caution: this record exposes no lastmodifieddate — there is no watermark column here, so incremental extraction must full-refresh the BOM headers. And a BOM header holds no components: quantities live on bomrevisioncomponent, one revision down.
-- 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.name AS "BOM name",
  t.memo AS "Memo",
  t.legacybomforassembly AS "Assembly this BOM was migrated from (internal id)",
  t.usedonassembly AS "BOM is used on at least one assembly",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.usecomponentyield AS "Component yield is applied when this BOM is exploded",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.includechildren AS "Available to child subsidiaries",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.availableforallassemblies AS "Usable on every assembly",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.availableforalllocations AS "Usable at every location",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.restricttoassemblies AS "Assemblies the BOM is restricted to — MULTISELECT",
  t.restricttolocations AS "Locations the BOM is restricted to — MULTISELECT",
  t.availableforlocations AS "Locations the BOM is available at — MULTISELECT",
  t.availableforsubisidiaries AS "Subsidiaries the BOM is available in — MULTISELECT, and the id is misspelled on the record page itself",
  t.subsidiary AS "Subsidiaries — MULTISELECT, not a scalar foreign key",
  t.bomrevision AS "Revisions of this BOM — MULTISELECT; the queryable rows are on bomrevision",
  t.isinactive AS "Inactive",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.createddate AS "Date created",
  t.externalid AS "External ID"
FROM <catalog>.<schema>.bom t
WHERE
  1 = 1  -- no partition column on this record; the filters below are optional
  -- AND t.id = <id>
  -- 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

  • bomrevisionbomforeign key · N:1
    ON bomrevision.billofmaterials = bom.id
  • manufacturingroutingbomforeign key · N:1
    ON manufacturingrouting.billofmaterials = bom.id

Browse more Manufacturing tables

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