Visual Integrator: Creating a job that imports invoices into AP Invoice Data Entry

SUGGESTED

Hi all, 

I hope everybody is doing well. I apologize in advance if I post this in the wrong section. 

I recently discovered the Visual Integrator module for Sage 100 and have been trying to learn how to create a job that imports an Excel spreadsheet containing invoice information into AP Invoice Data Entry. I've followed multiple tutorials online but I seem to be running into the same error. I feel like I'm on the cusp of success but am just missing a minor detail or two. Perhaps somebody can spot the error I am making in the process. Here are some screenshots below to help illustrate my process below:

Excel Spreadsheet Template that I am attempting to import with Visual Integrator: 

Data settings: 

Results of job test: 

Record Detail displaying error message for each line:

Please let me know if further clarification is needed for anything. I'd really appreciate some guidance on this matter. 

Thank you!

  • 0
    SUGGESTED

    Judging from the error message it appears you don't have the Option set in AP Options to use Divisions. Is that possible? Remember that VI is a system module so it will only be able to import into the company you are logged into. Maybe you set this job up for a different company in Sage?

  • 0

    If you are not using Divisions you still have to assign "00" for the Division before you give it the Vendor Number. In your example the source file has Division numbers other than 00 which will not work  as you are not using divisions. In your case only 00 will work.  Also do not include the Invoice Total in the header fields as the system will calculate that based on your line detail.  An easy trick to figuring things out is to manually enter an AP invoice and note which fields you must enter in data and in what order. That is how your source file should be setup.  

  • 0
    SUGGESTED

    If your import job is set to a delimited file type as the source, be sure to Save As a CSV and use that as the source.  XLS / XLSX files are not the same as CSV.

  • 0
    SUGGESTED

    A bit more. If you do not use divisions then in the import you must set Divisions as Assigned with a value of 00. In your case you are have the import job read the column and you have 01, 02, 03, 04 and 05 which are NOT valid in a setup not using divisions, hence your error message.

  • 0 in reply to rclowe

    Hi rclowe, 

    Thanks for your reply! I'm not sure how to enable the option to use Divisions but does this make a huge difference? I am sure I set this job up for our current company though.

  • 0 in reply to AP KCAA

    Don't enable divisions unless you need them.  If turned on, vendor numbers change from VENDOR to 00-VENDOR everywhere within Sage 100, and there is no going back.

    When disabled, Sage inserts the 00 behind the scenes, but that is hidden / seamless everywhere except Visual Integrator.

  • 0 in reply to AP KCAA

    Totally agree with Kevin, DO NOT turn on Divisions unless you absolutely have thought out the entire consequence of doing so. 

  • 0 in reply to BigLouie

    , where is your Sage Reseller? These are questions you really should be asking them. 

    That being said, I am in the same boat as Kevin and Big Louie - you do not want to just turn on divisions in order to get this VI job to run. There are many other questions to answer that effect myriad aspects of the system.

    Your Sage Business Partner should be able to answer your questions fairly easily.

  • 0
    SUGGESTED

    Hi! Good news is you almost have the puzzle solved, the below solution should fix the error you're getting (it will also correct the error related to VENDOR/INVOICE #: 

    - APDivisionNO you should not be replacing the value, this value should be defaulted to assign with value of 00. 

    Column B, although you're assigning value of 00, you need to make sure you  have the column populated with data or it will pull everything over a row. Replace all the division NO's you had to 00 (convert column to text). 

    Hope this helps! I highly suggest doing this in test company since you're importing to the GL!

  • 0 in reply to BigLouie

    Sorry just saw this users solution, he is correct.