Resolve Consumption Discrepancies
Consider a scenario where the parts in the upstream and the downstream views are equivalent to each other and are up to date. The consumption links are also not broken. A design engineer makes the following changes in the upstream view:
• Adds new parts
• Moves some parts
• Changes the position of some parts
Due to these changes, the consumption links between the upstream and downstream views may become unresolved. The consumption links may also become unresolved based on the applied filters.
A product manager can use the Resolve Consumption Discrepancies action to fix all the unresolved consumption links at once. Note the following points that are related to the Resolve Consumption Discrepancies action:
• Out of the box, this action is visible only to the Product Manager role. A Product Manager can configure the visibility of this action for other roles in the organization. For more information, see Configuring Visibility of Actions for Roles.
• The action is performance intensive and depends on the number of parts in the structure. A report is displayed after the action is complete.
• The action ignores non-configuration filters such as Path Filter, ECN Filter, and Selection Filter.
• The action is available only in the downstream structure.
• The action works only on the root node in the downstream structure.
• The action is not designed to be used on completely dissociated structures.
• The action detects discrepancies based on uniqueness and position logic. You can enhance this logic to detect discrepancies based on custom logic.
For more information, see Customizing Consumption Discrepancy Search.
To fix unresolved links, perform the following steps:
1. In the downstream view, select Resolve Consumption Discrepancies from the Editing menu.
2. The Consumption Discrepancy Report dialog box opens. The table in the dialog box displays the identity of each part for which the consumption link is unresolved, the upstream and downstream path of the part, and the following status:
◦ Unique Path Match—The path is unique in both the structures, but the consumption link is missing between the paths.
◦ Position Match—The path matches based on position in both the structures, but the consumption link is missing between the paths.
◦ Manual—The consumption link is missing between the paths, and a match could not be found.
◦ Matched randomly on occurrence data—The path matches based on occurrence ID in both the structures, but the consumption link is missing between the paths. If the occurrence IDs do not match, the status shows Matched randomly.
◦ Matched on occurrence attribute—The path matches based on reference designator in both the structures, but the consumption link is missing between the paths. If the reference designators do not match, the status shows Matched randomly.
◦ Matched randomly on usage data—The path matches randomly based on line number and quantity in both the structures, but the consumption link is missing between the paths.
◦ Missing equivalent link for same master—Equivalent link is created based on matching part master in both the structures.
The table tool bar displays the following actions:
|
Icon
|
Action
|
Description
|
|---|---|---|
 |
Clear all
|
Clears the selected entries.
|
 |
Invert selection
|
Inverses the current selection. Clears current selection and selects the entries that are not selected.
|
 |
Select all
|
Selects all the entries listed in the table.
|
 |
Select in structure
|
Highlights the parts that are associated with the selected rows in the upstream and downstream structures.
|
 |
Resolve
|
Resolves the missing consumption links.
|
 |
Search
|
Refines the listed changes based on the keywords specified in the Search box.
|
3. Select the rows that you want to resolve, and click .
.The rows that are resolved in the downstream structure display a Resolved status.
4. Click Close.
Click 
to verify the resolved consumption links on the Equivalent Occurrences tab. The downstream equivalent consumption status changes to 
indicating that an equivalent usage or occurrence exists.
to verify the resolved consumption links on the Equivalent Occurrences tab. The downstream equivalent consumption status changes to indicating that an equivalent usage or occurrence exists.