itemvendor
controlSubsidiary-scopedThe item sourcing sublist: one row per item, vendor and subsidiary, with the vendor's part code, preferred flag and purchase price.
Browser page name is itemVendor (label "Vendors"). This record exposes no internal id of its own — the grain is item + vendor + subsidiary. preferredvendor is what item.vendor mirrors.
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
10 fields · 3 key
10 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | item | Item (internal id) | NUMBER | Primary-key field |
| 2 | vendor | Vendor (internal id) | NUMBER | Primary-key field |
| 3 | subsidiary | Subsidiary (internal id) | NUMBER | Primary-key field |
| 4 | vendorcode | The vendor's own code for this item | VARCHAR | |
| 5 | preferredvendor | Preferred source for this item | VARCHAR | |
| 6 | purchaseprice | Purchase price | NUMBER | |
| 7 | vendorcost | Vendor cost | NUMBER | |
| 8 | vendorcostentered | Price as entered | NUMBER | |
| 9 | vendorcurrencyid | Currency of the vendor cost (internal id) | NUMBER | |
| 10 | schedule | Purchase price schedule (internal id) | NUMBER |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of itemvendor 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.
5 parameters not filled: <catalog>, <schema>, <subsidiary_id>, <item>, <vendor>
-- ============================================================
-- Table : itemvendor — The item sourcing sublist: one row per item, vendor and subsidiary, with the vendor's part code, preferred flag and purchase price.
-- Purpose: Column-selected read of itemvendor — auto-generated from field metadata
-- Grain : One row per item + vendor + subsidiary
-- 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.item AS "Item (internal id)",
t.vendor AS "Vendor (internal id)",
t.subsidiary AS "Subsidiary (internal id)",
t.vendorcode AS "The vendor's own code for this item",
t.preferredvendor AS "Preferred source for this item", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.purchaseprice AS "Purchase price",
t.vendorcost AS "Vendor cost",
t.vendorcostentered AS "Price as entered",
t.vendorcurrencyid AS "Currency of the vendor cost (internal id)",
t.schedule AS "Purchase price schedule (internal id)"
FROM <catalog>.<schema>.itemvendor t
WHERE
t.subsidiary = <subsidiary_id> -- OneWorld partition — see quirks guide #oneworld
-- AND t.item = <item>
-- AND t.vendor = <vendor>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.item;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 item.id = itemvendor.itemON itemvendor.vendor = vendor.idON itemvendor.subsidiary = subsidiary.id
More Items tables
- unitstypeThe units-of-measure header: one row per UOM family (weight, each, volume). The individual units and their conversion rates hang off the joined unitstypeuom record.
- unitstypeuomThe individual units inside a units-of-measure family: name, abbreviation, the base-unit marker and the conversion rate that turns this unit into the family's base unit.
- itemThe unified item master: one row for every item type — inventory, non-inventory, service, kit, assembly — discriminated by itemtype and subtype, carrying costing, pricing, planning parameters and global quantity rollups.
- itemmemberThe generic component record — analytics label "Members": one row per member line of a parent item, carrying the component, its parent, the quantity, the component yield and the effective/obsolete revision window. It is the shape the kit, item-group and assembly member records all repeat.
- itemsubsidiarymapThe item-to-subsidiary bridge: two columns, one row per item per subsidiary the item is available in. This is the item side of OneWorld scoping.