Showing results for 
Search instead for 
Do you mean 
Reply

Populating EOs

Hi All,

 

I am looking for a way to avoid human error when populating EOs with parts and assemblies.  In particular, when I need to revise and release a component, I want to ensure that the parent parts which use that component are also pulled into the EO. 

 

Our current method requires a user to use the "Impact Analysis" on a part, perform the where-used on all levels, then copy and paste all part revisions for each parent into the EO.  This is obviously very prone to mistakes due to Human error.

 

Is there a Teamcenter preference or other method that will allow all parents to be pulled into the EO folder when a child is added to the folder?

 

Thanks,

Brian