Reporting on Purchase order revisions

We are trying to track vendor performance and past due deliveries on purchase 
orders.  Ideally, we would like to do this by comparing original promise date 
to actual delivery date.  The problem we have is that when our purchase 
agents call vendors to get updates on delivery times, they change the promise 
date field on the PO.  

I need to know what the original promise date was when the purchase order 
was set to open status (once it printed).  Is this stored in the database 
somewhere?  Would it show up in PO revisions.  It would be nice to see how 
many times we are changing promise dates for some of our problem vendors.  

We could use a custom field for original promise date, but I would prefer to 
write a report versus a customization.

We actually had a similar requirement, but we were trying to forcast cash 
flow based off of the promised date as well as maintain the original promise 
date for vendor performance analysis...

I just didn't think about using the revision history, so I added user7 from 
purorddet to the PO screen....

Anywho, you might take a look at POReqHdr and POReqDet tables, you might be 
able to write a report using fields from those tables....

wish I had thought about that before I added the user field :)

"Katie Warner" wrote:

> We are trying to track vendor performance and past due deliveries on
purchase 
> orders.  Ideally, we would like to do this by comparing original promise
date 
> to actual delivery date.  The problem we have is that when our purchase 
> agents call vendors to get updates on delivery times, they change the
promise 
> date field on the PO.  
> 
> I need to know what the original promise date was when the purchase order 
> was set to open status (once it printed).  Is this stored in the database 
> somewhere?  Would it show up in PO revisions.  It would be nice to see how

> many times we are changing promise dates for some of our problem vendors. 

> 
> We could use a custom field for original promise date, but I would prefer
to 
> write a report versus a customization.