Sage 100

This goes back to the customer I had to redo the migration/conversion and Sage was giving me all the grief about test to live upgrades, etc. Well, things went well for the 2nd migration/conversion and all was good until the VI jobs needed to be run. The VI Job goes into GL_JournalHeader and throws: 'Error 200, line 18, An Unexpected error occurred in VIWI00 during import Error: 200'. This only appears to happen in companies without IM/PO/SO/multi-bin activated. I've recreated the job and still throws the error. Sage (this is another good one!) told the customer to activate the remaining modules (IM/PO/SO/MB) for the other companies and see if that works. Really? Would MB really have anything to do with this? I can certainly call them but reaching out to my friends here first. Sage 100 Advanced V2013.

(my several cents worth:) Because it's Friday and they can't hurt me on Friday) By your description I'm thinking linking issue. Run the embedded IO replacement script for all companies and modules. I know- I say that a lot, like a scratched LP record, but here's why I think it is applicable in your situation. I ran into an after upgrade problem that was being cause because the customer had never entered a Sales order but was using SO Invoicing. It was an upgrade and this process in use since startup. No records existed for SO Entry or SO Quote History. If I recall correctly the issue was an error when trying to post the SO Invoices. The update wouldn't post to GL and generated an error that normally generates when the data is corrupt. Brought the client data inhouse and noticed NO SO records- none. I thought this odd and entered an SO, invoiced and updated. The error could not be replicated after that. Not even for the existing invoice batch that was erroring out. So odd. Only one SO had to be created in SO entry for the error to resolve. The channal partner and I figured there had to be some linking mechanism that wasn't synched between the two tasks, SO Entry and SO Invoicing, that was affecting the update. Research PER was submitted to engineering on the matter. Low and behold, A KB on how to run the script to replace embedded IO's.

Run this for all modules/companies, even if the module is or is not activated for that company? Worth a shot, thanks! Have a good weekend!