It's no different than someone trying to enter a sales order for $0 - some companies want to prevent what is usually a user error. OrderEntry can pop a warning; PurchaseOrders can't. I'd like it to be able to.

The rest of what I'm going to write is tangential to my request but some of you may be interested in the background. The requesting client is a distributor who sells expensive parts (each is a separate item in Adagio). Customers often ship the items back for repair. They would like to use Adagio to monitor the repair cycle instead of Excel (which they are doing now). The steps once they receive the parts are:

1) They ship the part to the item's vendor together with a packing list (including instructions), asking for a cost quote to perform the repair.
2) The vendor sends a quote for doing the repair.
3) Based on the vendor's quote, they send a quote to the customer for authorization
4) The customer authorizes the work, at which point a sales order is created, and from it a PO to the vendor. (This is the point at which they want to prevent a $0 cost)
5) The vendor ships them the repaired part, together with an invoice
6) They ship the repaired part to the customer, together with an invoice

I am creating a GridView that will display each repair, including where it stands in the cycle and other necessary information. Part of that information is the PO amount.

It's quite a bit more complicated than this - for example the customer may decline the repair. Or the part may be under warranty. And generating the packing list in Step 1 without requiring double-entry is interesting - I am having them enter it as a Template Quote in SalesCQ (using the prospect table to store the vendor information). This flows from a customer quote to a sales order to a PO seamlessly. If anyone is interested in my documentation detailing how this works, please email me.

Steve
steve@sschwartzcpa.com