Sage 100

 View Only
  • 1.  Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 04-15-2014 12:47
    Issue 1: Client on 4.50 SP6. Multiple times the bank reconciliation is off. In reconciliation the out of balance goes to zero, but the reconciliation report shows out of balance. The amount is equal to one of the deposits. I rebuild BR_Transaction, and BR and GL sorts. This brings the out of balance amount in bank rec to equal the report. Then I need to add the deposit amount to the current balance in bank code maintenance. Now it reconciles with the correct ending balance. Does anyone know why this would continue to happen? Client has multiple (about 18) bank accounts and this happened to three of them this month. Exactly the same way. No error messages found in system activity log.


  • 2.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 04-15-2014 12:57
    Run the replacement script for the Embedded IO (File/Run/Syzcon, at prompt type: o=new(""sy_activation_bus"",%sys_ss) Hit enter/return for next line and type: Print o'activate(""m/m"",""XXX"") KB search EmbeddedIO. m/m = module code, xxx = company code


  • 3.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 04-15-2014 15:25
    @Joan. I will try that, thanks for the suggestion. I would like to know what that actually does.


  • 4.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 04-15-2014 18:58
    In version 4.x - because of the data file structure change there were pointers put into the DFs to redirect the program to the proper folder holding the data location instead of modifying all the varying programs. (Ever wonder why after an upgrade or conversion the SOA files are still there). For example there is a WO being created to support a SO demand, the WO module is legacy and wants the SO1 and SO2 soa files but the data is in SO_SalesOrderHeader and detail files. The embeddedIO pointer redirect the program from the SO1 to the new file SO_SalesOrderHeader. Simply put EmbeddedIO's are pointers to redirect the program from the legacy file to the new ones. When these pointers get damaged, and they will, running this script repairs or replaces the pointers. I'm told this is a no-harm no-foul script. I haven't seen or heard of any issues caused by running this script (although I do not recommend running it with extra folders in the company data directory. Keep that location clean, and remove any duplicated or copied folders. I used the script today to resolve a issue where ABC couldn't find IM_Item file when accessing an SO. Ran the script for IM, CI and SO. - Resolved. The more you muck with the data, the more often you'll likely run this script.


  • 5.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 01-05-2015 15:46
    I have this exact same issue with a customer (although they had a server crash). In reconciliation, the account is out of balance by zero but the report shows it is out of balance by over $350,000. I did the same rebuilds and now reconciliation shows the same out of balance. While I know you can plug the amount in bank code maintenance, that is currently correct and equals the GL balance. Is there another way to correct this? I hate to mess with the current balance in bank code maintenance.


  • 6.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 01-05-2015 16:44
    I always look at the Beginning balance of the Bank Recap Report to see if it matches the opening Bank Statement amount. If the amount is off by $350,000 then I look at the GL balance to see if it's possibly wrong. If the beginning balance of the report is right then there must be an errant cleared item. If there is none then I might foot the reconciliation report to see if doesn't foot which might mean there still is a corrupt record.


  • 7.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 01-06-2015 05:17
    @RonGouveia the Bank Recap report's beginning balance IS off by the $350,000! Now what? The GL balance agrees with the current balance in Bank Code Maintenance.


  • 8.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 01-06-2015 09:55
    If the beginning balance is wrong then the BR module can't balance to the bank and the current balance in bank code maintenance is probably wrong. Changing it so that the opening balance matches the opening bank statement balance will allow for the balancing of the BR module. Then the GL needs to be looked at to see if there is a $350,000 transaction that is a problem.


  • 9.  RE: Issue 1: Client on 4.50 SP6. Multiple times the

    Posted 01-06-2015 09:58
    Well, the answer is, their server crashed on 12/12 and one cash receipt and one check register from that date did NOT hit bank rec. Long process but I imported the checks (about 15) and entered the cash receipt manually. Adjusted current balance in Bank Code Maintenance and all should be good once I can rebuild BR sorts in live company. Whew!