Sage 100

 View Only
  • 1.  I imagine this has been discussed previously. Ho

    Posted 06-15-2017 12:42
    I imagine this has been discussed previously. How does the Inventory Item Inquiry fields ""On SO"" and ""On PO"" get out of balance with the actual On PO and On SO quantities? I know these can be fixed by rebuilding the sort files. Does anyone know how this occurs?


  • 2.  RE: I imagine this has been discussed previously. Ho

    Posted 06-15-2017 12:50
    It is only though the PROGRAMAGIC of Sage..


  • 3.  RE: I imagine this has been discussed previously. Ho

    Posted 06-15-2017 12:54
    LOL... that's what I figured. Customer has ONE item off and wants me to ""find out what caused this"".


  • 4.  RE: I imagine this has been discussed previously. Ho

    Posted 06-15-2017 13:05
    Tell them to be pathetically grateful it's only one. I have someone who MAY have been getting the issue because of WebRoot. Long time ago, overreceiving a PO could cause it.


  • 5.  RE: I imagine this has been discussed previously. Ho

    Posted 06-15-2017 13:08
    I was also told once cancelling an unsaved order without deleting the lines first could cause it. Ahh Sage, keeping clients guessing since.... Always.


  • 6.  RE: I imagine this has been discussed previously. Ho

    Posted 06-15-2017 13:18
    OH, yeah, because it's so intuitive to delete lines instead of just hitting Cancel...


  • 7.  RE: I imagine this has been discussed previously. Ho

    Posted 06-16-2017 12:13
    More than one PO receipt against the same PO being entered at the same time can cause this. (Have a customer who has separation of duties for phama products where this routinely happened until they changed their data entry processes).


  • 8.  RE: I imagine this has been discussed previously. Ho

    Posted 06-19-2017 05:34
    Thanks everyone! I used to have a list of reasons for error 47 and error 105 (corrupted data) that I would recite to end users when they asked. The real answer is ""who knows"".


  • 9.  RE: I imagine this has been discussed previously. Ho

    Posted 06-19-2017 05:44
    There is actually a fix listed in the 2017.2 service update that fixes one particular PO issue...