budgets
transactionSubsidiary-scopedThe budget header: one row per budget — an account, a fiscal year and whatever combination of subsidiary, class, department, location, customer and item the budget is dimensioned by — with the total the per-period rows add up to.
no lastmodifieddate on this record — full-refresh the budgets. The AMOUNTS are not here: total is the header rollup and the per-period figures are rows on budgetsmachine, so a budget-vs-actual read joins the period rows, never this table alone.
The analytics id is PLURAL — budgets — while the page's own label is the singular "Budget"; searching for the singular finds nothing. Feature-gated on Multiple Budgets: without it an account holds one budget per account and year and the category column is unused. hasSubsidiary is true — subsidiary here is a scalar select with a page-attested join. hasLocation is false by design: location is an OPTIONAL budget dimension and is null on any budget that isn't location-scoped, so an active anchor would discard rows rather than scope them — the transaction-header verdict again. year points at the accounting-period record (the year-level period row), and yearnoaccountingperiod is its plain-text twin for accounts that do not use accounting periods. The `item` column points at NetSuite's generalized item record rather than at the cataloged item master, so it is authored as an id pointer with no edge. One more page artifact worth knowing: the page lists a join from an account-type column that has no field row behind it, so nothing is authored from it. No 2025.2 script page exists for this record (the URL is a 405) — its continued existence is corroborated against the Help Center's Budget topic instead.
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 | id | Internal ID | NUMBER | Primary-key field |
| 2 | account | Account being budgeted (internal id) | NUMBER | |
| 3 | accountingbook | Accounting book the budget is held in (internal id) | NUMBER | |
| 4 | category | Budget category — the TEXT key budgetcategory.id holds | VARCHAR | |
| 5 | subsidiary | Subsidiary (internal id) | NUMBER | |
| 6 | class | Class the budget is dimensioned by (internal id) | NUMBER | |
| 7 | department | Department the budget is dimensioned by (internal id) | NUMBER | |
| 8 | location | Location the budget is dimensioned by (internal id) — optional, so no anchor is emitted | NUMBER | |
| 9 | customer | Customer the budget is dimensioned by (internal id) — resolves through the entity supertype | NUMBER | |
| 10 | item | Item the budget is dimensioned by (internal id) — the page's join targets NetSuite's generalized item record, so no edge is drawn | NUMBER | |
| 11 | currency | Currency the amounts are stated in (internal id) | NUMBER | |
| 12 | year | Fiscal year (internal id) — the year-level accounting period | NUMBER | |
| 13 | yearnoaccountingperiod | Fiscal year as text, for accounts that do not use accounting periods | VARCHAR | |
| 14 | total | Header total — the rollup of the per-period rows | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the Connect-landed copy of budgets 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>, <subsidiary_id>, <id>
-- ============================================================
-- Table : budgets — The budget header: one row per budget — an account, a fiscal year and whatever combination of subsidiary, class, department, location, customer and item the budget is dimensioned by — with the total the per-period rows add up to.
-- Purpose: Column-selected read of budgets — auto-generated from field metadata
-- Grain : One row per id
-- Caution: no lastmodifieddate on this record — full-refresh the budgets. The AMOUNTS are not here: total is the header rollup and the per-period figures are rows on budgetsmachine, so a budget-vs-actual read joins the period rows, never this table alone.
-- 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.account AS "Account being budgeted (internal id)",
t.accountingbook AS "Accounting book the budget is held in (internal id)",
t.category AS "Budget category — the TEXT key budgetcategory.id holds",
t.subsidiary AS "Subsidiary (internal id)",
t.class AS "Class the budget is dimensioned by (internal id)",
t.department AS "Department the budget is dimensioned by (internal id)",
t.location AS "Location the budget is dimensioned by (internal id) — optional, so no anchor is emitted",
t.customer AS "Customer the budget is dimensioned by (internal id) — resolves through the entity supertype",
t.item AS "Item the budget is dimensioned by (internal id) — the page's join targets NetSuite's generalized item record, so no edge is drawn",
t.currency AS "Currency the amounts are stated in (internal id)",
t.year AS "Fiscal year (internal id) — the year-level accounting period",
t.yearnoaccountingperiod AS "Fiscal year as text, for accounts that do not use accounting periods",
t.total AS "Header total — the rollup of the per-period rows"
FROM <catalog>.<schema>.budgets t
WHERE
t.subsidiary = <subsidiary_id> -- OneWorld partition — see quirks guide #oneworld
-- AND t.id = <id>
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (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 budgets.account = account.idON budgets.accountingbook = accountingbook.idON budgets.category = budgetcategory.idON budgets.subsidiary = subsidiary.idON budgets.class = classification.idON budgets.department = department.idON budgets.location = location.idON budgets.customer = entity.idON budgets.currency = currency.idON budgets.year = accountingperiod.idON budgetsmachine.budget = budgets.id
More Financials tables
- budgetsmachineThe budget's per-period rows: one row per budget and accounting period, with the amount budgeted for that period.
- expensecategoryThe expense-category list: one row per category an expense report line can be coded to, with its default rate, whether a rate must be entered, and the account the expense posts to.
- nexusThe nexus list: one row per tax jurisdiction the account is registered in, hierarchical through a parent nexus, with the country, state and the tax agency filings go to.
- salestaxitemThe tax-code list: one row per tax code a transaction line can be taxed under, pointing at the tax type that decides how the tax behaves.
- taxitemtaxgroupThe tax-item supertype: one row per tax code and tax group together, which is the surface a transaction line's tax pointer actually resolves against.
- taxtypeThe tax-type list: one row per type, carrying the behavior flags that decide how tax under it posts — whether it adds to the transaction total, whether it lands in item cost, whether it is a reverse charge, and whether it is included in the net amount.