Override data in the context of a composition

You can associate data to a composition in the context of an operation or process setup. The following figure shows how you may override data in the context of a setup.

Override occurrence data in the context of a composition

This structure contains occurrences (Resource 1, and consumed items C1 and C2) and a collection of absolute occurrences (occGroup1). This collection consists of absolute occurrences a6 and a7 which Teamcenter configures if you load Product 1. Thus, a6 and a7 in the process structure are absolute occurrences in the context of occGroup1. The consumed item C1 is an occurrence in the setup for Operation 1 and is linked to absolute occurrence a4 in Product 1.

Note

The process structure may also have its own absolute occurrences.

You can override data in the context of the process. You can also override data in the context of Product 1 through the absolute occurrences in the occurrence groups. The override data is controlled by a rule that allows you to attach JT files at a top level and at an intermediate level. Consequently, a JT file attached to c5 under Occurrence Group 1 in the context of the Operation 1 BOM view revision (BVR) overrides the default file, and also the file associated with a6 in the product 1 BVR.

If you create absolute occurrences for the process structure and (assuming P6 is the occurrence for C5), the data attached to P6 in the context of Process overrides data attached to a6 in the context of the Product 1 BVR.