On Tue, Sep 27, 2011 at 10:41 AM, Fabien (Open ERP) <email address hidden> wrote:

> I propose to set this as a wishlist. It's too risky to merge the proposed
> branch as there is a lot of side effects to handle if we want to store the
> price_unit in the stock.move:
>  - inventories,
>  - stock.moves are created way before they are processed (and the cost
> price can change)
>

Hello, in fact is why this features is needed you need to see cost price
variation in stock moves timeline.


>
> If you base reporting on this, you may have a lot of troubles. I think it's
> important that reporting remains on standard prices rather than a price on a
> stock.move.
>

Stock move happens one time, and price what happened need to be stored (not
related).

Please review the importance of this feature in accounting world.
IMHO has not this features is locking 6 months again and
unnecessary efforts.
New features is not only new toys (agree with @nhomar) is about include
features forgotten.

Regards,

>
> So, I think it's too risky to merge the proposed branch for now on and
> we should do a complete project to ensure it's clean.
>
> ** Changed in: openobject-addons
>   Importance: Low => Wishlist
>
> --
> You received this bug notification because you are subscribed to OpenERP
> Addons.
> 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 Addons (modules):
>  Fix Committed
>
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-addons/+bug/779145/+subscriptions
>



-- 
Cristian Salamea
@ovnicraft