Hi Neil,
We're on 6.10 but it sounds like the logic is the same. It just depends on what your company considers late. Vantage uses the due date to populate expected receipt dates and should be as accurate as possible. The Buyer Workbench looks at the Promise date when considering "lateness". The promise date is when the Vendor promises to have it to you. If that changes, then the Buyer would change the due date, but your company still wants it at the original promise date, it should be left alone. The part is still not arriving at the required delivery date and should be considered late. If the change in delivery date is acceptable to your company, then you can change the promise date as well. Also if the change in delivery date is initiated by your company and not the vendor and the vendor accepts the new delivery date, then the promise date should be updated as well.
Basically this allows buyers to track on time performance without sacrificing the validity of the due date.
-Elizabeth
To: vantage@yahoogroups.com
From: njones@...
Date: Thu, 3 Dec 2009 20:04:29 +0000
Subject: [Vantage] Purchase Order Dates, Promise Date / Due Date which date should count?
Current Version 8.03.407C
Vantage appears to use the PO due date in almost all case as the cast in stone receipt date. My problem is that the purchasing workbench shows orders late, by amending the late PO due date to a date in the future it still does not disappear from the late order screen. Only when the promise date is amended will it remove itself from the late orders.
My opinion would be is that that the promise date is the date first advised by the supplier, currently if an order goes overdue then the purchaser really needs to amned both dates at the same time.
Any comments?
Regards,
Neil
_________________________________________________________________
Chat with Messenger straight from your Hotmail inbox.
http://www.microsoft.com/windows/windowslive/hotmail_bl1/hotmail_bl1.aspx?ocid=PID23879::T:WLMTAGL:ON:WL:en-ww:WM_IMHM_4:092009
[Non-text portions of this message have been removed]
We're on 6.10 but it sounds like the logic is the same. It just depends on what your company considers late. Vantage uses the due date to populate expected receipt dates and should be as accurate as possible. The Buyer Workbench looks at the Promise date when considering "lateness". The promise date is when the Vendor promises to have it to you. If that changes, then the Buyer would change the due date, but your company still wants it at the original promise date, it should be left alone. The part is still not arriving at the required delivery date and should be considered late. If the change in delivery date is acceptable to your company, then you can change the promise date as well. Also if the change in delivery date is initiated by your company and not the vendor and the vendor accepts the new delivery date, then the promise date should be updated as well.
Basically this allows buyers to track on time performance without sacrificing the validity of the due date.
-Elizabeth
To: vantage@yahoogroups.com
From: njones@...
Date: Thu, 3 Dec 2009 20:04:29 +0000
Subject: [Vantage] Purchase Order Dates, Promise Date / Due Date which date should count?
Current Version 8.03.407C
Vantage appears to use the PO due date in almost all case as the cast in stone receipt date. My problem is that the purchasing workbench shows orders late, by amending the late PO due date to a date in the future it still does not disappear from the late order screen. Only when the promise date is amended will it remove itself from the late orders.
My opinion would be is that that the promise date is the date first advised by the supplier, currently if an order goes overdue then the purchaser really needs to amned both dates at the same time.
Any comments?
Regards,
Neil
_________________________________________________________________
Chat with Messenger straight from your Hotmail inbox.
http://www.microsoft.com/windows/windowslive/hotmail_bl1/hotmail_bl1.aspx?ocid=PID23879::T:WLMTAGL:ON:WL:en-ww:WM_IMHM_4:092009
[Non-text portions of this message have been removed]