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

Wrong bom filtering for multi variant products #1211

Open
wojtek1044 opened this issue Feb 22, 2024 · 1 comment
Open

Wrong bom filtering for multi variant products #1211

wojtek1044 opened this issue Feb 22, 2024 · 1 comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@wojtek1044
Copy link

wojtek1044 commented Feb 22, 2024

Module

mrp.multi.level

Describe the bug

Wrong bom is selected for explosion when product template has many variants. Procurement is calculated from first bom of the product template list, not regarding to ID from product.product module.

To Reproduce

16.0 community

Steps to reproduce the behavior:

  1. Make demand for product with defined variants and different boms for every variant (mrp.bom.product_id defined)

  2. Run MRP multi level

  3. Check plans for affected subproducts

  4. Rearange bom list in view
    image

  5. Again run MRP multi level and check procurement plans

Expected behavior
When product has defined variant and bom for that variant - predict procurement according to the right bom.

Additional context
Add any other context about the problem here. (e.g. OS, Python version, ...)

@wojtek1044 wojtek1044 added the bug label Feb 22, 2024
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

1 participant