Showing results for 
Search instead for 
Did you mean: 
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Need to share some code when posting a question or reply? Make sure to use the "Insert code sample" menu option. Learn more! X

A part added in an EBOM does not get created as a new downstream part.

A part added in an EBOM does not get created as a new downstream part.

1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Business description: Design and manufacturing of logistics systems. Mainly development of automobile production lines.
Affiliation: Belongs to Manufacturing Department. Create an MBOM from an EBOM created by Engineering Department. Arrange a part by transferring MBOM information from Windchill to a production control system, which is another system.
2. What version of Windchill are you currently running?
Windchill PDMLink
Windchill MPMLink

3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
This is a problem that occurs when you propagate a change (a part added in an EBOM) to an MBOM.
When you select a part added in an EBOM from "Propagate Upstream Changes" in Manufacturing Associative Part Structure Browser and execute "Propagate changes to downstream", the EBOM will be copied to the MBOM side.
Instead of copying the EBOM, we want to have a new downstream part created on the MBOM side.



4. What is the use case for your organization?
(With the desired behavior described above,) when you add multiple parts on the EBOM side, new downstream parts can be added to the MBOM side all at once.
With the current behavior, we need to take the following steps to create new downstream parts one by one, which takes a lot of time and effort:
①Search for a part added on the EBOM side.
②Search for the parent of the added part on the EBOM side --> Select the MBOM corresponding to the parent of the EBOM.
③Select the added part on the EBOM side and drag and drop it to the MBOM.
④Select "New Part" from "Options".


5. What business value would your suggestion represent for your organization?
Since we are designing automobile production lines, the number of parts is large and the hierarchy is complicated, and there is a risk in the work itself of accurately propagating changes (parts added on the EBOM side to an MBOM.
Currently, changes on the EBOM side are not accurately propagated to the MBOM side, and due to designers' mistakes, problems occur when propagating parts added on the EBOM side to the MBOM side, which leaves some parts not arranged.
Also, for the above reason, users are showing reluctance to manage MBOMs in Windchill.
By making the above improvement for the problem, it will be possible to reduce users' time and effort and the risk of leaving parts not arranged.

Community Manager
Status changed to: Acknowledged

Hello @RM_8706315 and welcome to the Community,
Thank you for your idea and the information provided.

Status changed to: Delivered



Thanks for the idea.  This has been implemented in the system...


You need to allow this property


<AddToProperty name="com.ptc.windchill.associativity.reconciliation.addusage.wt.part.WTPart" value="transformOption=newPart"/>


In the \\Windchill\codebase\com\ptc\core\foundation\associativity\xconfs\ file


Hope this works for you...