Netsuite ERP Consultant Practice Questions

The Work Order is the planning document that authorizes the build. The actual consumption of components is recorded on the Assembly Build transaction. It is on this transaction that the user must enter the inventory detail (i.e., the specific lot numbers and quantities) for each component item that was used in the production run. This creates the crucial link between the finished product's lot number and the component lot numbers.

This is false. The 'Override Period Restrictions' permission allows a user to post to a period that has been locked for non-administrators, but it does NOT allow posting to a period that has been formally 'Closed' using the final step in the Period Close Checklist. Once a period is closed, no one can post to it without reopening it.

This is the correct configuration. Sourcing from the Customer record's custom field will pull the value onto the transaction when the customer is selected. Setting the Display Type to 'Disabled' makes the field visible but not editable on the transaction form, meeting the read-only requirement. 'Inline Text' would also work for display, but 'Disabled' is a common and clear choice for sourced, non-editable data.

With the Consolidated Payments feature, payments can be accepted at the parent customer level. When creating the payment record for the parent, the 'Apply' sublist will display all open invoices for the parent and all of its sub-customers. The user can then select the specific invoices from 'Global East' and 'Global West' to apply the single payment against.

When 'Advanced Shipping' is enabled without 'Pick, Pack, and Ship', the process is bifurcated. The Sales Order is first fulfilled, which creates an Item Fulfillment record and deducts items from inventory. This fulfillment record has a status (e.g., Picked, Packed, Shipped). The final step in the shipping process is setting the status to 'Shipped'. Invoicing can happen independently, either before or after shipping, depending on the billing schedule.

The most effective and maintainable solution is to use role-based form assignments. By creating two distinct forms and assigning them as the preferred form to roles specifically configured for different subsidiaries, you create a clean separation. The custom field's 'Display' subtab does not have a 'Subsidiary' filter; it can only filter based on other field values on the same record. Using a workflow would work but is more complex than necessary. Relying on user roles to set preferred forms is the standard NetSuite best practice for this common requirement.

NetSuite ARM allocates the transaction price based on the relative standalone selling prices (SSPs). First, calculate the total SSP: $12,000 (License) + $4,000 (Service) = $16,000. Next, find the allocation percentage for each element: License = $12,000 / $16,000 = 75%; Service = $4,000 / $16,000 = 25%. Finally, apply these percentages to the actual transaction price of $15,000: License = $15,000 * 0.75 = $11,250; Service = $15,000 * 0.25 = $3,750.

The 'Override Preferences' advanced option in CSV import allows the user to specify a posting period in the import file that is different from the period derived from the transaction date. This enables the consultant to map the transaction date to the historical date field while mapping the posting period to the current open period, satisfying both business requirements.

With Standard Costing, the assembly item is always valued at its pre-defined standard cost, which is based on the standard BOM quantity (10 units). Any deviation from this standard, such as consuming extra components, is captured in variance accounts. Since the difference is in the quantity of components used, the cost of the extra 2 units is expensed to the Production Quantity Variance account, highlighting the production inefficiency.