manufacturingcosttemplatecostdetail
masterThe 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.
no lastmodifieddate — full refresh. Two rate columns per row: runrate scales with time and fixedrate does not, so a costed operation adds them rather than choosing one.
Browser page name is ManufacturingCostTemplateCostDetail (label "Cost Detail"). It exposes no internal id, so the template plus the cost category is the practical grain. `item` here is the CHARGE item the cost posts against, not a component. The cost-category pointer targets a record this catalog does not carry, so it is read 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
5 fields · 2 key
5 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | manufacturingcosttemplate | Cost template this rate line belongs to (internal id) | NUMBER | Primary-key field |
| 2 | costcategory | Cost category (internal id) — points at a record this catalog does not carry | NUMBER | Primary-key field |
| 3 | item | Charge item the cost posts against (internal id) — not a component | NUMBER | |
| 4 | runrate | Rate that scales with run time | NUMBER | |
| 5 | fixedrate | Rate that does not scale with time | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of manufacturingcosttemplatecostdetail 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 : manufacturingcosttemplatecostdetail — The 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.
-- Purpose: Column-selected read of manufacturingcosttemplatecostdetail — auto-generated from field metadata
-- Grain : One row per manufacturingcosttemplate + costcategory
-- Caution: no lastmodifieddate — full refresh. Two rate columns per row: runrate scales with time and fixedrate does not, so a costed operation adds them rather than choosing one.
-- 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.manufacturingcosttemplate AS "Cost template this rate line belongs to (internal id)",
t.costcategory AS "Cost category (internal id) — points at a record this catalog does not carry",
t.item AS "Charge item the cost posts against (internal id) — not a component",
t.runrate AS "Rate that scales with run time",
t.fixedrate AS "Rate that does not scale with time"
FROM <catalog>.<schema>.manufacturingcosttemplatecostdetail 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.manufacturingcosttemplate;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 manufacturingcosttemplatecostdetail.manufacturingcosttemplate = manufacturingcosttemplate.idON manufacturingcosttemplatecostdetail.item = item.id
More Manufacturing tables
- 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.
- 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.