Update a BVR structure with PMM changes

When you are informed through your workflow of changes made in Product Master Management (PMM) to a BOM view revision (BVR) previously generated in Multi-BOM Management from PMM data, you must refresh the BVR in Multi-BOM Management. The Refresh from PMM command uses the default "Any Status; No Working" revision value for configurator data. For information about customizing this revision value, see Configuring and Customizing Product Master Management.

Select one or more subassembly nodes to be updated, right-click any selection, and choose Refresh from PMM.

The Product Master Management information is updated for the selected part and changes to the key line of usage (LOU) attributes create a new revision. In the BVR, a new item occurrence is created with the new revision displayed on the node that you updated.

You or your administrator can set the preference PMM_PS_UseExistingTcItems to specify the property mapping between the Teamcenter item and PMM part.

• If the preference is not set, while querying the items from the Teamcenter database, if they do not exist, new items, item revisions (with revision effectivity applied), and corresponding forms (Part Form and Part Revision Form) are created in Teamcenter. These forms and the aligned design items are attached to these items. The newly created items are used for creating the BVR.Part, line of usage (LOU), solution, and solution group usage (SGU) customization is supported when this preference is not set.

• If the preference is set, while querying the items from the Teamcenter database, if they do no exist, the Refresh from PMM action or the command line utility displays an error. If the items exist, the Refresh from PMM action neither revises the items nor applies the revision effectivity to them. It also does not create the Part Revision Forms. It only creates the Part Forms and attaches them to the items. The items are then used for creating the BVR. The aligned design items are not attached to the existing Teamcenter items.Part customization is not supported when this preference is set.

Output that is displayed in Manufacturing Process Planner when there is an update to Product Master Management data includes the following.

Note

A pink node revision represents a part version in PMM. Pink node revision effectivity is mapped to part version effectivity.

• In some cases, a part version in PMM is mapped to multiple pink nodes in the BVR because a part can have multiple design revisions. A usage of the part, or different usages of the same part, can be aligned to solutions which have different design revisions.

Pink node occurrence corresponds to usage/occurrence of a part with associated design—line of usage (LOU) + solution.

• Effectivity on a pink node occurrence is combined with effectivity of the part version, LOU version, solution group usage (SGU) version, and solution version.

If a PMM scope or recipe is changed, all the cases that follow may occur and the existing BVR is updated.

Update	Details
Versionable property change on LOU	If the LOU is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of LOU with the overlapping effectivity dates mapped to its occurrence effectivity.
Versionable property change on part	A new revision of the existing item is created. The previous revision's revision effectivity dates are cut back and the new part's version effectivity dates are mapped with the new item's revision effectivity dates.
Versionable property change on solution	If a solution is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of the solution with the overlapping effectivity dates mapped to its occurrence effectivity.
Versionable property change on SGU	If the SGU is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of the SGU with the overlapping effectivity dates mapped to its occurrence effectivity.
Nonversionable property change on LOU	If there is a nonversionable update on the LOU, the existing occurrence effectivity is updated to the modified effectivity of the LOU (overlapping effectivity dates are mapped).
Nonversionable property change on part	If there is a nonversionable update on the part, the existing revision effectivity is updated to the modified effectivity of the part.
Nonversionable property change on solution	If there is a nonversionable update on the solution, the existing occurrence effectivity is updated to the modified effectivity of the solution (overlapping effectivity dates are mapped).
Nonversionable property change on SGU	If there is a nonversionable update on the SGU, the existing occurrence effectivity is updated to the modified effectivity of the SGU (overlapping effectivity dates are mapped).
Quantity update on LOU	If quantity is updated and the LOU is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of the LOU with the overlapping effectivity dates mapped to its occurrence effectivity.
Position designator update on solution	If the position designator is updated and the solution is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of solution with the overlapping effectivity dates mapped to its occurrence effectivity.
Part update on LOU	If a part is updated and the LOU is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of LOU with the overlapping effectivity dates mapped to its occurrence effectivity.
Partition update on LOU	If a partition is updated and the LOU is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of the LOU with the overlapping effectivity dates mapped to its occurrence effectivity.
Expression update on LOU	If an expression is updated and the LOU is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added in the product structure for the new version of LOU with the overlapping effectivity dates mapped to its occurrence effectivity.
Expression update on solution	If an expression is updated and the solution is versioned, the occurrence effectivity of the previous occurrence is cut back and a new occurrence is added to the product structure for the new version of the solution with the overlapping effectivity dates mapped to its occurrence effectivity.
New LOU found in query for the same part	If a new LOU is found for the same part, it creates a new occurrence and sets an occurrence effectivity and variant condition.
New solution found in query	If a new solution is found for the same part, it creates a new occurrence and will set occurrence effectivity and variant condition.
New part found in query	If a new part is found in the solve query, it creates a new item and item revision. It then creates a part form and relates it to an item. It then creates a part revision form and relates it with an item revision. Both forms can be seen using the relations.
Logically deleted LOU or discontinued LOU	If a LOU is logically deleted, its existing occurrence's effective in-and-out-dates are the same and the occurrence is configured out.
Reconfigured LOU or continued LOU	If a logically deleted or discontinued LOU is reconfigured in, its existing occurrence's effective in-and-out-date is modified accordingly and the occurrence is configured in for those dates.
Logically deleted solution	If a solution is logically deleted, its existing occurrence's effective in-and-out-date is the same and the occurrence is configured out.
Reconfigured solution	If a logically deleted or discontinued solution is reconfigured in, its existing occurrence's effective in-and-out-dates are modified accordingly and the occurrence is configured in for those dates.
Logically deleted parts	If a particular part's version is logically deleted, the revision effectivity of the corresponding item revision is modified. Because its effective in-and-out-date is identical, that particular revision of the item is configured out.
Reconfigured parts	If a particular part's version that was logically deleted is reconfigured, the revision effectivity of the corresponding item revision is modified and the particular revision of the item is configured in.
New design aligned to a solution	If a new design item is aligned to a particular revision of a solution, a new occurrence of the solution is added in the product structure and the new design item is attached to the existing item of the part that was consumed by the solution.
New design item aligned to all solutions	If a new design item is aligned to a particular revision of a solution, a new occurrence of the solution is added in the product structure and the new design item is attached to the existing item of the part that was consumed by the solution.
Custom property mapping: LOUs and solutions	Custom property mapping for LOUs and solutions.
Custom property mapping for parts	Set custom property mapping for parts.