Community mailing list archives

Re: procurement scheduler and nested BOMs

Libertus Solutions, Alan Bell
- 07/17/2015 04:51:57
interesting, thanks

The proposed methods are to start at the bottom of BOMs and work up, or to priorities the order points so that presumably you do the high level items first so when you get to the little ones you have already created the requirement.
I am unconvinced either of these will work perfectly in all complicated BOM situations, repeating the process until there is nothing left to do will always work exactly as it does now.


On 17/07/15 09:43, Graeme Gellatly wrote:
<blockquote cite="" type="cite">

Search the bug reports,  this exact scenario is covered in there with a patch which from memory was rejected as it was too complex. 

On Fri, 17 Jul 2015 8:34 PM Kurt Haselwimmer <> wrote:

+1 this is a key requirement for a professional MRP system. 


The scheduler that computes order points and creates the manufacturing 
orders works OK, but for nested BOMs it needs to be run multiple times. 
Is there a way of triggering a re-run if there were things found during 
processing that created new requirements?

for example, if we want to build a house, which is made up of a roof and 
4 walls, the roof being made of tile and the walls of bricks the BOM 
structure might be like this:

house (1)
     roof (1)
         tiles (100)
     wall (4)
         bricks (1000

when we procure a house, it will create manufacturing orders for 1 roof 
and 4 walls, but these can't be produced because they will be waiting 
raw materials. Running the scheduler a second time will procure the 
tiles and bricks that are needed. If we have BOMs that are many levels 
deep we need to run the scheduler quite a lot, and it isn't clear how 
many times to run it, or when we are done with running it, or what 
exactly it is doing.

Is there any better process for achieving this?



Post to:

Post to: