pricing
controlThe item price matrix: one row per item, price level, currency, quantity break and sale unit, carrying the unit price. This is where a price actually lives.
the grain is item + pricelevel + currency + quantity + saleunit — joining item to this record without pinning a price level (and, in a OneWorld account, a currency) multiplies every item row by its entire price matrix.
Its key column is internalid, not id. customer is populated only on customer-specific price rows; on the general levels it is empty, so an inner join through it silently reduces the matrix to negotiated prices only. An alternate, thinner price record exists in the analytics catalog and is deliberately not cataloged here — this is the richer of the two.
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 · 6 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | internalid | Internal ID | NUMBER | Primary-key field |
| 2 | item | Item (internal id) | NUMBER | Primary-key field |
| 3 | pricelevel | Price level (internal id) — pin this or the matrix multiplies | NUMBER | Primary-key field |
| 4 | currency | Currency (internal id) | NUMBER | Primary-key field |
| 5 | quantity | Quantity break this price applies from (internal id) | NUMBER | Primary-key field |
| 6 | saleunit | Sale unit the price is stated in (internal id) | NUMBER | Primary-key field |
| 7 | unitprice | Unit price | NUMBER | |
| 8 | customer | Customer (internal id) — populated only on customer-specific price rows | NUMBER | |
| 9 | assignedpricelevel | Price level was assigned rather than derived | VARCHAR |
Field provenance: hand-curated. 6 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of pricing 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.
3 parameters not filled: <catalog>, <schema>, <item>
-- ============================================================
-- Table : pricing — The item price matrix: one row per item, price level, currency, quantity break and sale unit, carrying the unit price. This is where a price actually lives.
-- Purpose: Column-selected read of pricing — auto-generated from field metadata
-- Grain : One row per internalid + item + pricelevel + currency + quantity + saleunit
-- Caution: the grain is item + pricelevel + currency + quantity + saleunit — joining item to this record without pinning a price level (and, in a OneWorld account, a currency) multiplies every item row by its entire price matrix.
-- 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.internalid AS "Internal ID",
t.item AS "Item (internal id)",
t.pricelevel AS "Price level (internal id) — pin this or the matrix multiplies",
t.currency AS "Currency (internal id)",
t.quantity AS "Quantity break this price applies from (internal id)",
t.saleunit AS "Sale unit the price is stated in (internal id)",
t.unitprice AS "Unit price",
t.customer AS "Customer (internal id) — populated only on customer-specific price rows",
t.assignedpricelevel AS "Price level was assigned rather than derived" -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
FROM <catalog>.<schema>.pricing t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.item = <item>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.internalid;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 pricing.item = item.idON pricing.pricelevel = pricelevel.idON pricing.currency = currency.idON pricing.customer = entity.idON pricing.saleunit = unitstypeuom.internalid
More Pricing tables
- pricinggroupThe pricing-group list: four columns naming the groups items are bucketed into for group-level price rules.
- quantitypricingscheduleVolume-break pricing schedules: one row per schedule, naming the base discount, the unit the breaks are counted in, and whether the discount applies marginally or to the whole order.
- termThe payment-terms master: one row per terms code with the whole date-driven rule set behind it — days till net due, discount percentage and expiry, day-of-month due, and the installment schedule columns.
- pricelevelThe price-level list: one row per level (base price, online price, a customer tier), each with the markup or discount percentage that defines it.