transactionshippingaddress
transactionThe shipping address as it was stamped on a document: the formatted block plus the parsed lines, city, state, zip, country and phone, keyed by the address key the transaction header points at.
this is the address AT THE TIME OF THE DOCUMENT, not the customer's current address — never substitute the entity record's address for it when restating history.
Browser page name is transactionShippingAddress (label "Address"). Its key column is nkey and the browser page leaves that column unlabeled; transaction.shippingaddress is what points at it. `override` marks the rows a user edited away from the entity default. transactionbillingaddress is the identical twin on the billing side.
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
14 fields · 1 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | nkey | Address key — what transaction.shippingaddress resolves to | NUMBER | Primary-key field |
| 2 | addressee | Addressee | VARCHAR | |
| 3 | attention | Attention line | VARCHAR | |
| 4 | addrtext | The whole address as one formatted block | VARCHAR | |
| 5 | addr1 | Address line 1 | VARCHAR | |
| 6 | addr2 | Address line 2 | VARCHAR | |
| 7 | addr3 | Address line 3 | VARCHAR | |
| 8 | city | City | VARCHAR | |
| 9 | state | State or province as text | VARCHAR | |
| 10 | dropdownstate | State or province (internal id) | NUMBER | |
| 11 | zip | Postal code | VARCHAR | |
| 12 | country | Country (internal id) | NUMBER | |
| 13 | addrphone | Phone | VARCHAR | |
| 14 | override | Address was edited away from the entity default on this document | VARCHAR |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of transactionshippingaddress 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 : transactionshippingaddress — The shipping address as it was stamped on a document: the formatted block plus the parsed lines, city, state, zip, country and phone, keyed by the address key the transaction header points at.
-- Purpose: Column-selected read of transactionshippingaddress — auto-generated from field metadata
-- Grain : One row per nkey
-- Caution: this is the address AT THE TIME OF THE DOCUMENT, not the customer's current address — never substitute the entity record's address for it when restating history.
-- 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.nkey AS "Address key — what transaction.shippingaddress resolves to",
t.addressee AS "Addressee",
t.attention AS "Attention line",
t.addrtext AS "The whole address as one formatted block",
t.addr1 AS "Address line 1",
t.addr2 AS "Address line 2",
t.addr3 AS "Address line 3",
t.city AS "City",
t.state AS "State or province as text",
t.dropdownstate AS "State or province (internal id)",
t.zip AS "Postal code",
t.country AS "Country (internal id)",
t.addrphone AS "Phone",
t.override AS "Address was edited away from the entity default on this document" -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
FROM <catalog>.<schema>.transactionshippingaddress 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.nkey;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 transaction.shippingaddress = transactionshippingaddress.nkey
More Transactions tables
- nexttransactionlinelinkThe forward line-link table: one row per line-to-line link travelling downstream — a sales-order line to its fulfillment line, a fulfillment line to its invoice line — with the link type and linked amount.
- paymentmethodThe payment-method list: one row per method a document can carry, with its type and the GL account payments land in.
- previoustransactionlinelinkThe backward line-link table: the exact mirror of nexttransactionlinelink, travelling upstream from an invoice line to the sales-order line it originated on.
- salesinvoicedThe invoiced-sales analytics view: the ordered twin plus a posting period, one row per invoiced transaction line with amount, quantity and the estimated cost and gross-profit columns.
- salesorderedThe ordered-sales analytics view: one row per sales transaction line with the amount, quantity, estimated cost and estimated gross profit already computed, alongside the customer, item, and the class/department/location segments.
- transactionThe document header for every transaction type NetSuite records — sales orders, purchase orders, fulfillments, receipts, invoices, journals — separated by the type column rather than by table.