Sage 100

Goal: Have an Excel file with multiple transactions, import each line in the file into a separate batch, and a separate transaction entry. Utilize the ""next"" feature in VI to have the system grab the next transaction entry number for the record. SCENARIO: Use a REPLACE function on the batch number, and specify a blank field. Use the NEXT function for the Transaction Entry number. RESULT: The next batch number is used, but it puts all transactions into one batch. All transactions with the same header details are put into the same transaction. SCENARIO: Use a REPLACE function on the batch number, and specify an actual data field. Use the NEXT function for the Transaction Entry number. RESULT: The batch number of the first transaction is used only, and puts all transactions into that one batch. The other batch numbers are ignored. All transactions with the same header details are put into the same transaction. SCENARIO: Specify the Transaction Entry Number, and the batch number in the source file. RESULT: Get multiple batches and multiple transactions. However, the last scenario isn't ideal because we aren't using the transaction numbers from MAS 90. Any suggestions?

Why not NEXT the Batch Number AND the Transactino Entry Number?

NEXT isn't an option for batch number. Well technically it's there but if you try to pick it, it tells you ""Nuh uh, can't do that.

Figures. :-(

Perform logic in the VI job can be used to prep the file prior to importing. Perform Type of On Execution will execute prior to running the VI job. I don't know Providex, so I use vbscript and compile it to an exe file. To force the program to complete prior to starting the VI job by putting a '~' at the beginning of the command (Example ~..\CM\SCRIPT\TransPrep.exe). The prep utility could query MAS and get the starting transaction and/or batch number.