Sage 100

 View Only
  • 1.  Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 09:43
    Client on 2016 getting error 80 in so_salesjournal_upd.pvc line 6015. They have Avatax, don't know if it's related. Sage does not have this exact line, but I rebuilt all of the files they suggested for a line close to this. Info says GL_SummaryDetailDrillDown, but I've rebuilt it with no luck. Anyone?


  • 2.  RE: Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 09:50
    What about rebuilding the invoice header file?


  • 3.  RE: Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 09:51
      |   view attached
    i'm not all that familiar with Avatax. Have you checked the Avatax site? I've attached an image of what error 80 could be caused by, which very likely could be caused by a 3rd party enhancement using override classes or there is something wrong with the dictionary definition for the file the directive is being used on,


  • 4.  RE: Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 10:01
    How many invoices? Were they imported by any chance? Have you tried recalculating sales taxes? I'm guessing there is an invalid address or tax calc.


  • 5.  RE: Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 10:14
    Have rebuilt the invoice header. NOT positive at all it has anything to do with Avatax, but just wanted to be complete in description.


  • 6.  RE: Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 11:02
    Corrupt or incorrect date in the GL_SummaryDetailDrillDown table? Possibly a bad data in one of the other key fields? KPRIMARY: AccountKey+PostingDate+SourceJournal+RegisterNo+DocumentNo+SequenceNo


  • 7.  RE: Client on 2016 getting error 80 in so_salesjournal

    Posted 02-05-2018 11:08
    @MarcosDeLuna checked out the source code and found it was reading the customer file. Customer looks fine. Restarted the update after the line in error and it finished - having client make sure all is OK with the order and invoice in question. I had added some REQUIRED checks to a couple of fields on the SO Header, but even with taking them off still got the same error, so I don't think it was that.