Wednesday, September 18, 2024
2 changes · saas-17.2
Resolved issues and error corrections
Users can now remove a component from a confirmed manufacturing order without triggering an error when saving. This prevents an interruption in manufacturing order updates and lets teams correct component lists as expected.
Original PR description
Steps to reproduce: - Create an MO and confirm it. - Remove any component (`move_raw_ids`). - Save the form. Expected behavior: The component should be removed. Current behavior: A traceback appears. This is because the `write` of the `mrp_production` always tries to destructure the value of `move_raw_ids` into a `Command` tuple of three elements, which is not the case when deleting on of the components, where the tuple consists only of two elements: the `DELETE` constant and the id of the removed record (no values element). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures warehouse push rules can be applied when stock moves originate from a sub-location, not only the exact configured location. It helps inventory routes behave consistently and reduces manual intervention when goods are redirected within warehouse location hierarchies.
Original PR description
The changes made in #156437 had the purpose of adding more flexibility in the moves, being able the re-route them on the fly, without having to bother with the whole chain being already created. And while the search for pull rules properly look for parent location if no rule is found within the givin location, it wasn't the case yet for push rules. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr