Skip to main content
J
jselland1-Visitor
1-Visitor
August 5, 2013
Question

Can a BOM be created for an inheritance feature in a part drawing?

  • August 5, 2013
  • 1 reply
  • 1661 views

Hello, I'm trying to use an inheritance feature for machined castings in part mode rather than adding machining operations in assembly mode (mainly for chamfer/round functionality). So I create a part, insert inheritance feature, and make cuts, holes, chamf, etc to the part. Then, when I create the drawing for the machined part, is there a way to make a functional 1 item bom that shows the name of the model used for the inheritance feature? Instead of a fake bom that you type in manually.

Using WF5 (M100) or whatever it is called now

thanks


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

D
dgschaefer21-Topaz II
21-Topaz II
August 5, 2013

Your inheritance feature should have a feature parameter named 'MERGE_BASE_PART' that contains the file name of the reference part. You should be able to show that in a note in the drawing. Enter '&MERGE_BASE_PART:FID_122' replacing the '122' with the feature id of your inheritance.

J
jselland1-VisitorAuthor
1-Visitor
August 5, 2013

Thanks doug. Is it possible to reference more parameters from within the merge base part (like description) in a table to mimic a BOM? Also, is there any way to automate this instead of having to key in the feature id? I think i'm pressing my luck but can't hurt to ask.

thanks

D
dgschaefer21-Topaz II
21-Topaz II
August 5, 2013

Not that I'm aware of on both accounts. I just tried to pull in other parameters and wasn't able to figure it out.

If you rename your inheritance feature you can use the name in place of the feature ID:

&MERGE_BASE_PART:FID_NAME

It might help a bit in that you don't have to figure out the ID.

Terms & ConditionsAccessibility statement