The PTC Community will be on read only status starting March 23rd in preparation for moving our platform to a new provider. Read more here
Version: Windchill 12.1
Use Case: Hi, we have got this situation: - "12345" Part Number ( Design) -> New Downstream Part "12345_100" (Manufacturing Plant 1)
Description:
Now we should create
-> New Downstream Part "12345_100" (Manufacturing Plant 2)
If I try to create, Windchill tell me that PartNumber already exist,
How can we do?
Any idea?
Best regards
Gianpaolo
Solved! Go to Solution.
This is very much possible. First , You will have to restructure your View Hierarchy as below.
Then transform your Design BOM to Mfg using the New Downstream part action as mentioned by you. This will be your Master or Plant Neutral BOM. From manufacturing you can then transform to Plant1, 2 and so on using the New Downstream Branch action instead of new downstream part. This way you will have the same number for the part to be used in multiple plants and subsequent push to ERP.
I would recommend you do a thorough testing with this setup. NOTE that the view hierarchy changes will NOT be possible once transformations are carried out based on a particularly view hierarchy. So plan the View hierarchy upfront. Spend as much time possible to brainstorm with multiple stakeholders before finalizing anything putting in Production.
Hope this helps.
Regards
~Syed
refer to below demo (basically cerate a new view version of Mbom and then create EQL manually )
Hi Fede,
really thanks for your quick reply.
But Windchill 12.1 seems not to have such an action.
Maybe is there an option to activate?
Below the Manufacturing Action Page.
Best regards
Gianpaolo
Hi @GianpaoloGallo,
Are you logged in as an Administrator?
If not, you will need to be granted the new view version access through ACLs.
It should be there , make sure the part is not checked out and part is revisable (No permission lack and revise transaction defined for that state ) ,see https://www.ptc.com/en/support/article/CS96009 for more details
It seems it doesn't work also as admin.
Just to share
This is the Views RelationShip we have:
- Design
Manufacturing
Plant 1
Plant 2
Plant 3
And using the feature "New Part View",
it seems that there is no way to create the View Plant 2 starting from the View Plant 1
Any idea?
Best regards
Gianpaolo
yes you are right ,the plants are leaf views they have no child views but you can open the design view and create new view for plant2 , below video from my 12.1 :
Hi Fede,
so it means that with a configuration like mine
"
Design
Manufacturing ( Actual not used)
Plant 1
Plant 2
Plant 3
"
If, in some cases, I use the Scheme
Design Part Number (A) -> Plant 1 Part Number (A_100) NEW PART
I cannot create the Plant 2 Part Number (A_100)
Please Did I understand correctly?
Best regards
Gianpaolo
What Can I do to manage such a scenario?
We have got multiple plants and brand only some of them need to work with such a feature.
Best regards
Gianpaolo
The second time ,you ask the system to create new part with same number , this does not make sense , you can not create 2 part with same number this is not MPM specific
Thanks Fede,
Maybe I've not described exactly what we are trying to set.
We wish to have a unic Same End_Item_A as the cad bom is unic for different Manufacturing Part Numbers.
Where the manufacturing Views have different structures.
In this way, I thought to manage with a unic design for multiple Manufacturing BOMs and then send them to ERP.
The "Red cases below" are the "views" I would like to have.
Is it so unrealistic?
Many thanks for your availability.
Best regards
Gianpaolo
This is very much possible. First , You will have to restructure your View Hierarchy as below.
Then transform your Design BOM to Mfg using the New Downstream part action as mentioned by you. This will be your Master or Plant Neutral BOM. From manufacturing you can then transform to Plant1, 2 and so on using the New Downstream Branch action instead of new downstream part. This way you will have the same number for the part to be used in multiple plants and subsequent push to ERP.
I would recommend you do a thorough testing with this setup. NOTE that the view hierarchy changes will NOT be possible once transformations are carried out based on a particularly view hierarchy. So plan the View hierarchy upfront. Spend as much time possible to brainstorm with multiple stakeholders before finalizing anything putting in Production.
Hope this helps.
Regards
~Syed
