Community mailing list archives

community@mail.odoo.com

RE: procurement scheduler and nested BOMs

by
Rooms For (Hong Kong) Limited, Yoshi Tashiro
- 07/17/2015 08:48:11

I'm not sure if repeating the scheduler run would always generate the desired result (haven't checked in detail), but in case you need to sort the procurements by priority of the product determined baesd on BOM records (higher level products first), you might check out these lines we wrote for a different purpose (based on 7.0):

https://github.com/rfhk/cip-customization/blob/master/product_procurement_extended/wizard/product_procurement.py#L78-L107

 

----------------------------
Yoshi Tashiro

 

From: Kurt Haselwimmer [mailto:kurt@hertford-developments.co.uk]
Sent: Friday, July 17, 2015 5:23 PM
To: Community
Subject: Re: procurement scheduler and nested BOMs

 

Well then the answer seems quite straightforward - keep a check on the number of requirements created by each pass and then offer an option to repeat the process until this value is zero.

 

Kurt



interesting, thanks
https://github.com/odoo/odoo/issues/3626

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.

Alan.

On 17/07/15 09:43, Graeme Gellatly wrote:

<blockquote cite="mid:CAFmBtG0tWkkYayRs27+_H0WP0==KEVFen=aqg77WGZn=Ecskcg@mail.gmail.com" 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 <kurt@hertford-developments.co.uk> wrote:

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

 

Kurt

 

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?

 

Alan.

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe