search

inventree / InvenTree

Open Source Inventory Management System
https://docs.inventree.org
MIT License
4.08k stars 727 forks source link

[FR] Summarise stock requirement for a BOM and it's children #6665

Closed LavissaWoW closed 1 week ago

LavissaWoW commented 6 months ago

Please verify that this feature request has NOT been suggested before.

Problem statement

Having complex, deep multi-level BOMs creates somewhat of an issue with production planning. If several of a given BOM's child BOMs use the same part, the toplevel BOM can't paint a picture of how many of itself you can build. As when you start creating Build Orders, and allocate stock, the stock that the top-level BOM thought it could use is eaten by its children.

This also applies to looking at any given BOM with child BOMs. The "Can build" field is based on the completed stock of the child, not how many of the child you can build. So, if BOM A has a line that is BOM B, and you have 0 of BOM B in stock, then BOM A claims you can build zero of BOM A. However, perhaps you actually have the stock to build 10 of BOM B. So you could actually make more than 0 of BOM A.

This is very difficult to discern as the structure works today.

Suggested solution

Listing some ideas:

  1. Implement some sort of lookahead to a BOM, to determine if there's stock to build a given child.
  2. Add calculations that can be rendered in a report
  3. Implement a mechanism to calculate how many of a given part can be built given current stock status, and what builds will be needed to meet this quota. List what parts have insufficient stock for this goal to be met

Describe alternatives you've considered

Manual math

Examples of other systems

No response

Do you want to develop this?

SchrodingersGat commented 5 months ago

This would be very difficult data to present "live", but a report would be a good option, as it can be generated offline and then presented to the user.

github-actions[bot] commented 3 months ago

This issue seems stale. Please react to show this is still important.

LavissaWoW commented 3 months ago

Not stale

github-actions[bot] commented 1 month ago

This issue seems stale. Please react to show this is still important.

LavissaWoW commented 1 month ago

Not stale

SchrodingersGat commented 1 week ago

This sort of "on demand" data would be perfect for a custom report or plugin. I do not think there is much I would want to add to the API / default user interface here.