Sage 100

 View Only
  • 1.  Last call for this issue before I throw it to Sage

    Posted 04-01-2014 10:06
    Last call for this issue before I throw it to Sage. New customer to me - Sage 100 ERP 2013 with latest PU. Also using: Avalara Scanforce Starship When there's a Sales Order with a BOM that is a KIT which explodes to the invoice the resulting DTR is doubling the Inventory (CR) portion of the transaction. Can't find a think in the Sage KB other than a lot of ancillary stuff that does not seem to apply (some double posting is only doubling of an invoice in history inquiry, etc). I'm about to pull a case with Sage and let them chew on this one.


  • 2.  RE: Last call for this issue before I throw it to Sage

    Posted 04-01-2014 11:43
    We ran into something similar with a client right after we installed 4.5 for them. In their case the sales amount of the transaction was getting doubled up. The workaround was to have them preview the Daily Sales Journal, answer No to print the other reports (Gross Profit, Sales Recap, etc), print the Daily Sales Journal as normal as well as all other subsequent reports, answer Yes to update and print the Daily Transaction Register. It eventually got fixed with a PU.


  • 3.  RE: Last call for this issue before I throw it to Sage

    Posted 04-01-2014 12:30
    Thanks - naturally when I connected to Sage today I could not duplicate it. So there's some other factor other than just the BOM exploding onto an Invoice. Customer has some third parties and it's possible something in SO or in Shipping could be interfering as well.


  • 4.  RE: Last call for this issue before I throw it to Sage

    Posted 04-01-2014 17:00
    Wow, what a throwback in the wayback machine Sherman!.. I do remember these v4.5 issues, but haven't seen it in v2013. What type of QC does Sage use anyway? Seems that bugs keep cropping up in new releases way too frequently.


  • 5.  RE: Last call for this issue before I throw it to Sage

    Posted 04-01-2014 18:17
    It does sound like the issue on 4.5 that was fixed with an update as @MaryJoKrueger describes. It went away with the update at our one client that ran into it. And the work around was as described. Hopefully it didn't resurface with 2013.


  • 6.  RE: Last call for this issue before I throw it to Sage

    Posted 04-02-2014 06:57
    thanks I'll try to look for the 4.5 fix and see if it matches with what's happening here. Oddly I am able to enter a transaction directly to invoice data entry and it does not double. I suspect the issue could be cropping up in SO entry and/or Shipping