diff options
| author | Arnold Moyaux <arm@odoo.com> | 2020-02-04 13:23:28 +0000 |
|---|---|---|
| committer | Arnold Moyaux <arm@odoo.com> | 2020-02-13 13:56:31 +0000 |
| commit | 1508705ab481a21f48f1aea2e635c51cc278e11e (patch) | |
| tree | e5247965e576b3245b1927a44255a29b1bba7c3d /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | 02fd561e7ed4ad19dc703b9e9d24033538d72eaa (diff) | |
[FIX] mrp: incorect production duration for MTO process
Usecase to reproduce:
- Create a product MTO manufacture with a BoM
- Set produce delay as 1 day.
- Create a SO for the product and validate
The production order is created but with a duration of 1h.
It's due to commit 8944674d6da8a64b1fbc1dff034e82f7052be1b2
It will use the moves finished date in order to determine the MO
finished date. However before this commit during _run_manufacture
the MO was created with a fix finished date and the move finished
date_expected was created with this date as date_expected.
Now the MO is created with the finished date, the inverse does
nothing since the finished moves do not exist yet.
In order to fix it, generate move_finished_ids use the product/company
manufacture delay. A first patch tried to rewrite date_planned_finished
after action_confirm. However it triggers the propagate date on
following moves.
closes odoo/odoo#44532
Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
