ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Sales >> HELP! &amp;nbsp;SO-A Numbers broke again
http://www.istechforum.com/YaBB.pl?num=1090881224

Message started by gtladmin on 07/26/04 at 14:33:44

Title: HELP! &amp;nbsp;SO-A Numbers broke again
Post by gtladmin on 07/26/04 at 14:33:44

:(
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

Title: Re: HELP! &amp;nbsp;SO-A Numbers broke aga
Post by Lynn Pantic on 07/26/04 at 15:37:08

Unfortunately, that's the way it is, it has been that way since version 2001.1 or thereabouts, I forget when it changed. The SO-A program got too big to compile so it was split into 2 separate programs, one for the header information and one for the lines. What that meant was, when you move from the header to the line items, the header needs to be seved which means it needs to pull a number which is then passed to the line item program. So if you cancel adding an order after you have moved into the line item screen, the number is already pulled. You can manually use that unused number in the next order but you need to remember to do it.

Title: Re: HELP! &amp;amp;nbsp;SO-A Numbers broke
Post by Laura on 07/26/04 at 15:41:56

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.

Title: Re: HELP! &amp;nbsp;SO-A Numbers broke aga
Post by gtladmin on 07/27/04 at 06:27:23

Laura & Lynn, I guess they probably want to keep track so we don't have gaps. I had told them back in June to manually assign the next SO# if it's missing. It's not a big deal to me, but it is to them to have to remember to do stuff like that. I just sent everyone an email repeating what I had told them back in June, so they'll just have to adapt and move on.

Val

Title: Re: HELP! &amp;amp;amp;amp;amp;amp;amp;amp
Post by Laura on 07/27/04 at 10:52:14

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#,