Propagating Upstream Changes
There may be some updates made to the upstream structure recently; for example, new parts added or existing parts removed. These updates may not be reflected in the downstream structure. You can use the Propagate Upstream Changes pane in Associative Part Structure browsers to update the downstream structure with the latest upstream changes. The application compares the current iteration of the upstream object with the previous up-to-date version that was linked to the current downstream iteration. You can review the detected changes and propagate the required changes to the downstream structure.
By default, equivalence association is used as the criterion to compare the objects. You can change the criterion to compare based on baseline number or time duration. For more information, see Customizing the Comparison Mechanism.
To propagate upstream changes:
1. Click 
on the middle pane tool bar and select the appropriate parts in the upstream structure.
on the middle pane tool bar and select the appropriate parts in the upstream structure.The Propagate Upstream Changes pane opens to the right of the browser.
 | The mechanism for detecting upstream changes requires that you select a part in the upstream structure. The search then detects changes made for the nodes linked up to the first level. The selection made in the downstream structure does not impact the search results. |
2. To search for the upstream changes based on a change notice created for an upstream part, enter the change notice or change task number in the Change Number box. The changes made on the resulting objects listed in the change notice or change task are detected.
| | • When using a change number, selecting a part in the upstream structure is not mandatory. Even if you select a part in upstream structure, the system displays only those discrepancies that are related with parts associated with the specified change number. • You can customize the search criterion for Change Number to detect the changes made through a promotion request. For more information, see Customizing Change Number Criteria. |
3. Select the search criteria to specify the upstream changes that you want to view:
◦ Criteria: To specify the comparison mechanism for detecting the upstream changes, select the appropriate mechanism from the Criteria list.
▪ Baseline: Enter the baseline number in the adjacent box. The current iteration of the upstream structure is compared with the parts included in the specified baseline.
▪ Out Of Date: The current iteration of the upstream structure is compared with the previous up-to-date version that was linked to the current downstream iteration.
▪ Duration: Enter the duration in the adjacent box. The current iteration of the upstream structure is compared with the iteration available before the specified duration.
◦ You can filter the search result by specifying the type of upstream changes to be listed, using the All Changes list.
▪ Added Parts: Detects parts that were added.
| | For the Added Parts criteria, you can control the way the detected parts are transferred to the downstream structure during the propagation. For more information, see Configuring and Customizing Automatic BOM Transformation. |
▪ Control Characteristics: Detects parts with added or removed control characteristics.
▪ Effectivity: Detects parts with updated effectivity values for the types: lot, block, serial, MSN, and date. Changes in effectivity values are detected only when a part is revised.
▪ Flexible Representation: Detects discrepancies in the flexible assembly features of parts. An administrator can add custom logic to detect, verify, and resolve flexible assembly discrepancies. For more information, see Customizing Flexible Assembly Discrepancy Search.
▪ Item Expressions: Detects parts with updated expressions assigned to items. The supported expressions are basic and advanced. Item Expressions also detects concatenated expressions. Item expressions also detect independent assigned expressions.
▪ Occurrence Expressions: Detects parts with updated expressions assigned to occurrences. The supported expressions are basic and advanced. Occurrence Expressions also detects concatenated expressions. However, independent assigned expressions are not detected.
▪ Out of Position: Detects parts with updated location coordinates.
▪ Part Attributes: Detects parts with updated values for the associated attributes including classification attributes. The attributes must be defined in the standard MPMLink carryover framework. Out of the box, the Part Attributes criterion detects changes for the Source and Assembly Mode attributes. You can customize the criterion to detect the attributes of your choice. For more information, see Customizing Part Attributes and Usage Attributes Criteria.
The criterion supports local and global attributes. It does not support dependent attributes, such as alias, cascaded, and calculated.
▪ Quantity: Detects parts with updated quantity values.
▪ Removed Parts: Detects parts that were removed.
▪ Replaced Parts: Detects parts that were replaced with new parts, existing parts, alternate or substitute parts, and peer equivalent parts.
▪ Usage Attributes: Detects parts with updated values for usage attributes that are defined in the standard MPMLink carryover framework. Out of the box, the Usage Attributes criterion detects changes for the Find Number attribute. You can customize the criterion to detect the attributes of your choice. For more information, see Customizing Part Attributes and Usage Attributes Criteria.
The criterion supports local and global attributes. It does not support dependent attributes, such as alias, cascaded, and calculated.
▪ Usage Expressions: Detects parts with updated expressions assigned to usage links. The supported expressions are basic and advanced. Usage Expressions also detects concatenated expressions. However, independent assigned expressions are not detected.
| | You can add or remove the change types given in the All Changes list. For more information, see Configuring Discrepancy Types and Supporting Interfaces. |
4. Click Search.
The box in the Upstream Changes panel displays the search result of the search task. The table lists the changes detected for the parts in the upstream structure. Each row in the table displays the updated part details and the current and previous values for a change type. For more information on the current and previous values, see Current and Previous Values for Discrepancy Types.
The table also includes the following status for each change:
◦ Resolved: The changes in the upstream structure are already resolved in the downstream structure.
◦ Auto: The changes in the upstream structure can be propagated to the downstream structure using the 
action.
action.◦ Manual: The changes in the upstream structure cannot be propagated using the default logic.
◦ Interactive: The changes in the upstream structure can be propagated by using the default logic and user interaction.
| | The Downstream Parent column displays parent part information. The parent part information appears as a path from common equivalent context. The part numbers are separated by a pipe sign. |
5. Select the changes that you want to propagate to the downstream structure, and click .
.| | The selection made in the downstream structure does not impact the propagation results. |
| | Instead of using the Propagate changes to downstream action, you can use a workflow event to sync the downstream structure with the latest upstream structure. For more information, see Propagating Changes Using a Workflow Event. |
6. Click OK to confirm.
The box in the Resulting Downstream Changes panel displays the result of the propagation task. The table lists the changes that were propagated to the downstream structure. Each row in the table displays the updated part details and the updated and previous values for a particular change type. For more information on the current and previous values, see Current and Previous Values for Discrepancy Types.
The changes that are successfully propagated to the downstream structure are grayed out in the Upstream Changes table. The changes that were not selected or could not be propagated, continue to appear in the Upstream Changes table.
The following status for each change appears in the Upstream Changes and Resulting Downstream Changes tables:
◦ Resolved: The upstream changes are propagated to the downstream structure.
◦ Failed: The upstream changes cannot be propagated.
 | After propagating a change, it is recommended to update the equivalent link for the corresponding parent node in the downstream structure. This ensures that subsequent searches for upstream changes provide relevant information. |
