PO Due Date Management

For the Due Date I think the best way is to use the Promise Date to store the Date that the supplier says they can deliver and do not move the Due Date. But we struggle with this because our buyers like to move the Due Date instead. One of the problems with moving the Due Date is then the supplier performance reporting is not accurate because we use the Due Date to calculate Days Early/Late on our reporting. If the Buyer and Supplier both agree it’s ok to move the Due Date then that’s fine. But the Due Date often gets moved when we get an update from the supplier that it’s going to be late and the Buyer wants to reflect that, when this happens the reporting will not be correct since the Due Date is no longer the date we wanted it... in this situation they should be using the Promise Date.
 

The Promise Date does display in other areas like Time Phase

For supplier performance reporting we have created our own reports that show Days Early/Late for each release and a summary of to show the total number of Early, Late, and On Time receipts. This reporting uses the Early/Late buffer in the supplier master.

For acknowledgements there are additional modules or 3rd party addons that leverage a supplier portals to keep track of supplier communication like acknowledgements. There are two different types of models/addons for MRO and Raw Material.

Very recently we just had this discussion on which way to use this and what you are saying Bruce is probably why the buyers have been reluctant to use the Promise Date. The trouble is Buyers don’t remember to populate the Promise Date with the original due date either so the Promise Date doesn’t work at all right now for reporting for us. I’m thinking maybe we need to use a BPM to populate the Promise Date when they first enter a Due Date.