Building and editing product structure > Restructuring and editing the product structure
Performing on-demand validation
Your administrator can configure Teamcenter to enforce any rules imposed by the organization on what types of content are allowed in the structure. You cannot add content or make other structure edits that would violate the defined business rules.
The following types of restrictions on content within a structure are enforced:
Only certain item classes or types may exist anywhere in a structure.
Only certain item classes or types may be children of others.
Only certain item classes or types may be parents of others.
Properties of the parent or child object must satisfy specified values or be NULL.
For allowable substitutes in a given BOM line, the same restrictions that apply to the primary part occurrence are applied to the substitute.
Validations are provided for the following operations:
Creating a new occurrence
Adding a substitute for a given occurrence
Cloning (duplicating) a structure
Importing or exporting a structure
Revise and baseline
Note
Teamcenter validates only the first two operations in real time.
When you save edits, Teamcenter validates that they do not violate the defined business rules and, if they do, displays an error message and does not save the changes.
Optionally, you can perform an on-demand validation of property updates at any time by right-clicking a top line with substructure and choosing Tools→Validate Occurrences. If no issues are found, Teamcenter displays a confirmation and saves a validation log. If issues are found, it displays a list of errors.
Note
The administrator uses the Business Modeler IDE to define these business rules on explicitly stated classes. Any subclasses or subtypes of these classes inherit the same rules.
Your administrator must also create and set the following preferences:
PS_Default_Rev_For_Occ_Cond_Validation Defines the default revision rule when a child item is used for validation.
PS_Bypass_Occurrence_Condition Configures the system to bypass occurrence condition validation for defined actions or operations.
Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.plm00043/xid432346 · retrieved 2026-07-11