The following actions are available in the Upstream Changes and Resulting Downstream Changes table tool bar.
Icon | Action | Description | ||
|---|---|---|---|---|
 | Clear all | Clears the selected entries. | ||
 | Select all | Selects all the entries listed in the table. | ||
 | Invert selection | Inverses the current selection. Clears current selection and selects the entries that are not selected. | ||
 | Select in structure Select in downstream structure | In the Upstream Changes table, the Select in structure action highlights the parts that are associated with the selected changes in the upstream and downstream structure. In the Resulting Downstream Changes table, the Select in downstream structure action highlights the parts that are associated with the selected changes in the downstream structure.
| ||
| Propagate changes to downstream | Propagates the changes selected in the Upstream Changes table to the Resulting Downstream Changes table. | ||
 | Search | Refines the result based on the keywords specified in the Search box. |
menu to remove highlights from the selected parts.Propagating Effectivity in BOM Transformer
Effectivity settings are propagated from an upstream part to a downstream part when the following conditions are met:
• Effectivity is assigned to an upstream part.
• No effectivity is assigned to the corresponding downstream part.
• The com.ptc.windchill.mpml.copyOver.mapsb.newBranch.create.wt.part.WTPart property is configured in the mpmlink.properties.xconf file, which is located at Windchill\codebase\com\ptc\windchill\mpml\xconfs.
If the above conditions are satisfied, the effectivity values of upstream parts are propagated to corresponding downstream parts when structure transformation actions are executed.
Special Case: Reconciliation for Added Parts as New Part or New Branch
• When you configure the com.ptc.windchill.associativity.reconciliation.addusage.wt.part.WTPartproperty, the values and settings specified in the following preferences are respected:
◦ > >
◦ > >
◦ > >
| | The part types specified in this preference should be also specified in Structure Transformation Applicable Types preference. |
◦ > >
◦ > >
| | The part types specified in this preference should be also specified in Structure Transformation Applicable Types preference. |
For example,
<AddToProperty name="com.ptc.windchill.associativity.reconciliation.addusage.org.rnd.CustomPart" value="transformOption=newBranch"/> or <AddToProperty name="com.ptc.windchill.associativity.reconciliation.addusage.org.rnd.CustomPart" value="transformOption=newPart"/>
• The settings configured in the following preferences as well as for the above mentioned preferences are respected only when the structureOption element is not defined in the com.ptc.windchill.associativity.reconciliation.addusage.wt.part.WTPart property:
◦ > > >
◦ > > >
| | • If structureOption=0 in the property or the value of the respective Child Structure Option preference is set to Do not Duplicate, then the system traverses the structure after the propagate action is initiated and follows the regular standard reconciliation process. • If structureOption=1 or structureOption=2, then the system does not traverse the structure. |
Alternatively, you can customize the reconciliation framework to remove the consideration of above-mentioned preferences completely. For more details, refer Configuring and Customizing Automatic BOM Transformation.