Josse Colpaert
219809a5a8
In v7, it could be in handy that when altering the quantities of a move, it would automatically update the next chained move as you could change quantities on the fly without any relation to the original documents. From v8, this is all being handled by extra moves which might e.g. follow a different route, so you still know what is related to the original procurement. But the functionality stayed in the code for who would still need it. In v10 and in previous versions, manufacturing orders however still use these moves. When we update the quantity on a halfproduct (which we can do now all the time in v10, it could change the consumption where it is used in the finished product (in MTO) That is why it is better to remove this functionality. (it might also speed up the split method on stock_move) The propagation of quantities was something from v7, that now causes trouble in mrp for nothing
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
If you are a developer you may type the following command at your terminal:
wget -O- https://raw.githubusercontent.com/odoo/odoo/9.0/odoo.py | python
Then follow the developer tutorials
For Odoo employees
To add the odoo-dev remote use this command:
$ ./odoo.py setup_git_dev
To fetch odoo merge pull requests refs use this command:
$ ./odoo.py setup_git_review