Sage 100

Anyone run into an issue like this on v4.4 where the BOM math doesn't foot? I'm looking at a couple possible product defects with Sage but figured maybe this is something that has been seen.

Have you verified the BOM has components?

What @MarkKotyla said.... Run the Bill Validation Report.

Wayne, check the calculations of the components where the UOM is EACH. This does odd things to the calculations of non-whole integers.

I'm throwing it to Sage after they install the one patch that I uncovered in the KB

Installed the 4.5 patch (they were on 4.5 vs the 4.4 I thought they were on). No change. Opening support case with Sage. I find BOM can be problematic to debug so I like to get Sage involved early so as not to have to spend an hour or two then another hour getting Sage up to speed.

v4.5 client also had issues. As I recall, theirs was attributable to the lower level bills not rolling up properly. Sage said it was a WAD.. Sigh.

@MarkKotyla wins on this - the subassembly had no components. We deleted the BOM (sub) and the report was fine. The trick here is that you can run the report for a selection (which ran with WRONG totals) or for a specific bill - which produced accurate totals.

I remember the same issue when selecting different ways. What a pain.