Sage 100

I have a VI job that imports Sales Orders. I need to have the job insert a line item into each order for shipping and handling at a fixed amount. The S&H row does not exist in the source file. I can accomplish this be pre-processing the file before the import but before I do that I would like to find out if this can be done natively within VI.

If the same has to be done for regular SO Entry via UI, you're better off having a script add the line.

If the S&H amount is the same for each order, you can create another vi job and assign the line item. It will add as the last line for each order.

Prediction: Customer will suddenly come up with reason why ""it will never change"" explanation for shipping and handling - does in fact have to change in some circumstances.

Chain it

The second vi will simply consist of Order Number, Item code (/S&H), and the Extension. The Extension can be edited for each time you import a batch of orders.

The only issue i see with the second chained VI Job is if there are multiple lines for each order in the source file the second job will add an S&H row for each of them.

Otherwise, it's either a script or Perform Logic.

@BrettLyder, you are right. Before the import, we quickly create a second file from the source that contains ""Unique"" order numbers. We use that to import the S&H lines.

@KennyDaniel if you're doing that then you could just add the S&H line to the original source file and do one import, i guess it's really just a matter of preference. @ShawnSlavin if the original source file always has one line per order that is a certain item code or if it's a file with a separate header record, that could be used to skip lines and only import one S&H line per order.

You guys are amazing. Since I don't know scripting, I will have to outsource that if we decide to go that way. I am going to kick around the idea @KennyDaniel offered. There are multiple lines per order but I think I might be able to get the second VI job to only process one record per order number. Something is tickling the back of my mind on how to do that but I will have to play with it a little. @WayneSchulz changing requirements are what keeps the lights on. If they want to change rates, they can tweak the job or have me do it.

@ShawnSlavin, once the orders are imported, you can also export just the order number of each order and use that as the source for the line import. Your VI will be: Order Number (Replace), Item Code (Assign - /S&H), and Extension (Assign - $$$)

@KennyDaniel the export job is a great idea. I've never tried chaining an export job to an import job. Hmmmmm.

You can set up the import/export/import job with a task on the launcher set to a batch file. That way you are sure to have the import for S/H occur immediately. Make sure you have a pause between executions to let each import/export/import finish. (I learned this one from @JimWoodhead thanks Jim) REM Pause @ping 127.0.0.1 -n ##> nul ---where ## is the number of seconds.

@MoiraGoggin Do you just test the import/exports to see about how long they take and then pad it a bit?

Yes, I end up doubling the time from the test - it's only seconds so unless the test data runs more than a minute it's tolerable.