customer
masterThe customer master: identity, status, terms, credit control and the entity-level balance rollups, plus the sales-history date stamps.
the balance columns here are entity-level rollups — PER-SUBSIDIARY receivables live on customersubsidiaryrelationship, and in a OneWorld account that is the number finance means.
There is no plain subsidiary column on this record; representingsubsidiary is the intercompany representation, not the customer's owning subsidiary. Join through customersubsidiaryrelationship for the real customer-to-subsidiary edge.
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.Business record
The business record this table holds, with Oracle’s own documentation for it: the Analytics Browser page that defines the queryable fields, and the current-release Records Browser page that corroborates it.
- Customercustomer
Fields
19 fields · 1 key
19 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | id | Internal ID | NUMBER | Primary-key field |
| 2 | entityid | Entity ID | VARCHAR | |
| 3 | entitytitle | Customer ID as displayed | VARCHAR | |
| 4 | altname | Customer name | VARCHAR | |
| 5 | companyname | Company name | VARCHAR | |
| 6 | isperson | Individual rather than a company | VARCHAR | |
| 7 | isinactive | Inactive | VARCHAR | |
| 8 | datecreated | Date created | TIMESTAMP | |
| 9 | lastmodifieddate | Last modified — the incremental watermark | TIMESTAMP | |
| 10 | parent | Parent customer (internal id) | NUMBER | |
| 11 | currency | Customer currency (internal id) | NUMBER | |
| 12 | terms | Payment terms (internal id) | NUMBER | |
| 13 | category | Customer category (internal id) | NUMBER | |
| 14 | pricelevel | Default price level (internal id) | NUMBER | |
| 15 | entitystatus | Customer status (internal id) | NUMBER | |
| 16 | creditlimit | Credit limit | NUMBER | |
| 17 | oncredithold | On credit hold | VARCHAR | |
| 18 | balancesearch | Entity-level balance — per-subsidiary balances live on customersubsidiaryrelationship | NUMBER | |
| 19 | representingsubsidiary | Subsidiary this customer represents for intercompany (internal id) | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of customer on Databricks — dates are real DATE/TIMESTAMP columns and need no conversion, and the partition anchors are already in place. The lastmodifieddate watermark is in place too. 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>, <id>, <watermark>
-- ============================================================
-- Table : customer — The customer master: identity, status, terms, credit control and the entity-level balance rollups, plus the sales-history date stamps.
-- Purpose: Column-selected read of customer — auto-generated from field metadata
-- Grain : One row per id
-- Caution: the balance columns here are entity-level rollups — PER-SUBSIDIARY receivables live on customersubsidiaryrelationship, and in a OneWorld account that is the number finance means.
-- 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.entityid AS "Entity ID",
t.entitytitle AS "Customer ID as displayed",
t.altname AS "Customer name",
t.companyname AS "Company name",
t.isperson AS "Individual rather than a company", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.isinactive AS "Inactive", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.datecreated AS "Date created",
t.lastmodifieddate AS "Last modified — the incremental watermark",
t.parent AS "Parent customer (internal id)",
t.currency AS "Customer currency (internal id)",
t.terms AS "Payment terms (internal id)",
t.category AS "Customer category (internal id)",
t.pricelevel AS "Default price level (internal id)",
t.entitystatus AS "Customer status (internal id)",
t.creditlimit AS "Credit limit",
t.oncredithold AS "On credit hold", -- 'T'/'F' string — compare = 'T', or CAST via CASE; see quirks #tf-booleans
t.balancesearch AS "Entity-level balance — per-subsidiary balances live on customersubsidiaryrelationship",
t.representingsubsidiary AS "Subsidiary this customer represents for intercompany (internal id)"
FROM <catalog>.<schema>.customer t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- AND t.id = <id>
-- AND t.lastmodifieddate >= TIMESTAMP '<watermark>' -- inserts and updates only — deletes never appear here; diff deletedrecord, which is itself blind to line-level deletes (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.
Join details
ON entity.customer = customer.idON customer.id = customersubsidiaryrelationship.entityON customer.currency = currency.idON customer.terms = term.id
More Entities tables
- customersubsidiaryrelationshipThe OneWorld customer bridge: one row per customer per subsidiary the customer is shared with, carrying that subsidiary's receivable, deposit and unbilled-order balances.
- entityThe entity supertype: one row for every customer, vendor, employee, partner, contact, project and group, with pointer columns to the concrete record and a type discriminator.
- vendorThe vendor master: identity, terms, incoterm, credit limit and payables balances in both the vendor's primary currency and the base currency.
- vendorsubsidiaryrelationshipThe OneWorld vendor bridge: one row per vendor per subsidiary, with payables, in-transit and unbilled balances in both the relationship currency and the base currency, plus the per-subsidiary credit limit.