Understanding occurrence effectivity

Several occurrences may share an effectivity. When you edit the effectivity range on one occurrence, Teamcenter applies the change to all occurrences. (This is generally the reason for sharing effectivity.)

You can also pack occurrences if they share the same unit or date range and access protection status. Packed occurrences are displayed in a similar way to packed structure lines.

You cannot import or export structures containing occurrence effectivity. If you require individual structure nodes to have effectivity, consider the use of incremental change.

If an occurrence does not have an associated effectivity object, Teamcenter assumes it is always effective and it is configured regardless of the date or unit number set by the revision rule, as shown in the following figure.

If you do not split effectivities, you can optionally use the Configuration Item check box to indicate the end item, although Teamcenter does not enforce this use.

Occurrence effectivity rule

When you create an effectivity condition on an occurrence, you change the parent BOM view revision. Consequently, you must have write access to the BOM view revision. However, you can make subsequent changes to the effectivity range if you have write access to the effectivity object, allowing you to edit effectivity data after the structure is released.

Note

The import or export of a structure containing legacy occurrence effectivities is not supported. If you require individual structure nodes to have effectivity, consider using incremental change instead of occurrence effectivity. Structures managed with incremental change can be imported and exported using Multi-Site Collaboration.