manufacturingroutingroutingstep
masterThe operation steps of a routing: one row per step, with its sequence, name, work center, cost template, run rate per unit and setup time.
no lastmodifieddate — full refresh. runrate is stated in MINUTES PER UNIT and setuptime in minutes per run: extended operation time is setuptime + runrate × quantity, not a single column.
Browser page name is manufacturingRoutingRoutingStep (label "Routing Steps") — note the doubled word; a record named for the singular step exists nowhere in the analytics catalog. It exposes no internal id of its own, so the routing plus the operation sequence is the practical key. Its edges are listed on the routing's page rather than its own. lagtype points at a key record this catalog does not carry, so read it as an id.
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 · 2 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | manufacturingrouting | Routing this step belongs to (internal id) | NUMBER | Primary-key field |
| 2 | operationsequence | Step sequence within the routing | NUMBER | Primary-key field |
| 3 | operationname | Operation name | VARCHAR | |
| 4 | manufacturingworkcenter | Work center the step runs at (internal id) — a group record, not a warehouse record | NUMBER | |
| 5 | manufacturingcosttemplate | Cost template the step is costed with (internal id) | NUMBER | |
| 6 | runrate | Run rate in minutes per unit | NUMBER | |
| 7 | setuptime | Setup time in minutes per run | NUMBER | |
| 8 | lagamount | Lag before the next step | NUMBER | |
| 9 | lagtype | Lag type (internal id) — points at a key record this catalog does not carry | NUMBER | |
| 10 | lagunits | Lag units as text | VARCHAR |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of manufacturingroutingroutingstep 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.
2 parameters not filled: <catalog>, <schema>
-- ============================================================
-- Table : manufacturingroutingroutingstep — The operation steps of a routing: one row per step, with its sequence, name, work center, cost template, run rate per unit and setup time.
-- Purpose: Column-selected read of manufacturingroutingroutingstep — auto-generated from field metadata
-- Grain : One row per manufacturingrouting + operationsequence
-- Caution: no lastmodifieddate — full refresh. runrate is stated in MINUTES PER UNIT and setuptime in minutes per run: extended operation time is setuptime + runrate × quantity, not a single column.
-- 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.manufacturingrouting AS "Routing this step belongs to (internal id)",
t.operationsequence AS "Step sequence within the routing",
t.operationname AS "Operation name",
t.manufacturingworkcenter AS "Work center the step runs at (internal id) — a group record, not a warehouse record",
t.manufacturingcosttemplate AS "Cost template the step is costed with (internal id)",
t.runrate AS "Run rate in minutes per unit",
t.setuptime AS "Setup time in minutes per run",
t.lagamount AS "Lag before the next step",
t.lagtype AS "Lag type (internal id) — points at a key record this catalog does not carry",
t.lagunits AS "Lag units as text"
FROM <catalog>.<schema>.manufacturingroutingroutingstep t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.manufacturingrouting;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 manufacturingroutingroutingstep.manufacturingrouting = manufacturingrouting.idON manufacturingroutingroutingstep.manufacturingcosttemplate = manufacturingcosttemplate.id
More Manufacturing tables
- 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.
- 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.