diff options
| author | Arnold Moyaux <arm@odoo.com> | 2019-06-14 14:23:22 +0000 |
|---|---|---|
| committer | svs-odoo <svs@odoo.com> | 2019-07-31 12:37:38 +0000 |
| commit | 3d4c0f92af86e534bc44ed48eb0ebf2ade3f7a92 (patch) | |
| tree | f7c9317f23e8643600b5a4d8a58d44fab9857853 /addons/mrp/wizard | |
| parent | c76fcd87c513b74cebea3a318c33f06fb03cafa9 (diff) | |
[FIX] mrp: log activity on parent MO
Usecase:
- Set table top as manufacture and MTO
- Create a MO for table(MTO)
- Confirm the MO
- Cancel the MO
The activity with the exception is not logged on the child MO
It happens because the _get_upstream_documents_and_responsible for move
linked to a MO is based on the created_production_id field. However it
is only set on the move that created the move_finished_ids for the new
MO. In the case of a MO that directly create a child MO the chain is:
MO -> move_raw_ids -> move_finished_ids -> MO2
The log_activity on cancel is based on the move_raw_ids and their
move_orig_ids in the previous case it's the move_finished_ids for MO2.
However the move_finished_ids for MO2 is directly link to the child MO
and the created_production_id is set on the move_raw_ids for MO parent.
Compare to PO, we could directly base the parent document on production_id
since the move_finished_ids are directly created.
Diffstat (limited to 'addons/mrp/wizard')
0 files changed, 0 insertions, 0 deletions
