Structure Management ─ Deployment and Administration
Group revision rule entries by occurrence type
You, as a configuration management analyst, can define revision rules to treat different occurrence types with variations of the configuration logic. In some cases, the existing grouping mechanisms based on the item type are not sufficient because a part appears in some assemblies only for reference purposes. In such cases, you can use a Working revision rule to author the BOM significant parts in an assembly. However, the system may reference the content, using a Released revision rule. For example, you create a Has Occurrence for the MEAssign occurrence type. Then you create a Working() revision rule to configure the product structure only if the occurrence type is MEAssign. For all other occurrence types in the product structure, Teamcenter applies the Has Status(Any Released Status, Configured Using Released Date) rule. You can modify the order of precedence of revision rule entries by grouping revision rules by occurrence type. For the configuration of an item revision, Teamcenter evaluates a revision rule within the occurrence type group only if there is a match between the occurrence type of the revision rule group and the underlying item revision on the line. By using this grouping mechanism with item revisions of different occurrence types, you can create revision rules to selectively apply the revision rule entries according to a given occurrence type. You cannot create item type groups within occurrence type groups. You create the Has Occurrence type in the following format: Copy Has Occurrence Type(Occurrence type1, Occurrence type 2, etc) { <Revision Rule Entry 1> <Revision Rule Entry 2> …… etc. } Example: Copy Has Occurrence Type(MEAssign) { Working() } Has Status(Any Release Status, Configured Using Released Date) In this example, the Working() revision rule entry configures the product structure only if the occurrence type is MEAssign. For all other occurrence types in the product structure, Teamcenter applies the Has Status(Any Released Status, Configured Using Released Date) rule.
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/administering_product_structures/qmd1737238832907/unn1737238834777/xid1560945.html · retrieved 2026-07-11