manufacturingoperationtask
transactionThe 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.
no lastmodifieddate — full refresh. The analytic hook is the PAIR of columns: runrate and setuptime are what the routing said, actualruntime and actualsetuptime are what happened. Compare them per step; do not average one across steps of different lengths.
Browser page name is manufacturingOperationTask. This is the one record in the catalog that points back at the spine: `workorder` holds the internal id of a transaction row, so it is the bridge between the manufacturing master data and the document; see quirks #work-orders. Its status column has no public value list, like the spine's — see quirks #status-codes. actualwork and remainingwork are typed as durations on the page rather than as plain numbers, and no public source states their unit, so they are landed as numbers and read alongside the minute-stated run and setup columns rather than added to them. The self-join that orders the steps and the predecessor and cost-detail children are page-listed but not cataloged here: they are scheduling plumbing, and the work center they name is an entity group, not a warehouse record.
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
19 fields · 1 key
19 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | workorder | Work order this task belongs to (internal id) — a row on the transaction spine | NUMBER | |
| 3 | operationsequence | Step sequence within the work order | NUMBER | |
| 4 | title | Task name — the column is title, not name | VARCHAR | |
| 5 | status | Task status (internal id) — no public value list; see quirks #status-codes | NUMBER | |
| 6 | manufacturingworkcenter | Work center the task runs at (internal id) — a group record, not a warehouse record | NUMBER | |
| 7 | manufacturingcosttemplate | Cost template the task is costed with (internal id) | NUMBER | |
| 8 | startdatetime | Scheduled start | TIMESTAMP | The record's primary analysis date — a real DATE/TIMESTAMP column, no conversion needed |
| 9 | enddate | Scheduled end | TIMESTAMP | |
| 10 | inputquantity | Quantity the task was given | NUMBER | |
| 11 | completedquantity | Quantity completed | NUMBER | |
| 12 | runrate | Standard run rate in minutes per unit — what the routing said | NUMBER | |
| 13 | setuptime | Standard setup time in minutes — what the routing said | NUMBER | |
| 14 | actualruntime | Actual run time in minutes — what happened | NUMBER | |
| 15 | actualsetuptime | Actual setup time in minutes — what happened | NUMBER | |
| 16 | estimatedwork | Estimated work for the task | NUMBER | |
| 17 | actualwork | Work recorded against the task — a duration on the page, with no stated unit | NUMBER | |
| 18 | remainingwork | Work still outstanding — a duration on the page, with no stated unit | NUMBER | |
| 19 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of manufacturingoperationtask 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 : manufacturingoperationtask — The 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.
-- Purpose: Column-selected read of manufacturingoperationtask — auto-generated from field metadata
-- Grain : One row per id
-- Caution: no lastmodifieddate — full refresh. The analytic hook is the PAIR of columns: runrate and setuptime are what the routing said, actualruntime and actualsetuptime are what happened. Compare them per step; do not average one across steps of different lengths.
-- 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.workorder AS "Work order this task belongs to (internal id) — a row on the transaction spine",
t.operationsequence AS "Step sequence within the work order",
t.title AS "Task name — the column is title, not name",
t.status AS "Task status (internal id) — no public value list; see quirks #status-codes",
t.manufacturingworkcenter AS "Work center the task runs at (internal id) — a group record, not a warehouse record",
t.manufacturingcosttemplate AS "Cost template the task is costed with (internal id)",
t.startdatetime AS "Scheduled start",
t.enddate AS "Scheduled end",
t.inputquantity AS "Quantity the task was given",
t.completedquantity AS "Quantity completed",
t.runrate AS "Standard run rate in minutes per unit — what the routing said",
t.setuptime AS "Standard setup time in minutes — what the routing said",
t.actualruntime AS "Actual run time in minutes — what happened",
t.actualsetuptime AS "Actual setup time in minutes — what happened",
t.estimatedwork AS "Estimated work for the task",
t.actualwork AS "Work recorded against the task — a duration on the page, with no stated unit",
t.remainingwork AS "Work still outstanding — a duration on the page, with no stated unit",
t.externalid AS "External ID"
FROM <catalog>.<schema>.manufacturingoperationtask t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.startdatetime >= TIMESTAMP '<DATE_FROM>'
-- AND t.startdatetime <= TIMESTAMP '<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 manufacturingoperationtask.workorder = transaction.idON manufacturingoperationtask.manufacturingcosttemplate = manufacturingcosttemplate.id
More Manufacturing tables
- 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.
- 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.