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

[16.0][BUG] mrp_multi_level: phantom/kit planning is broken #1362

Closed
matt454357 opened this issue Oct 15, 2024 · 1 comment · Fixed by #1384
Closed

[16.0][BUG] mrp_multi_level: phantom/kit planning is broken #1362

matt454357 opened this issue Oct 15, 2024 · 1 comment · Fixed by #1384
Labels

Comments

@matt454357
Copy link
Contributor

Version 16.0 module mrp_multi_level is calculating incorrect demand quantity for component lines of kit/phantom BOMs.

Versions 14.0, 15.0, 17.0 are probably also affected. I have not tested them.

To Reproduce

Using demo data:

  1. Set product PP-3 available quantity = 2.0
  2. Create outbound move for product FP-3
  3. Run MRP Multi Level

Expected behavior

Product FP-3 requires 4.0 units of PP-3. We only have 2.0 units of PP-3 available. We expect a planned order for 2.0 additional units of product PP-3, but the planned order is not generated.

Additional context

The core mrp module computes qty_available=2.0 for product SF-3, which is a kit.
The mrp.multi.level wizard double counts the available quantity of product PP-3.
The 2.0 available units of PP-3 are counted once as part of SF-3, and then counted again to satisfy the direct demand in FP-3.

Screenshot at 2024-10-14 17-44-53

Screenshot at 2024-10-14 17-46-21

@matt454357 matt454357 added the bug label Oct 15, 2024
matt454357 added a commit to asphaltzipper/manufacture that referenced this issue Oct 17, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
matt454357 added a commit to asphaltzipper/manufacture that referenced this issue Oct 17, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
matt454357 added a commit to asphaltzipper/manufacture that referenced this issue Oct 29, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
matt454357 added a commit to asphaltzipper/manufacture that referenced this issue Nov 1, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
matt454357 added a commit to asphaltzipper/manufacture that referenced this issue Nov 5, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
LoisRForgeFlow pushed a commit to ForgeFlow/manufacture that referenced this issue Nov 7, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
LoisRForgeFlow pushed a commit to ForgeFlow/manufacture that referenced this issue Nov 7, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
@LoisRForgeFlow
Copy link
Contributor

Fixed via #1367

JasminSForgeFlow pushed a commit to ForgeFlow/manufacture that referenced this issue Dec 3, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
JasminSForgeFlow pushed a commit to ForgeFlow/manufacture that referenced this issue Dec 4, 2024
fixes OCA#1362

Ignoring qty_available for phantom products prevents double counting the
qty_available of components.

Creating planned orders for phantom products is simpler than recursively
exploding phantom BOMs. This also makes it easier to analyze the planning data
generated by the MRP calculation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants