Sage 100

 View Only
  • 1.  I have a client who is running v2013 advanced with

    Posted 02-14-2014 05:40
    I have a client who is running v2013 advanced with several ACS modifications as well as ScanForce. On occasional and at random, the lines total during SO data entry does not coincide with the totals tab total. We have determined that the lines total is correct. On one instance, the lines were zeroed out and the totals tab maintained a value of $300. Again, the occurrence of this issue is not consistent with regards to a customer, items or any other pricing considerations. Because the issue is not consistent, I am lead to believe this is not related to custom enhancements, but who knows. Any ideas or help would be greatly appreciated.


  • 2.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 05:52
    @KevinRuppert I doubt it's related to the modifications also. We've run into this off and on and in various version for years. We usually go ahead and get the detail the way we want it and then DFDM the totals. Or delete the order and recreate it. There are other consideration, interfaced with Sage CRM for example. You may have to DFDM the supporting tax files as well. Someone else might have some insight as to what can cause this. It's always seemed very random to us.


  • 3.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 05:54
      |   view attached
    Looking briefly through Sage's KB - I see a bunch of random reports through various levels. If I were to guess it's probably an issue brought on by some type of editing of the lines in a way that's throwing Sage 100 for a loop. Here's one report that's fairly representative and it pretty much reinforces Brett's advice.


  • 4.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 05:56
    @BrettLyder thanks for the reply. I know when we use the copy function to make a copy of the affected order, the totals are correct. There are a lot of changes being made to the lines by the user(s) so it is likely sending us for the look as mentioned by @WayneSchulz


  • 5.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 05:56
      |   view attached
    another (lots of these claim to be fixed by patches but it's not unusual for Sage to re-break something during a later upgrade release)


  • 6.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 06:00
    Have you rebuilt the SO_SalesOrderDetail table?


  • 7.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 06:22
    Is the client moving off the line before clicking on the totals tab. Perhaps they are (aren't) clicking on the accept button from tab three to tab four. I think everyone has encountered these issues at one time or another, with or without enhancements. May @AlnoorCassim can shed some light today. And yes, for some strange reason, it takes several iterations of fixing by Sage before it stops reappearing.


  • 8.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 06:52
    Are you using AvaTax? I noticed an issue with one site where AvaTax was installed and the fix was to change the tax schedule from AvaTax to NonTax then back and it recalculated it correctly. The totals for some reason were doubling up. This was on a 4.5 version.


  • 9.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 08:58
    This is a classic symptom of damaged or broken embedded io. run the script: In mas, File \ Run, SYZCON at the prompt type: o=new(""sy_activation_bus"",%sys_ss) Hit enter to go to the next line and type: print o'activate(""c/i"",""abc"") Hit the enter key and wait for the 1 to be returned. Of course change the ABC to the proper company code and run this not only for C/I but S/O as well (doesn't hurt to repair the rest of the modules just in case. Just change the module code)


  • 10.  RE: I have a client who is running v2013 advanced with

    Posted 02-14-2014 09:23
    Along the lines of what @ToddMartin said I've caused that issue myself with a Line Post-Write script in S/O Entry. I didn't think I was coding anything wrong but when I moved it to Line Pre-Write it worked okay. Problem always happened when order lines were changed after Totals were clicked to calc sales tax etc.