NetSuite Reference
NetSuite Reference Database
NetSuite is one spine and one door: every transactional document — sales order, fulfillment, invoice, work order — lives in one table family separated by a type value, and all of it leaves through the NetSuite2.com analytics source. So this reference maps both halves.
Free & ungated · Analytics Browser 2021.1 · corroborated 2025.2 · Last verified August 2026
70
Tables
11
Modules
13
Quirks
How this is scoped
- Scope: the supply-chain core, building out from the OneWorld foundation, entities, the item master and inventory to the transaction spine and the platform records incremental extraction depends on — now with the order-to-cash and work-order document sets in the record map, the price matrix and payment terms behind what a line is worth, the shipping, fulfillment-request and warehouse pick records on the delivery side, and the make-and-plan layer — bills of material and their dated revisions, routings and cost templates, and the per-item-per-location planning parameters, demand plans and supply plans — plus the financial layer the spine posts into: the chart of accounts and its account types, budgets with their per-period rows, expense categories and the tax reference. The record map covers the financial documents too — journal entries, vendor bills, payments, credits, checks and deposits — alongside every table.
- Verification: field names, keys, and structural facts are curated against each record's own page in Oracle's Analytics Browser, pinned at 2021.1 because that is the last publicly reachable field-level catalog, and each record is corroborated against the current 2025.2 Records Browser (Analytics Browser 2021.1 · corroborated 2025.2). Anything neither source attests is left out rather than guessed — no transaction type codes ship, because Oracle publishes no list of them. Every description is original wording. Last verified August 2026.
- Built for analytics: relationships focus on the joins you'll actually write — the header/line pair, the line-to-accounting-line hop with its accounting-book anchor, the document links between one transaction and the next — and the generated SQL targets the Connect-landed copy in your lakehouse, never live NetSuite.
Frequently Referenced Tables
The workhorses of NetSuite supply-chain analytics — the transaction spine and its accounting lines, the item master, on-hand balances, and the foundation records every other join resolves through.
- transactionThe document header for every transaction type NetSuite records — sales orders, purchase orders, fulfillments, receipts, invoices, journals — separated by the type column rather than by table.
- transactionlineThe line grain of the transaction spine: item, quantity, rate and transaction-currency amounts, plus the subsidiary, location, class and department that scope the line.
- transactionaccountinglineThe accounting projection of a transaction line: base-currency amount, debit, credit and net, per accounting book, with the GL account and audit-number stamps.
- 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.
- inventoryitemlocationsThe per-item-per-location balance and policy record: on hand, available, committed, back-ordered and in-transit quantities alongside the reorder point, safety stock, lead times and the location's cost basis.
- customerThe customer master: identity, status, terms, credit control and the entity-level balance rollups, plus the sales-history date stamps.
- vendorThe vendor master: identity, terms, incoterm, credit limit and payables balances in both the vendor's primary currency and the base currency.
- subsidiaryThe OneWorld legal-entity master: one row per subsidiary, hierarchical through parent, each carrying its own base currency, country and fiscal calendar.
The NetSuite quirks guide
The modeling traps that make a first NetSuite extract wrong in ways that look right, for practitioners landing NetSuite data in a lakehouse: OneWorld scoping, the transaction spine, accounting-book duplication, and the deletes an incremental extract never sees. Each links to a worked Databricks SQL pattern.
Read all 13 quirksGetting NetSuite data into your lakehouse
The extraction guide covers the whole path out of the one door — the SuiteAnalytics Connect drivers and the role permissions that decide what your extract can see, SuiteQL and the REST query service and where each one wins, landing and layering in Databricks, an incremental pattern that handles the deletes a watermark never shows you, the records that carry no watermark at all, and NetSuite Analytics Warehouse as the managed alternative worth naming before you build.
Read the extraction guideBrowse by Module
Grouped by record family rather than business cycle — NetSuite has no product or schema axis, and its documents share one physical spine. Click a module to see its tables and the records that resolve into them.
- FoundationSubsidiaries, currencies and both exchange-rate tables, accounting periods and books, locations, departments and classes — the dimension layer every OneWorld filter resolves against. Location sits here rather than in inventory: in NetSuite it is an org segment first and a stocking site second.9 tables
- EntitiesThe entity supertype plus the customer and vendor records and their OneWorld subsidiary-relationship bridges — where per-subsidiary balances actually live.5 tables
- ItemsThe unified item master and its satellites: vendor sourcing rows, the item-to-subsidiary bridge, units of measure and their conversion rates, and the generic component record behind kits, groups and assemblies. One table holds every item type, discriminated by itemtype.6 tablesSupply chain
- InventoryPer-item-per-location balances and the lot/serial layer — inventory numbers and the assignment lines that tie them to transaction lines.3 tablesSupply chain
- TransactionsThe unified spine: transaction, transactionline, transactionaccountingline, the shipment and address satellites, the payment-method list, the two line-link tables, and the two delivered sales views. Sales orders, purchase orders, fulfillments, receipts, invoices, payments and journals all live here, separated by a type value rather than by table.11 tablesSupply chain
- Fulfillment & LogisticsShipping items — which in NetSuite are also the shipping methods — plus the fulfillment-request document and the warehouse-management pick tasks and zones. The pick and zone records are feature-gated: they exist in every account's catalog and hold rows only where NetSuite WMS is switched on.4 tablesSupply chain
- PricingPrice levels, pricing groups, payment terms, quantity-pricing schedules, and the item price matrix itself — one row per item, level, currency, quantity break and sale unit, which is the grain that catches an unpinned join.5 tables
- ManufacturingBills of material and their dated revisions, the component lines underneath them, routings and their operation steps, the cost templates a step is costed with, and the operation tasks a running order is executed through. Work orders stay on the transaction spine and are reached through the record map.8 tablesSupply chain
- PlanningThe planning parameters at item and location — reorder point, safety stock, lead times, time fences and lot sizing — plus the demand plans and their time buckets, and the supply plans with the orders and action messages the engine produced.6 tablesSupply chain
- FinancialsThe chart of accounts and the account types behind it, budgets with their per-period rows, expense categories, and the tax reference — tax codes, tax types, the tax-item supertype and the nexus jurisdictions. Journal entries and the payment documents stay on the transaction spine and are reached through the record map.10 tables
- PlatformThe audit-and-extensibility layer: both generations of the field-level change log — the text-valued original and the typed second version — and the deleted-record ledger that incremental extraction depends on.3 tables
Sources & further reading
Table structure and behavior are authoritative only at source. Use these references to verify before building on any claim in this reference.
Show all 28 sources, graded by group
Oracle schema browsers
- Analytics Browser 2021.1 — record pages (opens in new tab) — the field-level authority for the NetSuite2.com analytics source, and the last Oracle-authored public version of it. Every table and every field row in this reference was checked against its own record page. (These are the public archived srbrowser pages — not the discontinued in-account Analytics Browser tool, which was a different surface.)
- SuiteScript Records Browser 2025.2 — record pages (opens in new tab) — the current-release corroboration: each cataloged record was re-checked here for continued existence and behavior, and the document records with no analytics page cite it directly.
Oracle NetSuite Help Center
- SuiteAnalytics Connect — oa_tables (opens in new tab) — the column-by-column reference for the oa_tables metadata record, the discovery surface #connect-access queries first.
- SuiteAnalytics Connect — oa_columns (opens in new tab) — the sibling reference for the oa_columns metadata record: one row per exposed column, per role.
- SuiteAnalytics Connect — oa_fkeys (opens in new tab) — the third Connect metadata record, listing declared keys. Oracle's own page cautions it may be inaccurate for the NetSuite2.com source and should be read as reference only — which is why nothing in this catalog is derived from it.
- Role and Permission Considerations for NetSuite2.com (opens in new tab) — the access model behind #connect-access and the extraction guide: role-based visibility mirroring the UI, the Administrator/OAuth 2.0 restriction, the Data Warehouse Integrator role and its overrides, and the structure-vs-data visibility split.
- Removal of the NetSuite.com data source (opens in new tab) — the 2026.1 removal of the legacy source, which is why this reference documents one door and not two.
- SuiteQL (overview) (opens in new tab) — the page that actually states SuiteQL is based on the SQL-92 revision of SQL, behind every SQL-92 mention on this reference.
- Using SuiteQL with the Connect Service (opens in new tab) — Oracle's own syntax guidance: use Oracle SQL syntax against the analytics source, with an explicit timeout warning on ANSI-converted queries and the right-outer-join exception, behind the extraction guide's #suiteql.
- SuiteQL — the REST query service (opens in new tab) — the 100,000-row response cap and the limit/offset paging behind #connect-access and the extraction guide's #suiteql.
- SuiteQL query examples (opens in new tab) — Oracle's own examples filter the header row of a transaction, which is the attestation behind the #transaction-spine mainline convention.
- Transaction links (opens in new tab) — how one document is created from another: the linkage behind the document-link edges on the transaction pages.
- Custom Transaction Body Fields — custbody_ (opens in new tab) — the field-definition page attesting the custbody_ prefix behind #custom-fields.
- Custom Transaction Line Fields — custcol_ (opens in new tab) — the sibling page attesting the custcol_ prefix for transaction line columns.
- Custom Entity Fields — custentity_ (opens in new tab) — the sibling page attesting the custentity_ prefix for entity records.
- Custom Item Fields — custitem_ (opens in new tab) — the sibling page attesting the custitem_ prefix for item records.
- Custom record types (opens in new tab) — how a custom record becomes a queryable table, and why its name differs from account to account.
- Deleted records in Connect (opens in new tab) — the deleted-record ledger behind #deletes, and the reason a watermark alone never keeps an extract in sync.
- Searching for Deleted Records (opens in new tab) — the enumerated record types that support deletion tracking at all, with a separate and smaller list for the analytics data source: the coverage limit behind #deletes and the extraction guide's #incremental.
- Budget (opens in new tab) — what a budget covers (one account, one fiscal year, an amount per period) and the dimensions it can be broken down by. The budget record has no 2025.2 script page, so this topic is its currency corroboration.
- Budget Category (opens in new tab) — the Multiple Budgets feature gating: the category record exists, and budgets carry a category at all, only where that feature is on.
- Quantity Pricing Schedules (opens in new tab) — the Quantity Pricing feature gating and the three ways a break quantity can be counted, which is what the schedule's calculation column selects between.
Databricks & the managed alternative
- Databricks Auto Loader (opens in new tab) — the incremental file-ingestion path behind the extraction guide's bronze landing.
- Databricks — Upsert into Delta with MERGE (opens in new tab) — the MERGE and MERGE-DELETE patterns behind the extraction guide's incremental load and deleted-record diff.
- Databricks — Medallion architecture (opens in new tab) — the bronze/silver/gold layer conventions every snippet on this reference assumes.
- Oracle NetSuite Analytics Warehouse — Guides (opens in new tab) — the managed pipeline, warehouse and semantic model, named in the extraction guide as the build-versus-buy alternative to landing NetSuite yourself.
- Databricks Lakeflow Connect — NetSuite connector (opens in new tab) — the Databricks-managed ingestion connector for NetSuite, the third road named in the extraction guide's #what-not.
- Databricks Lakeflow Connect — NetSuite connector limitations (opens in new tab) — the limits that decide the fork: NetSuite2.com only, token-based auth, 200 tables per pipeline, no 300-plus-column tables, and no ingestion of the deleted-record ledger.