credativ team mailing list archive
-
credativ team
-
Mailing list archive
-
Message #02093
[Bug 907727] Re: warehous location ids must all be internal
Hello Dr Ferdinand,
I have checked your bug report, this is not a bug but I think you have
might misunderstand something because current code is fine.
Let me explain the whole thing.
For input location we have not used only View type location so we have
used a domain [('usage','<>','view')]) because input location have
either type internal or it may be
"Customer","Supplier","Inventory","Production", or "Procurement".
Same location type also available for Output location and one more thing
for using this domain we can also seen the internal location..;-).
So I think all are working as expected.
Correct me If I am wrong..:-).
Thanks for understanding!
** Changed in: openobject-addons
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/openobject-addons/+question/182660
--
You received this bug notification because you are a member of OpenERP
Framework Experts, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/907727
Title:
warehous location ids must all be internal
Status in OpenERP Addons (modules):
Invalid
Bug description:
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')]),
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...
similar to
https://bugs.launchpad.net/bugs/882481
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/907727/+subscriptions
References