This commit introduce the immediate production mechanism. As it works on stock.picking, marking a (some) production(s) as done without consuming anything will pop a wizard allowing the user to transfer all the reserve component quantities as done quantities. Task : 2278147
Now, by default, a Bill of Material have a flexible consumption instead of strict consumption. Also add new consumption choice: a flexible consumption but with a warning when the bom isn't respected. Also, now, the strict (a new warning option) consumption is checked only when we try to mark as done the MO. task-2241471
Use a view similar as the pickings one. task-2241471
Allow to "backorder" a production, meaning create another manufacturing order with the quantity remaining to produce. We also use the reservation of the first order on the next ones by using `post_inventory` on the first one and moving the newly created stock moves to the backorder. We introduce a wizard similar to the one in stock. Backorders have a sub-sequence. Backorders are linked together through the procurement group. We allow creating a backorder even if workorders are running by closing them, the backorder will call `button_plan` and create its own. task-2241471
This implements a warning when the user tries to do any of the following operations on a product that is not in stock: - Scrapping - Unbuilding - Repairing The warning displays the current stock of the product in question per location which can be helpful in case the user selected the wrong location.
* LDAP import: python-ldap is not python3-compatible, pyldap is Warning: only supported from debian Stretch (current testing)? https://packages.debian.org/search?searchon=names&keywords=pyldap * implicitly relative imports * imports of moved or removed stdlib modules issue #8530
Split files and move them according to the new API guidelines. Containing - mrp splitted into its main models and files - stock code moved into its own models and files - various renaming
- Preserved explicit 3rd-party copyright notices - Explicit boilerplate should not be necessary - copyright law applies automatically in all countries thanks to Berne Convention + WTO rules, and a reference to the applicable license is clear enough.