Post Reply 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
prolem with WO and leadtime of purchased components
04-29-2012, 08:14 AM (This post was last modified: 04-29-2012 09:10 AM by opto.)
Post: #3
RE: prolem with WO and leadtime of purchased components
Hi Exson,

thanks for your help.

Unfortunately, that does not solve it, the due date is still the required date of the WO.

One WO was created manually, ther other is a child (converted) from the first.


I think there is an error in the logic in mrp.php.

From the WO, the required date for purchased items is currently the required date of WO if autoissue - that is ok.

these dates are entered into mrprequirements table.

after all tables are created, the lode loops through all levels to compare requirement and supply (from top level to lowest level).

At each level, levelnetting is called for all parts of that level. Levelnetting enters the demand into the mrpplannedPO tabel WITHOUT taking leadtime into account.
In this function, createlowerlevel requirements is called, and takes leadtime into account for those components.

So it seems that depending on where a component is in the bom, it's lead time may or may not be considered.

Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: prolem with WO and leadtime of purchased components - opto - 04-29-2012 08:14 AM

Forum Jump:

User(s) browsing this thread: 1 Guest(s)