SageForum for UK versions of Sage 50- Help and support.

Can anybody help please ?

We have just started using BOMs but we find that the total price shown against the BOM does not reflect the total of all of the individual component prices. I have set up a trial BOM with only three components in it to try to determine where the differences may exist in their background data but have not been able to find the root cause.
I have looked at and compared the obvious data fields for the sub-components, such as purchase price, cost price, nominal purchase code, nominal sales code.
Can anybody advise me as to what data fields could be affecting this and how deep do I have to dig please ?

The cost price should be the sum, the sale price is independant.

brucedenney wrote:The cost price should be the sum, the sale price is independant.

Thank you for your reply on this. I do understand what you are saying but maybe I didn't make my problem clear enough.
The situation is that the total price shown for my test BOM (with only three items in it) does only include two out of the three cost prices. I can't determine why it won't pick up the other cost price. This has happened for BOMs with more parts in them aswell so I just concentrated on a very small BOM to try to get to the root cause. With the larger BOMs it was too difficult to find which prices had been left out.
I would prefer it if I could get Sage to pick up the individual component SALES prices but the cost prices would be a great step forward.
Any help would be greatly appreciated. Thanks

Are you sure that the stock used to make the assembly had been entered into stock at the correct cost price?

brucedenney wrote:Are you sure that the stock used to make the assembly had been entered into stock at the correct cost price?

Well, each of the components have a cost price shown on their individual product detail screens.
Is that what you mean ?

No

I mean the cost that they were entered into stock at as shown on the activity screen.

The cost price on the detail screen is what will be used by default next time a transaction happens