diff options
| author | Arnold Moyaux <arm@odoo.com> | 2018-03-20 16:42:19 +0100 |
|---|---|---|
| committer | Arnold Moyaux <arm@odoo.com> | 2018-03-27 17:36:44 +0200 |
| commit | b33d5af4a74e3f4ca515826d4683065e32005e85 (patch) | |
| tree | 9b5f4d2e30ac8ec8c07bc2a1c40215b1a703a74a /addons/web/static/tests/fields/relational_fields_tests.js | |
| parent | f22c5794c48158e48371666068b5435bb94b18ab (diff) | |
[FIX] stock: allow to validate a picking with 2 extra moves
Use case to reproduce:
- Create a picking containing 2 moves that have a quantity_done greater than reserved quantity
- Validate the picking with or without backorder
Traceback due to a record that do not exist anymore.
It happens due to 2 functionality that have a wrong behavior when used together:
- merge_move function that will try to merge moves with same characteristics inside a same picking.
- action_done functionality that will create an extra move if the quantity done for a move is greater
than reserved quantity. (the extra move is used in order to propagate changes)
With our usecase:
- MOVE A, reserved_qty: 10, qty_done: 20
- MOVE B, reserved_qty: 10, qty_done: 15
action_done on move A will create a new move thus we will have
- MOVE A, reserved_qty: 10, qty_done: 20
- A bis, reserved_qty: 10, qty_done: 0
- MOVE B, reserved_qty: 10, qty_done: 15
then merge move will not only merge move A and A bis but will also merge B
which result with inconsenstencies and traceback since system will try to
process move B after A
- MOVE A,A',B reserved_qty:30, qty_done:35 (the 5 extra qty is not propagated)
This commit adds a kwarg in action_confirm that is propagated to merge_move
this kwargs is a record set taht will limit the moves that can be used for the merge
in order to merge extra move in original move
opw-1825264
Diffstat (limited to 'addons/web/static/tests/fields/relational_fields_tests.js')
0 files changed, 0 insertions, 0 deletions
