Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[17.0][FIX] mrp_multi_level: when a product is a kit do not check rule #1403

Merged
merged 2 commits into from
Nov 28, 2024

Conversation

LoisRForgeFlow
Copy link
Contributor

When you procure a kit, it doesn't matter what the route configuration is on the product itself but on its children, so it is not needed to check anything else but the BoM to assign the 'phantom' supply method.

Also do not assign a BoM when the supply method is not phantom or manufacture.

Fwport of #1401

When you procure a kit, it doesn't matter what the route configuration
is on the product itself but on its children, so it is not needed to
check anything else but the BoM to assign the 'phantom' supply
method.

Also do not assign a BoM when the supply method is not phantom or manufacture.
@OCA-git-bot
Copy link
Contributor

Hi @ChrisOForgeFlow, @JordiBForgeFlow,
some modules you are maintaining are being modified, check this out!

After odoo/odoo@1ed6dbe
we need to explicitly set routes in the propoer order becouse while
in the cache there are not yet sorted by sequence (it requires flush
to the database, which we cannot do in a test).
@LoisRForgeFlow
Copy link
Contributor Author

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

This PR looks fantastic, let's merge it!
Prepared branch 17.0-ocabot-merge-pr-1403-by-LoisRForgeFlow-bump-patch, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 6c60629 into OCA:17.0 Nov 28, 2024
7 checks passed
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at 9e80ec8. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants