NetSuite 2026.2 CPQ: Independent Template BOM Conditions and Tests

In NetSuite 2026.2, CPQ Configurator 2.1.2 gives qualifying template-based assemblies their own copied bill of materials rather than sharing the template’s BOM. This behavior requires Advanced Bill of Materials to be enabled and the item creation record’s Bill of Materials box to be unchecked.

The practical benefit is template isolation: teams can edit the generated assembly’s BOM without changing the template BOM. To verify that result, test more than successful assembly creation. Confirm that the generated assembly has its own BOM, make a controlled edit, and compare the template against its original state.

Key takeaways

Copying conditions: Advanced Bill of Materials must be enabled, and the item creation record’s Bill of Materials box must be unchecked.
Creation prerequisite: NetSuite CPQ Manufacturing must be installed to automatically create assembly items required by a configuration.
Checkbox meaning: Unchecked does not mean the generated assembly has no BOM.
Acceptance test: The generated BOM changes as intended while the template BOM remains unchanged.
Separate checks: BOM naming and replacement behavior need their own review; they are not proof of template isolation.

When does NetSuite CPQ create an independent template BOM?

Item creation records can automatically create assemblies required by a configurable item when users submit their configuration. For qualifying assemblies created from a template, CPQ Configurator 2.1.2 copies the template BOM to the new assembly item instead of sharing it.

The distinction matters after creation. An assembly appearing after submission establishes that creation occurred. A visible BOM establishes that a BOM is present. Neither observation alone demonstrates that edits are isolated from the template.

For a useful test, follow one representative configuration through to its generated assembly and compare the two BOMs. Keep the scope specific: this release behavior concerns qualifying template-based assemblies, not every assembly or every CPQ configuration.

If you are also reviewing how configurable products are organized, see the overview of NetSuite CPQ Configurator products. For the independence test, focus on the source template, the item creation record, and the resulting assembly.

Required settings for an independent BOM copy

The copying conditions apply at different levels. Verify the account-level feature and then inspect the item creation record used by the configuration under test.

Setting	Required state	Applies to
Advanced Bill of Materials feature	Enabled	Account
Bill of Materials box	Unchecked	Item creation record

Both conditions must be satisfied for the documented template-BOM copying behavior. As a testing practice, record both states alongside the configuration you submit. This makes the result easier to review and helps keep the evidence tied to the intended item creation record.

The supplied source does not establish the template-copy behavior when either condition is unmet. Do not assume that a checked box or disabled feature produces the same result, and do not infer a specific alternative behavior from this release description.

Why the unchecked box does not mean “no BOM”

In this scenario, leaving the item creation record’s Bill of Materials box unchecked is a condition for copying the template BOM. It does not mean the resulting assembly has no BOM.

Use precise language in configuration notes: “unchecked for template-BOM copying” is clearer than “BOM disabled.” The latter suggests an outcome that the documented setting does not establish.

There is also a separate prerequisite: NetSuite CPQ Manufacturing must be installed for automatic creation of assembly items required by a configuration. Check that prerequisite before investigating why submission did not create the expected assembly. A missing assembly and a failed template-isolation test are different observations.

How to verify template BOM isolation after submission

Use a controlled test that compares the template before and after a deliberate change to the generated assembly’s BOM. The following is a recommended verification procedure, not a documented menu-by-menu setup sequence.

Select a representative template-based configuration. Identify its source template and item creation record so that the resulting assembly can be traced to the intended test case.
Confirm the prerequisites. Verify that NetSuite CPQ Manufacturing is installed, Advanced Bill of Materials is enabled, and the item creation record’s Bill of Materials box is unchecked.
Capture the template baseline. Record the template BOM information needed for comparison, including the component details relevant to the planned edit.
Submit the configuration. Verify that the expected assembly item is created.
Inspect the generated assembly’s BOM. Establish that it has its own BOM rather than merely recording that a BOM is visible.
Make a controlled edit to the generated BOM. Choose a change that will be easy to recognize and record exactly what changed.
Compare both results. Confirm that the generated BOM contains the intended edit and that the template BOM still matches its baseline.

Checking both sides matters. If you inspect only the template, an unsuccessful edit could look like successful isolation. If you inspect only the generated assembly, you have not tested whether the template remained unchanged.

Interpret the test evidence

Observation	What it establishes	Next check
The expected assembly was created	Assembly creation occurred	Inspect its BOM
A BOM is visible on the generated assembly	A BOM is present	Establish that it is the assembly’s own copy
The generated BOM contains the controlled edit	The edit took effect	Compare the template with its baseline
The generated BOM changed and the template stayed unchanged	The test demonstrates isolation for the tested case	Retain the evidence with the configuration settings

Where your wider workflow includes converting transaction lines into configured items, choose a representative configuration from that workflow. Keep the acceptance criterion focused on BOM independence.

Likewise, making new items available in transaction fields is a separate operational concern. Item availability does not demonstrate that edits to a generated BOM leave its template unchanged.

Prepare the assembly setup before testing

With Advanced Bill of Materials enabled, select assembly as the item type to work with an advanced BOM. Without that feature, the available type is assembly/bill of materials, and assemblies with an advanced BOM cannot be created.

The documented item creation record preparation sequence is:

Create an item creation record and complete its basic fields.
Set the BOM and revision fields.
Add components to the assembly.
Set manufacturing routing fields.
Add routing steps to the manufacturing routing.

Advanced-BOM assemblies support fields for both the BOM and its revision. Include these fields, components, and routing setup in the preparation review so the test represents the assembly you intend to create. A successful isolation check does not, by itself, validate the rest of that setup.

For the documented assembly setup, see Oracle’s Working with Assemblies on Item Creation Records.

Keep naming and replacement checks separate

When updating an existing BOM, keep the same name on the item creation record. The documentation also warns that adding a new BOM to assembly items overwrites an existing standard or master-default BOM.

Review BOM naming and existing default assignments before testing replacement scenarios. The supplied source does not describe further overwrite conditions, so this warning should not be treated as a complete replacement procedure.

For a clearer first test, avoid combining template-isolation verification with a replacement scenario. First establish that the generated assembly’s BOM can change without modifying the template. Then assess naming and default-assignment effects separately, using a recorded baseline for each review.

Who should own each check?

Administrators should verify Advanced Bill of Materials and the CPQ Manufacturing installation. Recording these prerequisites gives the team a clear starting point if submission does not create the expected assembly.

CPQ configuration designers should review the template-based item creation record and its Bill of Materials checkbox. They should also identify the representative configuration and retain the edit-and-compare evidence.

Manufacturing teams should include components, BOM revisions, and routing setup in assembly validation. Their setup review complements the isolation test rather than replacing it.

The rollout decision should rest on the behavior the release promises: the qualifying assembly receives its own copied BOM, and edits to that BOM leave the template unchanged. Successful creation, a familiar BOM name, or transaction availability is not a substitute for that comparison.