(Confirming and assigning to R&D)

** Description changed:

+ 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 
+ 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) 
+ 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

** Description changed:

- 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).
+ 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.).
+ 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.
- 
- 
+ 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

** Changed in: openobject-addons
   Importance: Undecided => Low

** Changed in: openobject-addons
       Status: Incomplete => Confirmed

** Changed in: openobject-addons
    Milestone: None => 6.1

** Changed in: openobject-addons
     Assignee: (unassigned) => OpenERP R&D Addons Team 2 (openerp-dev-addons2)

-- 
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

_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help   : https://help.launchpad.net/ListHelp

Reply via email to