diff options
| author | Simon Lejeune <sle@openerp.com> | 2018-10-25 12:25:50 +0000 |
|---|---|---|
| committer | Simon Lejeune <sle@openerp.com> | 2018-10-25 12:25:50 +0000 |
| commit | d5c31e231aecc130b695f914441a6c6d29b02f0a (patch) | |
| tree | a703806fc670a7ec4f6ccdda921fcd9405eba5b0 /doc/reference/javascript_reference.rst | |
| parent | 5494b0bc3eec6bb063017eaec61fd312c880e4b8 (diff) | |
[REV] mrp: block updating live BoM
This reverts commit d78b6f5e25eb7bf36aef57d1ae1c5c6e51d1ec7b.
This constraint is considered too harsh. It was applied to circumvent
inconsistencies when a bom is modified while being used in a
manufacturing order and the user chose to update the quantity to
produce. The current code will look at the existing move if no
intermaddite post of inventory was done else look at the new bom.
A code to re-construct the original BoM from the stock moves isn't easy
to write to handle all cases, one particularly complicated is the
deletion of bom lines of the same product.
We also considered to block the update qty button if the bom is modified
after the create date of the MO, but if we have to read all the bom
lines of all the sub bom in a computed field it may be slow on large
databases.
We thus chose to remove the constraint and think of a better approach in
a future version.
task 1891407
closes odoo/odoo#28155
Diffstat (limited to 'doc/reference/javascript_reference.rst')
0 files changed, 0 insertions, 0 deletions
