bomrevision
masterA dated version of a bill of materials: one row per revision, with the effective start and end dates that decide which component list is in force on a given day.
no lastmodifieddate on this record — full-refresh the revisions. effectivestartdate and effectiveenddate are a validity WINDOW, so an as-of read is a BETWEEN against a chosen date, never a max() on the revision id.
Browser page name is bomRevision. This is the record that makes a BOM date-effective, and the one a component list hangs off. The page names the component child under an alias — the same record cataloged here as bomrevisioncomponent — so a join written against the alias name will not resolve in the landed copy.
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
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | billofmaterials | BOM this revision belongs to (internal id) | NUMBER | |
| 3 | name | Revision name | VARCHAR | |
| 4 | effectivestartdate | First day this revision is in force | DATE | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 5 | effectiveenddate | Last day this revision is in force | DATE | |
| 6 | memo | Memo | VARCHAR | |
| 7 | isinactive | Inactive | VARCHAR | |
| 8 | createddate | Date created | TIMESTAMP | |
| 9 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of bomrevision 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 : bomrevision — A dated version of a bill of materials: one row per revision, with the effective start and end dates that decide which component list is in force on a given day.
-- Purpose: Column-selected read of bomrevision — auto-generated from field metadata
-- Grain : One row per id
-- Caution: no lastmodifieddate on this record — full-refresh the revisions. effectivestartdate and effectiveenddate are a validity WINDOW, so an as-of read is a BETWEEN against a chosen date, never a max() on the revision id.
-- 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.billofmaterials AS "BOM this revision belongs to (internal id)",
t.name AS "Revision name",
t.effectivestartdate AS "First day this revision is in force",
t.effectiveenddate AS "Last day this revision is in force",
t.memo AS "Memo",
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>.bomrevision t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.effectivestartdate >= DATE '<DATE_FROM>'
-- AND t.effectivestartdate <= 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
ON bomrevision.billofmaterials = bom.idON bomrevisioncomponent.bomrevision = bomrevision.id
More Manufacturing tables
- bomrevisioncomponentThe BOM line: one row per component on a revision, with the quantity, the BOM quantity, the component yield, the unit and how the component is sourced.
- manufacturingcosttemplateThe manufacturing cost template: a named set of labor, machine and overhead rates a routing step is costed with, owned by a subsidiary.
- manufacturingcosttemplatecostdetailThe rate lines of a cost template: one row per cost category, with the charge item, the run rate and the fixed rate that category contributes.
- manufacturingoperationtaskThe operation task on a work order: one row per step being executed, with its work center, cost template, scheduled dates, input and completed quantities, and both the standard and the actual run and setup times.
- manufacturingroutingThe routing header: one row per routing for an item, tied to the bill of materials it is run against, with a default marker and the subsidiary that owns it.
- manufacturingroutingroutingstepThe operation steps of a routing: one row per step, with its sequence, name, work center, cost template, run rate per unit and setup time.