Configuring structures by modular variants

Teamcenter supports three methods of variant configuration, modular variants (described here), classic variants, and Product Configurator variants. Siemens Digital Industries Software recommends that you do not create both classic variants and modular variants in the same product structure, as this may cause in unpredictable results.

Caution If you migrate from one variants technique to the other, be aware that Teamcenter evaluates the same variant condition differently in modular variants and classic variants. In some circumstances, this may result in different product structure configurations. For example, Teamcenter evaluates classic variant conditions from the left, giving all operators the same precedence. When it evaluates modular variant conditions, it automatically gives AND clauses precedence over OR clauses. While it is technically possible to use modular variants with precise structures, unpredictable results may occur. If you want to implement modular variants, consider creating imprecise structures. If you authored a line within a product structure using Product Configurator variants, you cannot update that line using classic or modular variants.

Caution The Teamcenter Integration for NX does not fully support modular variants. To exchange variant assembly data between Teamcenter and NX, you must implement classic variants. However, the Teamcenter Integration for NX does support the synchronization of part data for modular variant items. You can synchronize option values with NX expressions when working with geometric options and variants, but you cannot see stored option sets in NX; use variant items instead of stored option sets. Modular variants make substantial use of temporary table space. The database administrator must ensure sufficient temporary table space is configured in accordance with the database manufacturer’s guidelines and deployment recommendations provided by Siemens Digital Industries Software.