cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Phantom attribute should not be a Master Attribute. Different plants may designate the same component differently.

Phantom attribute should not be a Master Attribute. Different plants may designate the same component differently.

Status: Archived Submitted by 1-Newbie on ‎Nov 16, 2015 03:28 PM
1 Comment (1 New)

The Phantom attribute is currently a Master Attribute.  However, at Boston Scientific, one plant may designate a component as a Phantom whereas a different plant may not.  This is troublesome in MPMLink whereas a user cannot perform part allocation on Phantom parts.  Additionally, SAP sets this a the plant level.  We are in the process of implementing MPMLink Process Plans to author these in Windchill and integrate to SAP.  Today, Process Plans (Routers) are authored in SAP.  Since plants have different designations for the component as being or not being a phantom, migrating the Routers to Windchill Process Plans poses an additional challenge.

See more ideas labeled with:
1 Comment
olivierlp
Community Manager
Community Manager
‎Jan 05, 2022 10:59 AM
‎Jan 05, 2022 10:59 AM
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.