[15.0][FIX] purchase_request_operating_unit: operating unit when purchase request is created based on procurements #597
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable the route MTO or dropship in a product. Then try to create a sales order for that product in another operating unit than the main operating unit. This constraint will raise: https://github.com/OCA/operating-unit/blob/15.0/purchase_request_operating_unit/model/purchase_request.py#L56, because it will try to create the purcahse request for the main operating unit, instead the operating unit of the procurement, which is the operating unit of the sales order.
cc @ForgeFlow @BT-pcavero