Merge lp:~akretion-team/openobject-addons/addons-purchase-extensible-action-picking-create into lp:openobject-addons
Status: | Merged |
---|---|
Approved by: | Olivier Dony (Odoo) |
Approved revision: | no longer in the source branch. |
Merged at revision: | 5576 |
Proposed branch: | lp:~akretion-team/openobject-addons/addons-purchase-extensible-action-picking-create |
Merge into: | lp:openobject-addons |
Diff against target: |
144 lines (+75/-50) 1 file modified
purchase/purchase.py (+75/-50) |
To merge this branch: | bzr merge lp:~akretion-team/openobject-addons/addons-purchase-extensible-action-picking-create |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Olivier Dony (Odoo) | Approve | ||
Review via email: mp+79485@code.launchpad.net |
Description of the change
Hello,
This refactoring is the equivalent of the one you just merged in the sale module:
https:/
But this time it's in the purchase module.
It breaks down the monolothic generation of the purchase picking and receptions moves and make sure those objects can be customized or localized before they are created into the database.
This is very useful in localizations such as for Brazil where some fiscal code must be propagated from the purchase to the supplier invoice, passing through the picking.
This refactoring also permit to have several pickings for one purchase order, something useful for blanket orders or lines with drop shipping for instance.
It seems to me that, in line 63, the code would always create a new picking regardless a "picking_id" is provided.