Need help creating a VI Job

I am new in this company and I found out that previous people were not knowledgeable of the Bank Reconciliation Module.

I am now facing a the situation that though we only have 1 bank account, 2 different Bank Code have been assigned to it, making it impossible to reconcile.

How can I create a VI Job (export, then import) that replaces "Bank code 4" with "Bank code C"

Thanks a lot everybody!

Parents
  • 0

    I don't work with BR much but since the bank code is part of the primary key, you can't just change/update it. I'm also unsure of what kind of impact changing the bank code in BR_Transaction would have on other modules' historical data that might reference the bank code used at the time of the transaction. Might be best to discuss with your reseller or wait for someone else's opinion on this. If it is safe to change the bank code in BR_Transaction alone, you could export all the data in it, then reinitialize the file, change the bank code in the exported data, and then import it all back in but i'd be weary of any fields that are read only and can't be updated through VI because they are normally set by Sage 100's logic when writing records to the file from the other integrated modules. Never attempt something like this in your production company without first attempting it in a test company and verifying the results are acceptable. You can always copy your production company to a test company code for this purpose.

Reply
  • 0

    I don't work with BR much but since the bank code is part of the primary key, you can't just change/update it. I'm also unsure of what kind of impact changing the bank code in BR_Transaction would have on other modules' historical data that might reference the bank code used at the time of the transaction. Might be best to discuss with your reseller or wait for someone else's opinion on this. If it is safe to change the bank code in BR_Transaction alone, you could export all the data in it, then reinitialize the file, change the bank code in the exported data, and then import it all back in but i'd be weary of any fields that are read only and can't be updated through VI because they are normally set by Sage 100's logic when writing records to the file from the other integrated modules. Never attempt something like this in your production company without first attempting it in a test company and verifying the results are acceptable. You can always copy your production company to a test company code for this purpose.

Children
No Data