bomrevisioncomponent
masterThe 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.
no lastmodifieddate — full refresh. `quantity` and `bomquantity` are different numbers on the same row (the member quantity and the manufacturing quantity, as on itemmember), and componentyield is a PERCENTAGE, so a gross requirement divides by it rather than multiplying.
Browser page name is bomRevisionComponent. Edges run to bomrevision, to the item master and to unitstypeuom — the three joins a readable component list needs. isoutsourcingcharge is typed as text on the page, not as a check box, so read it as a label rather than testing it for 'T'.
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
10 fields · 1 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | bomrevision | Revision this component line belongs to (internal id) | NUMBER | |
| 3 | item | Component item (internal id) | NUMBER | |
| 4 | quantity | Component quantity | NUMBER | |
| 5 | bomquantity | BOM quantity — the manufacturing quantity, not the member quantity | NUMBER | |
| 6 | componentyield | Component yield percentage — a gross requirement divides by it | NUMBER | |
| 7 | units | Unit of measure (internal id) — resolves to unitstypeuom.internalid | NUMBER | |
| 8 | itemsource | How the component is sourced (internal id) | NUMBER | |
| 9 | isoutsourcingcharge | Outsourcing charge marker — typed as TEXT on the page, not as a check box | VARCHAR | |
| 10 | description | Line description | CLOB |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of bomrevisioncomponent 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.
3 parameters not filled: <catalog>, <schema>, <id>
-- ============================================================
-- Table : bomrevisioncomponent — The 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.
-- Purpose: Column-selected read of bomrevisioncomponent — auto-generated from field metadata
-- Grain : One row per id
-- Caution: no lastmodifieddate — full refresh. `quantity` and `bomquantity` are different numbers on the same row (the member quantity and the manufacturing quantity, as on itemmember), and componentyield is a PERCENTAGE, so a gross requirement divides by it rather than multiplying.
-- 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.bomrevision AS "Revision this component line belongs to (internal id)",
t.item AS "Component item (internal id)",
t.quantity AS "Component quantity",
t.bomquantity AS "BOM quantity — the manufacturing quantity, not the member quantity",
t.componentyield AS "Component yield percentage — a gross requirement divides by it",
t.units AS "Unit of measure (internal id) — resolves to unitstypeuom.internalid",
t.itemsource AS "How the component is sourced (internal id)",
t.isoutsourcingcharge AS "Outsourcing charge marker — typed as TEXT on the page, not as a check box",
t.description AS "Line description"
FROM <catalog>.<schema>.bomrevisioncomponent 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
ON bomrevisioncomponent.bomrevision = bomrevision.idON bomrevisioncomponent.item = item.idON bomrevisioncomponent.units = unitstypeuom.internalid
More Manufacturing tables
- 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.
- bomThe 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.