Answer
Reconsider the Picking Lead Time setting itself rather than trying to suppress the message it produces. Setting a site's Picking Lead Time to a fixed number of days like 10 doesn't just add processing buffer — it functionally forces every single order's calculated due date to be pushed back by that same fixed number of days regardless of the order's real characteristics, which is exactly why a genuinely short-lead order then appears to already be 'late,' triggering the informational due-date warning on every line. That informational message is correctly reflecting the real consequence of the site-level setting rather than being a bug — suppressing it via modification would just hide a valid warning about a scheduling conflict you've actually created. The better fix is re-evaluating whether Picking Lead Time really needs to be a fixed nonzero value for every single order at that site; it should generally only be set above zero if it will genuinely be true for every order placed at that site.