Can anyone explaing the heirarchy of purchasing lead times for PO Suggestions? I’ve found three different fields where the lead time is entered:
PartPlant.LeadTime
VendPart.LeadTime
PartXRefVend.LeadTime
I can’t figure out which field is driving the PO Suggestions, can anyone help explain the logic?
Thanks!
The primary driver of lead time for purchasing suggestions is the lead time of the part on the item master (Part). That can be overridden by a value in Supplier Price List, that is the only place I am aware of that will replace the lead time of a part that is set up through item master.
The same goes for subcontract operation lead times. Whatever is in the part master will be overwritten by supplier price list when MRP creates the unfirm jobs.
When you think about it, this makes sense, as it gives the ability to change an item lead time without having to involve engineering.
Thanks, Gil.
That makes sense for the behavior I was seeing. I had the Part Master set to a 40 day lead time, while PO Suggestions was showing a 0 day lead time. The Supplier Price List had a 0 day lead time, so it must have overwritten the Part Master.
Which field on the Supplier Price List takes precedence? VendPart.LeadTime (Parts>Detail>Lead) or PartXRefVend.LeadTime (Parts>Supplier Parts>Supplier Lead Time)?
Thanks again!
Thank you! 
Is there a way to implement a dynamic lead time? So that the lead time for a part will update automatically to whatever the most recent previous lead time was (from PO to receipt)? Or the have the system dynamically aggregate an average lead time of some sort? I feel something like this would provide some decently accurate lead times (not all the time, but most of the time). Right now obviously it is difficult to nail down lead times with suppliers because it changes often… but a feature like this could help out significantly.
There is nothing out-of-the-box that does this, but it is probably a fairly straightforward customization. That said, I’d be REALLY CAREFUL rolling it out. I don’t know your business, but there are a few million exceptions that would be difficult to account for (multiple releases on a PO, internal expedites/postpones, backorders, etc).
