Sage 100

 View Only
  • 1.  I have a VI job that runs in 4.3. We are upgradin

    Posted 08-23-2015 18:41
    I have a VI job that runs in 4.3. We are upgrading to Sage 2014 Premium. The VI job imports Sales Order from an Access table. It assigns Sales Order Numbers using the NEXT operation. It uses the 'Change Next On' record selection. The way it works is that the access table actually has nine characters in the Customer Number field. The nine digits are made up of 7 digits for the customer number and two digits as an additional change code. The 'Change Next On' looks at the nine characters that I have in the customer number field and creates a new Sales Order when the last two digits change even though the customer number, the first seven digits, does not change. This way I can split Sales Orders even though the customer number does not change based on item groups. The 'Change Next On' is no longer an available selection in the record tab. Before I start modifying my Access program I thought I would ask if anyone has a way to get the same functionality as the 'Change Next On'. Thanks in advance.


  • 2.  RE: I have a VI job that runs in 4.3. We are upgradin

    Posted 08-23-2015 18:59
    Have you tested this import using just NEXT for the Order Number. I've found you don't need Change On Next. It's automatic if there is ANYTHING different in the Header. Good for your application but not if you want the VI job to ignore it.


  • 3.  RE: I have a VI job that runs in 4.3. We are upgradin

    Posted 08-23-2015 19:13
    It does create a Sales Order Number when the customer changes but in 4.3 it created a new Sales Order when the last 2 digits of the nine character customer number I have in my table. When my customer number changed from 0054000_1 to 005400_2 the job created a new invoice even though both the first SO and the second SO were for customer 0054000. In premium it imports as one Order where as in 4.3 it imported it as two orders which is what I want it to do. The 'Change Next On' allowed me to look at the nine characters in the first field of the access tables even though it only used the first 7 for the customer number.


  • 4.  RE: I have a VI job that runs in 4.3. We are upgradin

    Posted 08-23-2015 19:38
    Thanks Kathryn. Actually your answer solved my problem. I created a Temp field in the Heater and used a substring to look at the last two Characters in my customer field. As you said when anything changes in the header the job automatically creates a new Sales Order so my VI job is now working. I appreciate you taking the time on a Sunday night to help. Thanks, Bob


  • 5.  RE: I have a VI job that runs in 4.3. We are upgradin

    Posted 08-23-2015 19:57
    Glad to help point you in the right direction. That's what makes this group great!