Overview of creating a structure context

You can create a structure context and add it to the current collaboration context. You can create any valid structure context, including a product or process to include in a collaboration context. If no collaboration context is open, Teamcenter adds the new structure context to the database for later assignment.

The structure context may be a composition, depending on its type. Items in a composition structure may have relationships to other structures or to absolute occurrences and occurrence groups.

If the structure context is a composition:

• Each target line in the structure context refers back to the source line, as indicated by the symbol. You can use the Tools→Find in other panel command to identify the related source from the target or vice versa.

• Occurrence data is retrieved from the source line to the target line when you open the target structure context; it is not copied. Absolute transforms, absolute occurrence identifiers, and variant conditions are retrieved; occurrence notes are not retrieved.

• No absolute occurrence identifiers are created during assignments. However, if you specify an absolute occurrence identifier in the source, Teamcenter shows it in the ID at All Levels property column, not on the top level.

• If you change occurrence data on the source, the change is inherited by the target unless you override the corresponding data on the target.

• If you change occurrence data on the target, Teamcenter does not change the corresponding data on the source. This allows you to reposition lines in the target, for example, to move assemblies to give a different structure or insert lines to represent consumables. Note When you change item or item revision attributes (for example, the revision master form), the values Teamcenter displays depend on the revision rule that configures the source and target. These attributes are independent of occurrence data.

• Revision or variant rules applied to the source also configure the target.

If the structure context is not a composition:

• The target line in the structure context does not refer back to the source line. However, you can use the Tools→Find in other panel command to identify the related source from the target, or vice versa.

• Occurrence data is copied from the source line to the target line, including absolute transforms, absolute occurrence identifiers, variant conditions, and occurrence notes.

• The absolute occurrence identifier is populated during the assignment process and, if you already enter a value in the source, the same value is copied to the target. If the value is empty, the source is populated with the UID.

• If you change occurrence data on the source, the change is not propagated to the target.

• If you change occurrence data on the target, Teamcenter does not change the corresponding data on the source.

• When you change item or item revision attributes (for example, the revision master form), the values Teamcenter displays depend on the revision rule that configures the source and target. These attributes are independent of occurrence data.

• If you change occurrence data on the target, Teamcenter does not change the corresponding data on the source. This allows you to reposition lines in the target, for example, to move assemblies to give a different structure or insert lines to represent consumables. Note When you change item or item revision attributes (for example, the revision master form), the values Teamcenter displays depend on the revision rule that configures the source and target. These attributes are independent of occurrence data.

• Revision or variant rules applied to the source have no impact on the target.