Comment 7 for bug 1266664

I am currently operating OpenERP v7.0 with no pending updates. Since there
are no pending updates, I'm assuming there are no bugfixes I haven't
gotten. Still, I'm experiencing the problem you describe in your bug
report, as I understand it. That is, when calculating the cost of a bom, if
the purchase uom is different than the uom then the cost is applied with a
wrong factor.

I'm afraid that the switch to github has confused me. You say that bug
1266664 has been fixed and yet Launchpad has no sign of that. The FAQ for
the transition from launchpad to github says that bugs in launchpad will
not be transferred to github. I don't understand how anyone is tracking
which old bugs have been fixed.

I am a part-time amateur programmer. I've learned a lot to get OpenERP to
work but there is much left.

You say you have a module. What is the purpose of this module?

A search has led me to this conversation where you were involved.
https://www.odoo.com/forum/help-1/question/is-there-a-product-extended-for-v7-4258
I'm not sure if this is telling me to use product_extended instead of
product_cost_incl_bom.

The more I dig into this problem, the more it seems I'm not suppose to have
it. ;)

Gilles Lehoux <email address hidden> www.isogarde.com
Isogarde inc. Tel. 450-472-8128 Tel. 888-472-8128 Fax.
450-472-5207

On Tue, Mar 24, 2015 at 3:01 PM, E.R. Spada II <email address hidden>
wrote:

> As for the BOM issue, it was updated in product_extended.py, but the
> forgot to / produc_effecieny on the cost so I add it to my module. Plus I
> added a cron to update all the standard cost products with a BOM. I can
> have it if you want it.
> ER
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1266664
>
> Title:
> Calculated BOM is incorrect when Purchase UOM is different from
> product default UOM
>
> Status in OpenERP Financial controlling and costing:
> New
>
> Bug description:
> Hello,
> I found a bug that was fixed by OpenERP Enterprise Contact. Please see
> lp:~openerp-dev/openobject-addons/7.0-opw-599727-fka this fixed a bug that
> the UOM on the sale order line is incorrect when the UOM and purchase UOM
> are different. Since your module also uses these fields, it now creates the
> incorrect BOM cost. It divide the cost by the purchase UOM.
>
> For example if the product is sold as a Unit, and the Purchase UOM is
> Case of 50. When the cost is calculated it is divided by 50. If you review
> the simple changes in lp:~openerp-dev/openobject-addons/7.0-opw-599727-fka
> it is quite obvious.
> ER
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/margin-analysis/+bug/1266664/+subscriptions
>