Sage 100

Upgrading from 3.71 to 2014 going live Monday. Just discovered an issue with a crucial VI job that gets run daily. Importing sales orders. In 3.71 division is assign 00. customer# is replace using field 2, default UNASSIG. In 3.71 if the customer was invalid UNASSIG would be used and the order would import. In 2014 set up exactly the same but if the customer# is invalid then the record fails... UNASSIG doesn't get set as the customer number. Any ideas on workarounds... We need all of the orders to import ... even ith the invalid customers. Thanks!

Are you assigning fields from the customer masterfile that would fail if no customer exists? Can you create a customer UNASSIG?

What makes a customer number invalid? You might need to use perform logic to pretest the number and then change it to unassig if it is invalid.

@ThereseLogeais We have a customer # UNASSIG. For customer # in the VI job it is Replace field 2 and default UNASSIG. The hope is that if the customer number in the input file is invalid the VI job would use the default customer number instead.

@JimWoodhead It could be anything but generally just a bad customer number such as a misspelling. Do you happen to have a pre write script to test for invalid customer numbers and assign a good one if it is invalid? I am willing to pay for it at this point.

I will check but I think it is a matter of looking up the ar_customer table. If valid pass it..... If not there set to unassig.

can you print your VI job to pdf and attach it ?

Will print VI job in two to three hours. Thank you

@JeffFiddelman pdf attached. Any suggestions are welcome. Thanks.

Doug, not sure if this is the problem but your temp001 starts in position 4 and goes thru 7. Seems like it should start at 1

Doug, Here is some perform logic to use. It checks the Customer Number to see if it is valid. If it is it goes thru if it isn't it set the CustomerNo to ""UNASSIG"" You will need to copy this program to the SOA folder and add a line in the perform logic of the VI Perform type:Before Assign File Type:Header Table Name: SO_SalesOrderHeader Column Name: CustomerNo Seq: 001 Command: ..\SOA\DSDVIP.MCS;LOOKUP_CUSTOMER

@DougHiggs this will definitely need to be tested but it looks correct.

Thanks a million @JimWoodhead . I will test it tomorrow when the conversion completes.

Hi Jim and Doug - using a similar perform to what Jim provided is exactly the direction I would have taken .. gives you full control of the situation. Also much of the VI job is not needed going from 3.71 (when you had to assign all fields) to 2014 where the object behavior will take care of a lot of it... it generally doesn't hurt to keep it in, but you should only need the lines that override the normal behavior of the object or populate fields that are not handled by the object. Good luck

Hi - just a follow-up to see if all is well..... Jeff

Going pretty well. First day live and I am on site. I used Jim's pre processing vi script and am grateful to have it. I had some issues with it as the customer has multiple divisions and the code was checking for a valid customer using the concatenated 00 division only and the customer number. I was able to modify the script Jim gave me and create another similar script to process the division number also. Looks like it is working. Thanks for checking. You guys are a huge help.