Warehouse stock locations should be internal location

[Numérigraphe]

For the moment the stock location in a warehouse can by any type except "view".
I suggest it would make sense to allow only "internal" locations.
Lionel Sausin.

[Amit Parik (amit-parik)]

Hello Lionel,

Thanks for the reporting!

As per my Opinion it's good suggestion and it should be improve.

Your patch is fine...nice catch..:)

Thanks again.

[Nhomar - Vauxoo (nhomar)]

IMHO, view location never should accept moves, when you see "stock by
location" view, it can give numbers that need analisys to have sense,
making dificult use this feate, ioh, if you have a parent location where
you want that receive moves, just change its type and ready.

But by default it is working fine.

Regards.

my 2cents

[Numérigraphe (numerigraphe)]

Dear Nhomar Hernandez,
The problem here would be a warehouse configured with a stock location type "inventory", "customer" etc.
That would not make sense would it ?
Lionel

[Fabien (Open ERP) (fp-tinyerp)]

thanks for the fixed, applied in trunk r5590

[Ferdinand (office-chricar)]

in stock.py (trunk)

./stock.py:2753: 'lot_input_id': fields.many2one('stock.location', 'Location Input', required=True, domain=[('usage','<>','view')]),
./stock.py:2754: 'lot_stock_id': fields.many2one('stock.location', 'Location Stock', required=True, domain=[('usage','=','internal')]),
./stock.py:2755: 'lot_output_id': fields.many2one('stock.location', 'Location Output', required=True, domain=[('usage','<>','view')]),

this seems not to be fixed completely

IMHO lot_input_id and lot_output_id must be internal too
or do I miss something ?

Exmple
purchase.py
uses lot_input_id as destination...