Create a revision rule for nested effectivity

When you create a revision rule for a nested effectivity scheme, ensure you select the Nested Effectivity check box. This action adds a Nested Effectivity entry to the revision rule and ensures that Teamcenter modifies the revision rule according to the mapping on any configuration items it encounters. If you do not check this check box, Teamcenter ignores any configuration items. The position of the Nested Effectivity entry in the rule is not significant and never changes. The following example structure has date effectivity and an end item defined on the item revision of each part: Item Status, effectivity Note NE-A1000/A (CI) – Product X - - NE-A2000/A (CI) Released, EI: NE-A1000, 15 July-UP Rev Effect wrt NE-A1000 – Product X NE-A100/A Released, EI: NE-A2000, 20 July-UP - NE-A200/A Released, EI: NE-A2000, 20 July-UP - NE-PP30/A Released, EI: NE-A2000, 20 July-UP - NE-PP10/A Released, EI: NE-A2000, 20 July-UP - NE-PP20/A Released, EI: NE-A2000, 20 July-UP - NE-A3100/A (CI) Released, EI: NE-A1000, 16 July-UP Rev Effect wrt NE-A1000 – Product X NE-A400/A Released, EI: NE-A3100, 23 July-UP - NE-PP70/A Released, EI: NE-A3100, 25 July-UP - NE-PP60/A Released, EI: NE-A3100, 25 July-UP - NE-A5000/A (CI) – Product Y - - NE-A2000/A Released, EI: NE-A5000, 15 July-UP Rev Effect wrt NE-A5000 – Product Y The resulting configuration item effectivity mappings are: Mapping on NE-A2000 (CI): NE-A1000 (CI) – Product X : NE-A2000 (CI) NE-A5000 (CI) – Product Y : NE-A2000 (CI) Mapping on NE-A3100 (CI): NE-A2000 (CI) – Product Y : NE-A3100 (CI) If you apply the following revision rule, the structure is configured as shown in the following figure: Status = Released, Configured by Effective Date Working Nested Effectivity EI = NE-A5000 Date = 27 July 2006 Nested effectivity 1 Conversely, if you apply the following revision rule with no nested effectivity entry, the structure is configured as shown in the following figure: Status = Released, Configured by Effective Date Working EI = NE-A5000 Date = 16 July 2005 Nested effectivity 2 Teamcenter ignores the mappings, so the end item does not switch from A5000 to NE-A2000/NE-A3100 at the configuration items. Consequently, none of the components below the configuration items are configured, as the end item on the effectivity is not NE-A5000. If you apply the following revision rule, Teamcenter applies effectivity mapping due to the Nested Effectivity entry and the structure is configured as shown in the following figure. However, some of the components are not effective on 23 July and have no configured revision; Teamcenter marks these components as ???. Status = Released, Configured by Effective Date Working Nested Effectivity EI = NE-A5000 Date = 23 July 2005 Nested effectivity 3