Sage 100

 View Only
  • 1.  Customer on Sage 100 ERP 2013 - PU 3 - went in and

    Posted 04-01-2015 10:42
    Customer on Sage 100 ERP 2013 - PU 3 - went in and did a customer merge. They hosed their AR Invoice History - or rather it appears Sage 100 ERP hosed it. I think we've talked about this and Sage pushed a fix out pretty quickly (says PU 5 for Sage 100 ERP 2013 fixes). However that doesn't help me with their 200+ MB history file that is now incorrect. I'm thinking figure out the changes between old and new AR_InvoiceHistoryHeader and vi the proper customer into their live data table. Any other way to fix this? Here's the Sage KB: Delete and Change Customers changes the customer number for most invoices within AR Invoice History Inquiry instead of just the customer selected during the utility Description Delete and Change Customers changes the customer number for most invoices within AR Invoice History Inquiry instead of just the customer selected during the utility Resolved with the following updates: Product Update 3 for Sage 100 ERP 2014 (5.10.3.0) Product Update 5 for Sage 100 ERP 2013 (5.00.5.0) I just logged in to see that we are using Product Update 3 (5.00.3.0) and Sage claims this is resolved in their product update 5.


  • 2.  RE: Customer on Sage 100 ERP 2013 - PU 3 - went in and

    Posted 04-01-2015 11:17
    That's how I fixed it - get a list of old customers and export out all invoices that had them, then import in with new. You only need the invoice number and header seq.


  • 3.  RE: Customer on Sage 100 ERP 2013 - PU 3 - went in and

    Posted 04-01-2015 11:23
    Thanks I was hoping it would be that ""easy


  • 4.  RE: Customer on Sage 100 ERP 2013 - PU 3 - went in and

    Posted 04-01-2015 13:36
    Just finished this - seemed to work ok. The only issue we had was the XD (deleted) invoices did not change the customer number. Since we didn't care about the deleted we decided not to worry about it. An excellent case study for why installing all the product updates is advisable. As well as why you should always make a complete backup just before you do any delete/change.


  • 5.  RE: Customer on Sage 100 ERP 2013 - PU 3 - went in and

    Posted 04-01-2015 17:06
    Reminds me of a client that merged all of their customers on 9/11. Their problem wasn't too bad by comparison.