Minimize expansion of structures using closure rules

You can limit the expansion of the structure using site-specific criteria to reduce potentially time-consuming expansions. For example, if a line has a monolithic JT file attached to it, you may not want to expand the subassembly below it. Similarly, you may not want to expand an assembly if it is not assigned to the current project. The site administrator specifies the available rules in the ClosureRulesForBomExpansion preference.

Lines filtered out by a closure rule are not exported.

If lines are hidden by a closure rule, you cannot find them from other views using the Find menu commands.

Note

Expanding a structure based on a closure rule can affect the outcome of an accountability check. Because this type of expansion filters the displayed lines, it can interact with any inclusion rules you may set for the accountability check.

Select a closure rule before expanding the structure:

Procedure

1. Choose Tools→View/Set Closure Rule for Expansion.Teamcenter displays the View/Set Closure Rule for Expansion dialog box. Note If the closure rules differ from those shown, the site administrator must edit the ClosureRulesForBomExpansion preference.

2. Select the required closure rule in the Rules list, and then enter any filter attributes necessary for the selected rule. In the example shown, you must specify at least one project identifier.Note In a conditional clause, evaluation of the left-hand expression must give primitive data types such as string or integer. If the related property is a typed reference, untyped reference, relation, or external references, the left-hand expression must evaluate to a primitive data type that uses the property of the object. You must use the property of the object, rather than the object itself. For example, instead of using PRIMARY.bl_uom==”kg” in a condition clause, you should traverse from BOMLine to UnitOfMeasure using bl_uom and then use a icon property of UnitOfMeasure.

Primary object class

Primary object

Secondary object class

Secondary object

Relation type

Related property

Action type

Conditional clause

CLASS

BOMLine

CLASS

UnitOfMeasure

Property

bl_uom

Skip

SECONDARY. symbol ==$var

Note Line breaks are not supported in closure rules with variables.

3. After you enter the attributes, click OK to set the closure rule.Teamcenter applies the closure rule to all future structure expansions until you unset it or set another rule.Note You can set the SkipClosureRuleEquivalent user preference to determine whether the closure rule is re-evaluated if you reapply it in the same session and the referenced property has changed.

To unset the closure rule, select it in the Rules list and then click Unset Rule.

Tip

You can see the name of the current closure rule in the tooltip on the structure tab or in the configuration information when you click .

If the action type in the closure rule is SKIP, lines meeting the criteria do not appear. If the action type is PROCESS, qualified lines appear but are not expanded (they show a + icon). To expand such a line, unset the closure rule from the window and then repeat the expansion of the subassembly.