c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #25362
[Bug 788064] Re: decimal_precision lost at product reception
Hello,
The problem was there because in class stock_move line no:1548 is as
below:
'price_unit': fields.float('Unit Price', digits_compute=
dp.get_precision('Account'), help="Technical field used to record the
product cost set by the user during a picking confirmation (when average
price costing method is used)"),
While actually it should be like below:
'price_unit': fields.float('Unit Price', digits_compute= dp.get_precision('Purchase Price'), help="Technical field used to record the product cost set by the user during a picking confirmation (when average price costing method is used)"),
Regards,
techreceptives
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/788064
Title:
decimal_precision lost at product reception
Status in OpenERP Modules (addons):
Confirmed
Bug description:
Sys: Ubuntu 9.10, OERP V602
I have a db with decimal_precision installed and purchase price set to 4 decimals.
I make a Purchase Order for a product with cost price of 0.0042.
The PO displays the price, and computes well everything.
When I go to the receptions, to receive the products, in the Product
to Process (stock.partial.picking) dialog I can see the price only
with two decimals, I mean 0.00.
After validating, the product enters in the database with price 0.00 ,
and not with 0.0042.
Arpi
References