Just upgraded to 2002.4 with the '03 service pack from DBA.   We have seen three problems so far.
 
First:  When in SO-A, if after entering the customer PO and then cursor down to the next field (s), but decide you need to go back up and edit a field, once you go up past the customer PO field, all the data in the sales order changes to an existing sales order (usually closed, but not always!).  the only thing that does not seem to change is the customer ID.  If you go and delete the order description field, everything comes back to what you entered.
 
As long as we save the sales order first, we can go back and edit it and don't have this problem.
 
2nd problem:  sometimes (not consistent), if you go through the fields when entering a sales order and get to the point where you are to enter the line items, you don't get the line item screen, you get the messages you normally receive after you've entered all the line item, i.e. "use default ending lines", etc.  And it does not save the sales order, no matter how you answer.
(I think I may have seen this as fixed with Lynn's patches?)
 
3rd problem:  Again, entering a sales order, you are at the line item screen and the customer decides not to place the order, so you want to cancel out.  At this point the sales order has been assigned a number.  But if you cancel the sales order, the nuber is gone--the next sales ordered entered does not get that number, but the next number.  So we have gaps in the sales order numbers.
 
Are any/all of these fixed in patches I can purchase with Lynn?
 
Thanks,
 
Val

Not practical. You need to kick all the users out of the system to do that each time...

You can manually assign a skipped number to a new SO.  Just type it in and press enter. You'll get a message that says "SO # xxxxx does not exist. Do you want to use the number entered for a new SO?" Say yes and off you go.    If you jump ahead of  the system counter, it will ask also ask if you want to reset the counter.

Thanks' Cyndee--we'll give the manual number assign a try.  I think if folks are careful, that should help us.
 
Hey Allen, that's great on the SO change tracking.
Do we have to use EVO, or can we use standard?
 
Is there some sort of list that shows the enhancements and which requires EVO?  I'd like to be able to review the list and make a better determination of whether we should move to the EVO version.
 
Thanks,
 
Val

Val, just a reminder-- you don't move to EVO, in the sense of no longer using "regular" DBA. I love it (numerical lookups, multiple windows open, etc, etc.) and use it almost exclusively. Some folks here prefer the familiar, so they still use "regular" DBA. Everybody's happy and the cost is very reasonable. And, no, Lynn didn't pay me to write this. I'm just a satisfied EVO user.  8)

Didn't I say that?