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

are you wanting to use the missing Sales order....or just account for it?
 
My earlier suggestion would only be applicable if you wanted to account for any  "unused" SO numbers.
 

I account for every sales order number.   If one is not there I want to know why.   The # 1 fear is ....Did a a customer place an order and we fail to tell DBA.      
 
I can understand your folks concern.    It is really not much effort to create the skipped SO.
 
Laura
 
 
earlier I had written:
                Maybe I am wrong, but I dont think DBA  ever "remembers" a Sales Order unless you have entered a line item.  Here is my suggestion: You may already have a misc part#.   enter that  number and then in the description the reason you cancelled the SO.    As long as there is no qty or $$ amt the SO will close.  
 
It sounds like you are letting DBA assign SO nuymbers.  Then this may be different for you.  We dont let DBA assign sales order numbers because we have several ordertakers that use different order books and they enter their specific book order#,