Sage 100

 View Only
  • 1.  2017 premium. Unable to update the sales journal.

    Posted 02-21-2018 07:56
      |   view attached
    2017 premium. Unable to update the sales journal. See the attached screenshot. I looked at the SO_InvoiceHeader table and there is only one 0137988 invoice record.


  • 2.  RE: 2017 premium. Unable to update the sales journal.

    Posted 02-21-2018 08:04
    I think this error message is not really accurate. Notice it says it is coming from ""PopulateWorkTable"". I think those live in temp tables. Do the Sage 100 Premium work tables get created as #tables or does Sage actually create tables in Tempdb, which may have gotten a stuck record?


  • 3.  RE: 2017 premium. Unable to update the sales journal.

    Posted 02-21-2018 08:06
    @PhilMcIntosh I noticed that this invoice 0137988 has the same item number on two different lines in SO_InvoiceDetail. Not sure if that would cause it but it seems like a smoking gun. I will look in tempdb also.


  • 4.  RE: 2017 premium. Unable to update the sales journal.

    Posted 02-21-2018 09:38
    Doug it sounds like the physical table SO_InvoiceDetail is missing the KPRIMARY (clustered) index. For the short term you can remove the extra row in SO_InvoiceDetail (extra b/c it shares the same InvoiceNo + LineKey). Probably somebody was editing the line but b/c the index is missing it INSERTed a new row for that item code instead of UPDATEing it. For the larger problem you'll want to see if the dictionary for SO_InvoiceDetail is either missing KPRIMARY or it's there but missing in the Providex.KDF. In case you have the DD util, going to send you a chat with some steps should you need it:


  • 5.  RE: 2017 premium. Unable to update the sales journal.

    Posted 02-21-2018 09:43
    Thanks Alnoor!