Skip to content
NetSuite Reference

zone

masterLocation-scoped

The warehouse zone list: one row per pick zone at a location, with its name and description.

Notes

Warehouse-management feature-gated, like picktask. Six columns and no page-listed joins, so it ships with no edges — the location column is authored and anchored, but the bins and tasks that reference a zone are reached from their own records.

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

6 fields · 1 key

6 fields.

Table fields: position, field name, description, data type, and flags. 6 fields.
#FieldDescriptionTypeFlags
1idInternal IDNUMBER
Primary-key field
2nameZone nameVARCHAR
3descriptionDescriptionCLOB
4locationLocation the zone belongs to (internal id)NUMBER
5isinactiveInactiveVARCHAR
6externalidExternal IDVARCHAR

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the Connect-landed copy of zone 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

4 parameters not filled: <catalog>, <schema>, <location_id>, <id>

-- ============================================================
-- Table  : zone — The warehouse zone list: one row per pick zone at a location, with its name and description.
-- Purpose: Column-selected read of zone — 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 "Zone name",
  t.description AS "Description",
  t.location AS "Location the zone belongs to (internal id)",
  t.isinactive AS "Inactive",  -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
  t.externalid AS "External ID"
FROM <catalog>.<schema>.zone t
WHERE
  t.location = <location_id>  -- location scope — see quirks guide #oneworld
  -- 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.

Browse more Fulfillment & Logistics tables

More Fulfillment & Logistics 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.