Skip to content
NetSuite Reference

department

master

The department segment: one row per department, hierarchical through parent, used to stripe transaction lines for reporting.

Module: FoundationNo partition column
Grain note

`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

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.

Structural facts — how the record is partitioned, not a trap by itself

Subsidiary-scoped
The record carries a subsidiary column 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 location column — an org segment in NetSuite before it is a warehouse — and the generated SQL anchors it the same way.

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field, and the T/F chip marks a check-box column Connect returns as a 'T'/'F' string.

Fields

8 fields · 1 key

8 fields.

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2nameDepartment nameVARCHAR
3fullnameFull hierarchical nameVARCHAR
4parentParent department (internal id)NUMBER
5subsidiarySubsidiaries — MULTISELECT, not a scalar foreign keyVARCHAR
6isinactiveInactiveVARCHAR
7includechildrenSubdepartments roll upVARCHAR
8externalidExternal IDVARCHAR

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.

Query parameters

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

  • budgetsdepartmentforeign key · N:1
    ON budgets.department = department.id

Browse more Foundation tables

More Foundation tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle or NetSuite. NetSuite is a registered trademark of Oracle and/or its affiliates.