NetSuite ERP Fundamentals
This domain tests the foundation under every module: the account structure, how records relate, how access is granted, and how features are switched on. Expect scenarios rather than definitions - why a user with the right permission still cannot open a record, or which field drives consolidation.
Structure and dimensions
- A subsidiary is the legal and accounting unit. It determines base currency, tax nexus, and consolidation. Non-OneWorld accounts hold one implicit subsidiary.
- Department, Class, and Location are transaction and line-level segments used for reporting. They are not legal entities and hold no balances of their own.
- Custom segments create new reporting dimensions without consuming custom fields and can attach to transactions, transaction lines, or entities.
- Customers and vendors can be shared across subsidiaries; that sharing setting is separate from role permissions.
Roles and access
- Permission levels run None, View, Create, Edit, Full; Full includes delete.
- Role restrictions (subsidiary, department, class, location, employee) scope the data a permission applies to. Restrictions beat permissions.
- Feature enablement is often one-way: once Departments, Classes, or Locations are in use they cannot be switched off.
Worked example
A UK user with Full permission on Purchase Order still cannot open a US purchase order. The permission grants the action; the role's subsidiary restriction limits the records. The fix is adding the US subsidiary to the role, not raising the permission. Then confirm the employee's approval limit covers the order value.
Traps that cost marks
- Confusing segments (Department/Class/Location) with the subsidiary that drives currency and consolidation.
- Assuming CSV Update creates records - it matches on Internal ID and updates only.
- Mixing Internal ID (system-generated) with External ID (integration key).
- Forgetting that restrictions, not permissions, explain most "cannot see it" questions.