Associating the EBOM and MBOM

Rolling up variant conditions

You can optionally propagate rolled-up variant conditions when you assign parts from a source to a target part structure or from a product BOP to a plant BOP. As a result, the BOM lines in the target or plant BOP hold the same variant conditions as the corresponding BOM lines in the source or product BOP. Teamcenter copies the variant condition on the source line, rolls up the variant conditions of all parents of the source line, and then propagates the rolled-up variant condition to the target line, as shown.

The top levels of the source and target must be linked for correct propagation of rolled-up variant conditions. Teamcenter calculates the rolled-up variant condition by traversing from the source line to the linked top or up to the installation assembly level, and then adding together all the variant conditions found during the traversal.

If the source line does not have variant conditions, Teamcenter calculates the rolled-up variant condition by considering the variant conditions of the parent and all levels above.

The accountability check is modified to recalculate the rolled-up variant condition on the source line and compare it with the variant condition already stored on the associated target line. It then reports any partial match discrepancies between the variant conditions.

By default, rolling up of variant conditions is disabled and must be enabled by setting the Rollup_Variant_Feature site preference to true. You should also set the RollUp_Variant_Traverse_Level_Is_InstallationAssembly preference to determine the level to which rolled-up variant conditions are calculated. If this preference is set to TRUE, Teamcenter calculates the rolled-up variant condition by traversing up to the installation assembly level in the structure. If the preference does not exist or is set to FALSE, it calculates the rolled-up variant condition by traversing up to the linked top.

If the rolled up variant expression is too long, your administrator can create the Rollup_Variant_Optimized_Format preference and set it to TRUE. Teamcenter then optimizes the rolled up variant expression for storage and display.

The following installation assembly preferences must also be set:

PortalDesignContextIsInstallationAssemblyMethod
PortalDesignContextIsInstallationAssemblyMethod.hasIRType.Type
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.name
PortalDesignContextIsInstallationAssemblyMethod.has_bomline_prop.value

Note

For the EBOM/MBOM scenario, Teamcenter calculates a rolled-up variant condition only if an assignment is made from the EBOM to the MBOM and both structures are linked.

Rolled-up variant condition supports the Teamcenter Product Configurator and classic model, not with modular variants.

The rolled-up variant condition is saved in optimized form in the database but, when you view it, you see a summation (AND calculation) of all variant conditions from the source line to the linked top. Consequently, the rolled-up variant condition displayed on the target line may contain some redundant clauses. This helps you decompose the variant condition to its constituent building block expressions.

Additional preference settings:

Set PSM_enable_product_configurator to true.
Set Rollup_Variant_Feature to true.
Add bl_formula to the MEAlignedPropertiesList preference.
Make sure bl_formula is not in any preferences beginning with MEAlignedPropertiesToExclude...