Skip to main content
Aug 19, 2013 12:57 PM UTC
Archived

BOM table in Annotation should count by subassy

Related products:Creo Parametric

I have a drawing of an assy and this assy contains subassys. The subassys contain parts, shared in one or more other subassys. When I create a BOM table in Annotation, it will now count all instances of the shared part, ignoring the assy-structure. I would like to have the option to count them per level (per subassy).

6 replies

Aug 19, 2013 2:11 PM UTC

then i think you should use the option 'one level' when scanning the model in stead of 'all levels'.

this way the scan wil only look down 1 level, scanning the sub-assembly and not the parts. or is this not really what you mean?

I also think the BOM functionality should be expanded, so multi-level BOM's are possible. kinda like the BOM editor in Model Manager.

Aug 19, 2013 2:33 PM UTC

No, I really want "all levels". The shares in the subassys are intentionally organized that way and reflect some kind of assembly procedure. I need one comprehensive table of the top-level assy containing the BOM-information.

Aug 22, 2013 1:08 PM UTC

After generating the BOM, then create a report.  this will let you expand all of your subassemblies. You can expand the sub assemblies and included or exclude the sub assembly.

It takes a little time to develop your best practices that best suits your needs.  Once you do, you can generate your bill of materials very quickly.

Aug 22, 2013 1:15 PM UTC

I think your suggestion refers to the BOM-module, but I mean the BOM functions inside Annotation (without BOM license).

Aug 22, 2013 1:18 PM UTC

You are correct.  I have not used the BOM functions inside Annotation in a long time. 

Mar 17, 2019 2:27 PM UTC
Status changed to: Archived