MRP and PO Promise Date in 8.03.405a

(1) It would be safe, prior to MRP running, to export all your due date/prom date data, import (SQL update fine as most run MRP 'off hours' where the impact on the db wouldn't bring things to a crawl) the prom dates into due date fields, run MRP, then restore the 'real' due dates via a post MRP SQL update.

Or - (2) consider switching the names of the native fields on all forms so Prom Date (stored in native due date field) is always your MRP driver.

Each has a negatives:

(1)Â will result in time phase messaging that doesn't coincide with MRP PO change suggestions (as you can't add prom date to time phase to make it more understandable and the on the fly time phase messages will be based on due date).

(2) will also impact time phase as a planner won't see the real known current adjusted due date without launching another screen.

Rob Brown


Â



________________________________
From: Jeff Bieringer <jeff_bieringer@...>
To: vantage@yahoogroups.com
Sent: Friday, June 12, 2009 6:01:45 AM
Subject: [Vantage] MRP and PO Promise Date in 8.03.405a





When MRP is run, it uses the Purchase Order Due Date for constraining material even though another date is entered for the Promise Date which is later than the Due Date. How do we get MRP to look at the Promise Date? The only way I see around it is to change the Due Date to the Promise Date but this does not help in showing when the product was requested by and if the vendor is late.







[Non-text portions of this message have been removed]
When MRP is run, it uses the Purchase Order Due Date for constraining material even though another date is entered for the Promise Date which is later than the Due Date. How do we get MRP to look at the Promise Date? The only way I see around it is to change the Due Date to the Promise Date but this does not help in showing when the product was requested by and if the vendor is late.