We’re working with BOMs that have multiple operations that all have required materials that are static no matter what configuration options are chosen. When looking at the price rollup options within Configuration Maintenance the available choices are:
-
Parent: Only the parent stock item is the source of the configured price. (Fixed price)
-
Children All: The selling price is calculated as the rolled-up selling price of each option,
including any fixed materials on the bill of material, times the quantity of each option.
-
Children CFG: The selling price is calculated as the rolled up selling price of each option, excluding any fixed materials on the bill of material, times the quantity of each option.
-
Parent/Children: The selling price is calculated as both Parent and Children All.
We’re selling larger ticket items and prefer to price things as whole numbers. So ideally we’d prefer to set a base price for the parent part number that accounts for the cost/price of the static materials within the BOM and then add the price of the options chosen.
The first two list options are not candidates for us to use.
Children CFG would exclude the base price of the parent but does bring in just the standard price of the option selected itself and avoids the pricing of child materials within those options that might get blown into the final BOM. Because it excludes the parent price and the parent default BOM contains static materials/costs we need to account for, we’d have to throw some kind of a dummy option within the options and make it required to account for that base cost/price. This would increase the need for maintenance, but I don’t think could be an option, just not ideal.
Parent/Children uses the parent price and the price of all the individual materials that get brought into the BOM from the options chosen. This results in smaller dollars and cents in the total price of the configuration as our material within builds range from small ticket items (stickers and warning decals as an example) to items that are thousands of dollars. The small ticket item’s sale price for part replacement to customers use a standard markup that results in odd cents in the pricing which we would like to avoid when used in BOMs for pricing parents.
Using the descriptions of the current settings available above, we would need the combination of “Parent/Children CFG.” This would allow us to set an even number as the base price for the parent and the the configurated options pricing would stack on top of that.
I’m looking to see if I’m missing anything that would allow me to achieve the outcome I’m looking for and/or if anyone else has ideas of how to achieve the outcome outside my idea of using the Children CFG with a dummy material.
