c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #25820
[Bug 779145] Re: [stock] store price_unit for all stock moves, and use it for suggesting return picking values
thanks for clarification, but IMHO the analysis is not complete.
please consider that the way
./report/report_stock_move.py
calculates the product value does not return historical prices.
hence doing the anlaysis every month (for products with average price)
it will likely return different values for past month (as it uses the
current avg price) . this can't be explained as (useful) feature of
Openerp.
hence arguing that the price_unit is not used - although it should be -
can't be an argumetn to not store it.
--
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/779145
Title:
[stock] store price_unit for all stock moves, and use it for
suggesting return picking values
Status in OpenERP Modules (addons):
Confirmed
Bug description:
In OpenERP 6.0 stock.move has a price_unit field for storing the unit
cost price of the products, but this field only has a value for
incoming pickings on products with average price (because it is used
by the picking wizard in that case).
We should change the stock module to make sure the unit price is always written in that field, also in the other cases (we must also preserve the current behavior for
incoming pickings, which means we should store the value that was set by the user in the picking wizard, not always the current average price.).
Finally, we should use this price_unit column to suggest a cost price when doing a return picking. We should suggest the price_unit value of the stock moves we are
returning, instead of suggesting the current product price, as previously discussed in bug 613286. The tooltip should also be updated, etc.
======= (original description below) =======
to be able to calculate the stock value for every point in time for avg price and real time
obviously for accounting purpose real time we must have
account_balance == stock values
and must be able to proove it
if (pick.type != 'in') and (move.product_id.cost_method == 'average'):
if all stock moves have the price_unit field set:
qty * price_unit= move_value
and sum(+/- move_value)
enables to calculated the total stock value per product in every point of time matching the account balance
a little step further will be to calculated the average price per
stock_location and lot
References