transactionshipment
transactionThe shipment satellite of a transaction: ship-from and ship-to addresses, ship method, shipping and handling rates, weight, and whether the shipment has been fulfilled.
Analytics label is "Shipment". This record is analytics-only — it is not exposed to SuiteScript or the legacy Connect schema — and its grain is uniquekey within a parent transaction (doc). shippingmethod here is TEXT, not a shipping-item id, so it cannot be joined to the shipitem record — decode it as a label or read the method from the document's own columns.
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
9 fields · 2 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | uniquekey | Shipment unique key | NUMBER | Primary-key field |
| 2 | doc | Parent transaction (internal id) | NUMBER | Primary-key field |
| 3 | shippingmethod | Ship via, as text | VARCHAR | |
| 4 | sourceaddress | Ship-from address, as text | VARCHAR | |
| 5 | destinationaddress | Ship-to address, as text | VARCHAR | |
| 6 | shippingrate | Shipping rate | NUMBER | |
| 7 | handlingrate | Handling rate | NUMBER | |
| 8 | weight | Shipment weight | NUMBER | |
| 9 | isfulfilledtransaction | Shipment has been fulfilled | VARCHAR |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of transactionshipment 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.
4 parameters not filled: <catalog>, <schema>, <uniquekey>, <doc>
-- ============================================================
-- Table : transactionshipment — The shipment satellite of a transaction: ship-from and ship-to addresses, ship method, shipping and handling rates, weight, and whether the shipment has been fulfilled.
-- Purpose: Column-selected read of transactionshipment — auto-generated from field metadata
-- Grain : One row per uniquekey + doc
-- 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.uniquekey AS "Shipment unique key",
t.doc AS "Parent transaction (internal id)",
t.shippingmethod AS "Ship via, as text",
t.sourceaddress AS "Ship-from address, as text",
t.destinationaddress AS "Ship-to address, as text",
t.shippingrate AS "Shipping rate",
t.handlingrate AS "Handling rate",
t.weight AS "Shipment weight",
t.isfulfilledtransaction AS "Shipment has been fulfilled" -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
FROM <catalog>.<schema>.transactionshipment t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.uniquekey = <uniquekey>
-- AND t.doc = <doc>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.uniquekey;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 transactionshipment.doc = transaction.id
More Transactions tables
- transactionshippingaddressThe 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.
- 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.