Sage 100

 View Only
  • 1.  We ran a significant GL renumber for a client. Re

    Posted 12-11-2018 13:09
    We ran a significant GL renumber for a client. Reviewed the system and all looked fine. We then performed on the live company. Client has come to us a week or so later to point out all of the invoice history seems to be a hit or miss on the accuracy of the assignment of GL account. Some accounts were 4 different accounts before the renumber. Anyone seen this? Anyone know the cause? I have a feeling we have a lot of cleanup to do.


  • 2.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-11-2018 13:25
    The client is running 2014


  • 3.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-11-2018 14:05
    Is the issue with invoices that existed in history prior to the renumber, or invoices that were added to history since the renumber? If they are using SO Invoice Data Entry, it could be using the old GLs if they were not updated in the SO Sales Order Detail records prior to invoicing.


  • 4.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-11-2018 14:12
    This is AP Invoices in History that were there prior to the renumber. We went back and checked our test. It behaved similarly but assigned to different wrong accounts during the first renumber test!


  • 5.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-12-2018 04:51
    Hi - if you have a copy of the data before the renumber, a number of options come to mind, some seem like a ton of work... If you want to discuss a one-off MD solution to this, please email me directly - perhaps we can help. Jeff


  • 6.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-12-2018 06:33
    So, we compared the preconversion and it appears to have impacted most of the subsidiary modules. We can not determine a logic. We have 5 different accounts that were assigned to an account that was a new account and not involved in the renumbering at all.


  • 7.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-12-2018 12:22
    Solved the problem. Apparently during the renumber the GL was restored mid way through the steps and none of the other modules.(not the middle of a renumber but between groups of renumbers)


  • 8.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-12-2018 14:05
    ouch


  • 9.  RE: We ran a significant GL renumber for a client. Re

    Posted 12-12-2018 14:30
    Well it is good news. In the maintenance world, they have lock out controls to keep people from running machines when someone else is inside it. Sounds like a similar situation. At least you don't have to eat your rework time....