Skip to content
NetSuite Reference

subsidiary

master

The OneWorld legal-entity master: one row per subsidiary, hierarchical through parent, each carrying its own base currency, country and fiscal calendar.

Module: FoundationNo partition column
Notes

The subsidiary id is what every OneWorld partition filter resolves to, but the column that carries it lives on transactionline, not on the transaction header. currency here is the subsidiary's BASE currency — the currency transactionaccountingline states its amounts in.

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.
Used in the library
Cross-ERP guides

Business record

The business record this table holds, with Oracle’s own documentation for it: the Analytics Browser page that defines the queryable fields, and the current-release Records Browser page that corroborates it.

Fields

16 fields · 1 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2nameSubsidiary nameVARCHAR
3fullnameFull hierarchical nameVARCHAR
4legalnameLegal nameVARCHAR
5parentParent subsidiary (internal id)NUMBER
6currencyBase currency (internal id)NUMBER
7countryCountry (internal id)NUMBER
8stateState or province textVARCHAR
9dropdownstateState or province (internal id)NUMBER
10editionNetSuite edition (internal id)NUMBER
11fiscalcalendarFiscal calendar (internal id)NUMBER
12languagelocaleLanguage locale (internal id)NUMBER
13iseliminationElimination subsidiaryVARCHAR
14isinactiveInactiveVARCHAR
15tranprefixDocument number prefixVARCHAR
16externalidExternal IDVARCHAR

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the Connect-landed copy of subsidiary 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  : subsidiary — The OneWorld legal-entity master: one row per subsidiary, hierarchical through parent, each carrying its own base currency, country and fiscal calendar.
-- Purpose: Column-selected read of subsidiary — auto-generated from field metadata
-- Grain  : One row per id
-- 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 "Subsidiary name",
  t.fullname AS "Full hierarchical name",
  t.legalname AS "Legal name",
  t.parent AS "Parent subsidiary (internal id)",
  t.currency AS "Base currency (internal id)",
  t.country AS "Country (internal id)",
  t.state AS "State or province text",
  t.dropdownstate AS "State or province (internal id)",
  t.edition AS "NetSuite edition (internal id)",
  t.fiscalcalendar AS "Fiscal calendar (internal id)",
  t.languagelocale AS "Language locale (internal id)",
  t.iselimination AS "Elimination subsidiary",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.isinactive AS "Inactive",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.tranprefix AS "Document number prefix",
  t.externalid AS "External ID"
FROM <catalog>.<schema>.subsidiary 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

  • transactionlinesubsidiaryforeign key · N:1
    ON transactionline.subsidiary = subsidiary.id
  • customersubsidiaryrelationshipsubsidiaryforeign key · N:1
    ON customersubsidiaryrelationship.subsidiary = subsidiary.id
  • vendorsubsidiaryrelationshipsubsidiaryforeign key · N:1
    ON vendorsubsidiaryrelationship.subsidiary = subsidiary.id
  • itemvendorsubsidiaryforeign key · N:1
    ON itemvendor.subsidiary = subsidiary.id
  • itemsubsidiarymapsubsidiaryforeign key · N:1
    ON itemsubsidiarymap.subsidiary = subsidiary.id
  • fulfillmentrequestsubsidiaryforeign key · N:1
    ON fulfillmentrequest.subsidiary = subsidiary.id
  • subsidiarycurrencyforeign key · N:1
    ON subsidiary.currency = currency.id
  • subsidiarysubsidiaryforeign key · N:1
    ON subsidiary1.parent = subsidiary2.id
  • consolidatedexchangeratesubsidiaryforeign key · N:1
    ON consolidatedexchangerate.fromsubsidiary = subsidiary.id
  • consolidatedexchangeratesubsidiaryforeign key · N:1
    ON consolidatedexchangerate.tosubsidiary = subsidiary.id
  • manufacturingroutingsubsidiaryforeign key · N:1
    ON manufacturingrouting.subsidiary = subsidiary.id
  • manufacturingcosttemplatesubsidiaryforeign key · N:1
    ON manufacturingcosttemplate.subsidiary = subsidiary.id
  • itemdemandplansubsidiaryforeign key · N:1
    ON itemdemandplan.subsidiary = subsidiary.id
  • itemsupplyplansubsidiaryforeign key · N:1
    ON itemsupplyplan.subsidiary = subsidiary.id
  • itemlocationconfigurationsubsidiaryforeign key · N:1
    ON itemlocationconfiguration.subsidiary = subsidiary.id
  • budgetssubsidiaryforeign key · N:1
    ON budgets.subsidiary = subsidiary.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.