(posted also in Sales, just in case)
 

OK, for some reason now when our sales folks start to enter a sales order, and cancel out *after* the SO number is assigned, the process is skipping the cancelled # and going to the next one.  I just experimented doing this three times in a row in my test company, and every time I noted the SO number assigned [ex. 25358], then cancelled out after getting into the line items screen, confirmed cancel, then went to enter a new order.  The cancelled # is not in the SO listing.  When the order entry gets to the point where a SO is to be assigned, it gave 25359, not 25358.  I cancelled out again, and started the process over a 3rd time, and it assigned 25360.  
 
We have missing 8 SO numbers in our SO listing since 7/21, the last time we applied a fix (the SA-A fix).
 
Help!
 
Val

yep, we have always allowed DBA to assign the SO#, but it usually hasn't been a problem with skipped numbers until the recent update (we updated from 2000.1 to latest rev). So I guess we'll have to set some
sort of standard here to keep track of the missing #s like you suggest.  My biggest problem will be getting people to pay attention to when they do it.
 
Thanks,
 
Val