I think the key is the use of criteria "shippable". So there has to be a routine/script to check the quantity when an order is being entered or saved. My honest opinion is that the notification approach might be the best. I did something similar, which involved SQL Server since I'm don't know Providex or server side scripting much. This might help you, though it's really not an automation. My notification routine runs every time a new order is entered, and send email to the user who entered the order with all the back orders for the given customer. The info includes includes everything like qty on hand, qty on PO, and earliest expected inbound shipment date, and etc. This script is tied to CustomerNo column post-validate the S/O Header. So it runs every time you type in a new CustomerNo . This can be done entirely in vbscript through ODBC and doesn't requie SQL Server by the way. Vbscript can also email using the same SMTP used by SQL server. It's your choice on how to get the same result. I used MSSQL only because I simply hate having a complicated SQL statement in vbs file. Plus it's easier for me to manipulate the numbers to show exactly what I wanted to show to the users in SQL, which is the most important part. Say you have 10pcs on hand and 5 orders all entered today, totaling 10pcs. Let's say the 1st order is for 6pcs and is scheduled to be shipped in a few weeks and you are expecting a shipment next week. When a new order is entered, MAS will scream at you because you don't have enough quantity on hand. But you actually have 6pcs left! The only way to check whether something is "shippable" or not is to check all of related information. Crystal can't do this well but SQL can. I do like what Strew suggested by the way. With her suggestions, the newest order can even have how many orders there are total.
↧