Allow adding BOM_REPORT_QUANTITY for bulk items to the family table to manage varying quantity
1. Describe the Problem
When using family tables to manage product variants of different geometric size, eg. height/width variants, the quantity needed for a bulk item, e.g. glue or paint will often depend on the actual size variant.
So there is a need to control the value of BOM_REPORT_QUANTITY individually for each instance in the assembly family table.
However, Creo does currently not support that is explained in https://www.ptc.com/en/support/article/CS214511
"BOM_REPORT_QUANTITY" can be driven from bulk template or bulk component only to avoid conflict of drivers for this parameters.
Please consider resolving this constraint to allow the same variability for bulk items as for other types of components in family tables.
2. Are you using a workaround?
We are using an "overloading" methodology for family tables with few instances, where a bulk item for the same material is created or assembled into the generic assembly as many times as there are different quantities needed across all the instances. Then each bulk item is added to the familly table as a component column, and for any given instance, only the one relevant bulk item is marked as "Y" while the others are suppressed with "N". However for our larger family tables with +40 instances and maybe 3-4 different types of material going in as bulk item that is an ugly workaround which will cause the amount of columns in the family table to explode.
3. What is the use case for your organization?
The idea would allow a much more consistent approach of using of bulk items to represent the use of non-each quantity type materials, and drive related WTPart structures including those materials from the CAD structures, rather than having to maintain the consumption of those materials in different ways, including maintenance for all variants independently in the WTPart structures.
4. What impact does this problem currently have on your organization?
+200 users affected by non-consistent way of working with bulk items, depending on the actual use cases. Bigger family tables which are more difficult to handle and overview.
