This content has been marked as final. Show 2 replies
The solution you mention is the only way I am aware of to do what you want...having an IntegerFeature as an intermediate value, whereby your rules contribute a default value to the IntegerFeature, the user has visibility to and can increase or decrease the IntegerFeature value, and the IntegerFeature then contributes its value to the appropriate BOM Item.
(The IntegerFeature must be defined with no Minimum value, or a Minimum that is less than zero, or else it is technically a CountFeature, and this approach will not work. If you need a Minimum value for the IntegerFeature that is equal to or greater than zero, it would need to be achieved with an additional Logic or Comparison Rule.)
As you suggest, the maintenance becomes a challenge if the solution must scale to many such intermediate IntegerFeatures. But I am not aware of a better, less burdensome route.
You can reduce the quantity using "Consumes from" wherever it s required.
Pls revert back if need more details.