openerp-india team mailing list archive

["Ferdinand @ Camptocamp" <943899@xxxxxxxxxxxxxxxxxx>]

IMHO I found an easy work around
define the parent as internal , add it as stock location in the warehouse and change the type to view afterwards

AFAICS - the computations work correctly and no one will be able to
create moves for the parent location

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/943899

Title:
  6.1.1 stock location - parent must be view

Status in OpenERP Addons (modules):
  New

Bug description:
  IMHO the design change from V5 to V6 is not helpful

  V 5.x

          'lot_stock_id': fields.many2one('stock.location', 'Location
  Stock', required=True ,
              help="(virtual) stock location to calculate available
  quantities. This and all children. Do not put stock locations at partner
  location here, the products can't be sold to others." ),

  V 6.1
          'lot_stock_id': fields.many2one('stock.location', 'Location
  Stock', required=True, domain=[('usage','=','internal')]),

  
  at a certain point in time everybody agreed that aggregates items (like it is implemented for accounts, analytic accounts ...) should be views to allow clear representation 
  (parent) view = sum of child items 

  Example
  parent = 5
  - child item 1 =2
  - child item 2 =3

  in stock location this principle is now violated

  parent = 6
  - item 1 =2
  - item 2 =3

  because the parent location can be of any type and stock moves can be
  posted at the level of parent.

  nobody will understand this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/943899/+subscriptions