manufacturingrouting
masterSubsidiary-scopedThe 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.
no lastmodifieddate — full refresh. `location` on this record is a MULTISELECT ("Locations") — a routing can be valid at several sites at once — so no location anchor is emitted; filtering it with `= <id>` would drop every multi-site routing.
Browser page name is manufacturingRouting. hasSubsidiary is true: `subsidiary` here is a scalar select with a page-attested join, unlike the multiselect on the BOM header. The operation steps live on manufacturingroutingroutingstep, and the work center each step runs at points at NetSuite's group record rather than at a warehouse record — work centers ARE entity groups, which is why no work-center table exists to catalog or to join.
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
11 fields · 1 key
11 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | name | Routing name | VARCHAR | |
| 3 | item | Item the routing produces (internal id) | NUMBER | |
| 4 | billofmaterials | BOM the routing is run against (internal id) | NUMBER | |
| 5 | subsidiary | Subsidiary (internal id) — a scalar select, unlike the BOM header's multiselect | NUMBER | |
| 6 | location | Locations the routing is valid at — MULTISELECT, not a scalar foreign key | VARCHAR | |
| 7 | isdefault | Default routing for the item | VARCHAR | |
| 8 | autocalculatelag | Lag between steps is calculated rather than entered | VARCHAR | |
| 9 | isinactive | Inactive | VARCHAR | |
| 10 | memo | Memo | CLOB | |
| 11 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of manufacturingrouting 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.
4 parameters not filled: <id>, <catalog>, <schema>, <subsidiary_id>
-- ============================================================
-- Table : manufacturingrouting — The 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.
-- Purpose: Column-selected read of manufacturingrouting — auto-generated from field metadata
-- Grain : One row per id
-- Caution: no lastmodifieddate — full refresh. `location` on this record is a MULTISELECT ("Locations") — a routing can be valid at several sites at once — so no location anchor is emitted; filtering it with `= <id>` would drop every multi-site routing.
-- 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 "Routing name",
t.item AS "Item the routing produces (internal id)",
t.billofmaterials AS "BOM the routing is run against (internal id)",
t.subsidiary AS "Subsidiary (internal id) — a scalar select, unlike the BOM header's multiselect",
t.location AS "Locations the routing is valid at — MULTISELECT, not a scalar foreign key",
t.isdefault AS "Default routing for the item", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.autocalculatelag AS "Lag between steps is calculated rather than entered", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.isinactive AS "Inactive", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.memo AS "Memo",
t.externalid AS "External ID"
FROM <catalog>.<schema>.manufacturingrouting t
WHERE
t.subsidiary = <subsidiary_id> -- OneWorld partition — see quirks guide #oneworld
-- 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 manufacturingrouting.item = item.idON manufacturingrouting.billofmaterials = bom.idON manufacturingrouting.subsidiary = subsidiary.idON manufacturingroutingroutingstep.manufacturingrouting = manufacturingrouting.id
More Manufacturing tables
- 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.
- bomrevisionA 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.
- 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.