I have a multi level BOM with Subassemblies and i’m having a hard time getting the top level assembly roll up costs (on this page: “…/part/11/component_list”) to be accurate. In some cases, certain parts in the indented BOM are not showing a price, just $0.0000 but inside the BOM, the accurate price exists…see image below. Both pages were simultaneously displayed in 2 browser instances…
Also, why is the rollup value in parentheses? Some items on this page: “…/part/11/component_list” show up with parentheses and some do not…(see red highlight)
Fortunately there are some straightforward answers to your questions there!
First, on the BOM overview screen, you’re comparing the rollup cost to the “cost” column on the BOM Edit screen. You need to unhide the “Cost Record” screen on the BOM overview. It’s that “cost record” value that should be the same as the “cost” column on the BOM Edit screen.
Second, if you hover over the parenthesis you’ll see it reads: “Not a BOM, part Ext Cost used”. Rollup is only calculated for BOMs. So, instead of Rollup, if it’s not a BOM, it will use the “cost record” extended. The reason why you see some raw component items in the BOM overview that do not have the parenthesis is because those have BOM records with zero components inside of them (blank BOMs). If you removed those BOMs from their part record, you would see the parentheses.
So on the first topic: I don’t think this answers my question. Isn’t the total Rollup for Qty SUB000001 “unit” cost suppose to include the RAW000007 part cost? so the Material cost should be $10.77207 PLUS $45.53? this feeds in the unit cost which is incorrect…
IF not, how do i get the overall BOM cost of this assembly? because the current unit cost is incorrect…
Do you mean clicking on the “remove as BOM” button? if so, i’m not sure we can do this as this part has had many revisions and we document the “change” of these parts using the ECO process (which requires “parts” to be BOMS if you want to capture revision changes)
I think the best short term workaround would be to go ahead and click that Remove As BOM button, and keep it as a normal raw component by default. (After you remove as BOM, you may have to refresh the browser once or twice to see it propagate).
Then, in the future, if/when an ECO is needed for that particular component part record, you can add the BOM record back to it during the ECO process, then remove the BOM again when the ECO is concluded and the rev is updated.
I realize that’s a wonky workaround… longer term we could potentially look at getting to support ECO rev changes on raw components instead of requiring the BOM.
do you know if the roll-up cost calculation changed in your system recently? I seem to recall in that recent past
(6 mo?) that this roll-up cost would include the component cost, even when the BOM items might have had zero components…I could be mistaken though…
