budgetsmachine
transactionThe budget's per-period rows: one row per budget and accounting period, with the amount budgeted for that period.
no lastmodifieddate — full refresh. Three columns and no internal id: budget + period IS the grain, so summing this record without grouping inside a budget mixes every dimension the header carries.
Browser page name is budgetsMachine (label "Budget by Period"). The composite key is the budget pointer plus the period pointer — the demand-plan bucket precedent. The edge back to the header is listed on the budgets page, not here. period is an id pointer at the accounting-period record, but no join for it is attested on either page, so it is read as an id and no edge is drawn. A month-keyed twin record — budget by month — exists for accounts that do not use accounting periods, and it is deliberately not cataloged here: the period-keyed rows are the ones a period-grain budget-vs-actual read needs.
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
3 fields · 2 key
3 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | budget | Budget this row belongs to (internal id) | NUMBER | Primary-key field |
| 2 | period | Accounting period (internal id) — read as an id, no page-attested join | NUMBER | Primary-key field |
| 3 | amount | Amount budgeted for the period | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the Connect-landed copy of budgetsmachine 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.
2 parameters not filled: <catalog>, <schema>
-- ============================================================
-- Table : budgetsmachine — The budget's per-period rows: one row per budget and accounting period, with the amount budgeted for that period.
-- Purpose: Column-selected read of budgetsmachine — auto-generated from field metadata
-- Grain : One row per budget + period
-- Caution: no lastmodifieddate — full refresh. Three columns and no internal id: budget + period IS the grain, so summing this record without grouping inside a budget mixes every dimension the header carries.
-- 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.budget AS "Budget this row belongs to (internal id)",
t.period AS "Accounting period (internal id) — read as an id, no page-attested join",
t.amount AS "Amount budgeted for the period"
FROM <catalog>.<schema>.budgetsmachine t
WHERE
1 = 1 -- no partition column on this record; the filters below are optional
-- no lastmodifieddate on this record — there is no watermark column, so incremental extraction must full-refresh it (see quirks #deletes)
ORDER BY t.budget;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 budgetsmachine.budget = budgets.id
More Financials tables
- 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.
- accountThe chart of accounts: one row per account, hierarchical through parent, with its type, currency, special-account marker and the balance NetSuite maintains on it.