department
masterThe department segment: one row per department, hierarchical through parent, used to stripe transaction lines for reporting.
`subsidiary` on this record is a MULTISELECT (a department can serve several subsidiaries) — it is NOT an equality filter, so no subsidiary anchor is emitted here. The normalized link is a separate department-to-subsidiary map record, which this catalog does not carry.
hasSubsidiary is false by design: the `subsidiary` column is authored below for completeness, but it holds several ids at once, so `subsidiary = <id>` would silently drop every department shared across subsidiaries.
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
8 fields · 1 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | name | Department name | VARCHAR | |
| 3 | fullname | Full hierarchical name | VARCHAR | |
| 4 | parent | Parent department (internal id) | NUMBER | |
| 5 | subsidiary | Subsidiaries — MULTISELECT, not a scalar foreign key | VARCHAR | |
| 6 | isinactive | Inactive | VARCHAR | |
| 7 | includechildren | Subdepartments roll up | VARCHAR | |
| 8 | externalid | External ID | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of department 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 : department — The department segment: one row per department, hierarchical through parent, used to stripe transaction lines for reporting.
-- Purpose: Column-selected read of department — auto-generated from field metadata
-- Grain : One row per id
-- Caution: `subsidiary` on this record is a MULTISELECT (a department can serve several subsidiaries) — it is NOT an equality filter, so no subsidiary anchor is emitted here. The normalized link is a separate department-to-subsidiary map record, which this catalog does not carry.
-- 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 "Department name",
t.fullname AS "Full hierarchical name",
t.parent AS "Parent department (internal id)",
t.subsidiary AS "Subsidiaries — MULTISELECT, not a scalar foreign key",
t.isinactive AS "Inactive", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.includechildren AS "Subdepartments roll up", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.externalid AS "External ID"
FROM <catalog>.<schema>.department 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 budgets.department = department.id
More Foundation tables
- locationThe location master: stocking sites, stores and virtual locations, hierarchical through parent, carrying the inventory-availability, bin and warehouse-management switches that decide how stock behaves at a site.
- subsidiaryThe OneWorld legal-entity master: one row per subsidiary, hierarchical through parent, each carrying its own base currency, country and fiscal calendar.
- accountingbookThe multi-book accounting register: one row per book, with isprimary marking the book most analytics should anchor on.
- accountingperiodThe period calendar: one row per period, hierarchical through parent, with year/quarter/adjustment flags and the close and lock state that governs what can still post.
- classificationThe class segment: one row per class, hierarchical through parent. The analytics id is classification; the NetSuite UI calls it "Class".
- consolidatedexchangeratePeriod consolidation rates: one row per accounting book, posting period and from/to subsidiary pair, carrying the current, average and historical rate flavors side by side.