Understanding BOM view revisions, view types, and multiple views

A BOM view revision is a Teamcenter workspace object that contains the single-level structure of an item revision. You can see BOM view revisions attached to the item revision by the BOMView revision relation. BOM view revisions are visible in other Teamcenter applications and allow you to easily distinguish different view types. Teamcenter processes BOM view revisions in a similar way to items. You can apply protection to BOM view revisions independently of other data. You can also release a BOM view revision independently of the related item revision or other associated data. Teamcenter automatically creates BOM view revisions when you initially create the product structure in Structure Manager; it is not necessarily to manually create BOM view revisions. However, you can manually create BOM view revisions if you create multiple views in the structure.

Note The creation of multiple views is discouraged for new Teamcenter deployments but continues to be supported for existing customers with successful deployments. Several possible alternatives to multiple views are available and require less maintenance of data. BOM view revisions are only meaningful in the context of the item revision in which they are created. You can paste references to BOM view revisions into a regular folder, for example, to collect together objects to submit to a release. However, you cannot copy references of BOM view revisions into other item revisions. Cutting, deleting, or removing a BOM view revision is not done regularly, and may be disabled completely at your site if the BVRManagement preference is set to false. The view type is an attribute of a BOM view revision that indicates its purpose, for example, design or manufacturing. It allows you to distinguish one BOM view revision to be distinguished from another BOM view revision in the same item revision. The view type of a BOM view revision in a parent assembly is not dynamically configured in the same way as revisions. You must specify the view type when you add the component to the assembly, for example, adding a specific (nonconfigurable) view of the component. If the component has multiple views, you can change the view type referenced by the parent assembly, but must have write access to the parent assembly to complete this edit operation. The administrator defines a set of view types for each site using the Business Modeler IDE. Any number of view types can be defined, but most sites only require a single view type for product structure synchronization with Structure Manager. You can use a Bought In view type to model a view that has no components. This may be useful when an assembly designed in one organization should be treated as a piece part in the parent assembly of a different structure.