Sage 100

 View Only
Expand all | Collapse all

Anyone have a client with the issue of the Sales O

  • 1.  Anyone have a client with the issue of the Sales O

    Posted 07-29-2013 16:26
    Anyone have a client with the issue of the Sales Order History file not jibing with the Sales Order file?


  • 2.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-29-2013 16:29
    YES I have seen that for sure. Sometime the amounts are different not to mention the cost and price/ also you can get additional lines in history. What kind of issues are you seeing?


  • 3.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-29-2013 16:35
    Much the same, plus missing lines. So WTF, why don't I see a write-up on the KB? It can't be just you and I. (I've actually seen it at two clients now, different versions.)


  • 4.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-29-2013 19:19
    Are the additional lines deleted lines? I believe there is a flag to keep deleted lines in history. Have any of the mismatched orders been edited by chance?


  • 5.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 05:18
    I'm sure the orders have been edited, but it's the MISSING lines that are a real mystery - they are on the order but not in history.


  • 6.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 05:32
    Wasn't this discussed here maybe a week or two ago - I think it was regarding saving deleted lines in history? Maybe not an exact match to the issue Beth is experiencing but I recall a discussion with someone pointing out the option in SO - Setup to save/not save deleted or back order lines (can't recall the exact issue at the moment).


  • 7.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 05:34
    No, this is different. This isn't that a deleted line still shows up - this is that a current line does NOT show up. Or shows up differently.


  • 8.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 07:24
    This is what I was thinking of - https://90minds-com.socialcast.com/messages/16824100


  • 9.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 15:33
    Yes @BethBowers I have seen that on version 4.3 and 4.5 (same customer). We had the ""track deleted SO"" UNchecked and were relying on the salesreps to answer ""Yes"" to save to history and select a cancel reason code. Once we checked ON the track deleted SO the issue stopped. It wasn't just whole orders missing with the option unchecked but a line here or there too with no rhyme or reason for it.


  • 10.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 15:54
    Seriously, folks, it's not the deleted line thing. It's a line that currently exists on the SO in SO Entry and does not in SO History.


  • 11.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-30-2013 22:14
    what are the line types? Inventory, misc etc. We know about a misc charge and misc items getting messed up.


  • 12.  RE: Anyone have a client with the issue of the Sales O

    Posted 07-31-2013 03:59
    I think they were inventory, but can check. What happened with your misc stuff?


  • 13.  RE: Anyone have a client with the issue of the Sales O

    Posted 08-30-2013 14:14
    I have a client running 2013 SQL and we're finding hundreds of orders not recording all SO Entry Lines to SO History. Worse yet the SO History Line SO Line Index does not match the actual SO Line Index. So when an invoice update writes back to SO History the quantity shipped is wrong (because the active data is written to the wrong line in history). The real kicker is the write back sometimes goes to a Comment Line (due to mismatch sequence numbers)! When this happens the sales journal update throws an error 40 (missing UoM CF on a Comment Line) and halts the update. The resolution is to manually enter it for the Comment Line and restart the update. When this is done the update restarts, doubling the value of the original Invoice History Header Sequence 000000 (and Open Invoice), and it creates a duplicate Invoice History Header Sequence 000001. Loads of fun... :)