Hi Mike,

My understanding is even the receipt did by warehouse guys and the transaction is post only after day-end. in fact when the day-end the liability is in the clearing account and will transfer to the vendor AP after invoice is keyed and posted. I may misunderstand your question, why do you ask to stop that happens?

thanks

@Sage300.  no, you have completely missed the point.  I'm only talking about the PO receipt cost automatically changing the ICITMV table.  that's it.  Nothing to do with A/P or inventory costing.  It's just the vendor cost table that I want to stop touching.

@Sage300.  no, you have completely missed the point.  I'm only talking about the PO receipt cost automatically changing the ICITMV table.  that's it.  Nothing to do with A/P or inventory costing.  It's just the vendor cost table that I want to stop touching.

Sorry, just a follow up to using the "Vendor Contract Pricing".   The big downside with that is that you can't have a vendor used more than once for a given item.  We use this a lot as well for some vendors that we order hose from.  They can have multiple SKU's for the same hose to separate specific lengths.

The Vendor contract pricing could be SUPER usable if it allowed something like that.  That would also allow us to insert future price increases.   Maybe the price today is $2, and we know that in May 2015, it will jump to $2.50, we could just insert that now, if the table allow multiple instances of the same vendor code.

Anyways... beating a dead horse here.  Thanks for your input guys.  

We are just going to change how we are doing it now.   Currently we have a day-end script to export the table using the Export function, then run day end, then import it back in.   With our upgrade in a few weeks, that might break the script(?), so we are going to redesign it to do the dump as an SQL and avoid using the Export/Import function.  should save about 20 minutes in the whole process.