In SL 7.0 (no feature packs, no service packs), Cash Manager module, Bank Reconciliation Report: when I run the report, it does not match what is in the Bank Reconciliation Screen. The GL balance for the period is zero, yet the report shows a GL balance (balance from the bank accounts preceding the ones with the error) and, therefore, reports an out of balance situation, but only if I run a series of bank accounts. If I run the report for only one bank account, the report is correct. In reviewing the wrkcabalances table, I see that there are values there before I run the report. While the report is in print preview, the wrkcabalances table is populated with more records (one for each bank account on the report). There are differences in the records for what is on the print preview report, including no CuryID.
Is the wrkcabalances table supposed to be empty if no report is running?
Short answer is yes - it should be empty except for when reports are run. Deleting the records that are still there when no report is being run should be fine.
Look at the RI_ID value of the wrkcabalances records. That value ties to the RI_ID value in an RptRuntime record. An RptRuntime record is created every time a report is run. There is some information here about who is running the report and the options they selected.
When Crystal Reports queries the database, it should only get the wrkcabalances records whose RI_ID value matches the current report run. If a previous run crashed, the post-process may not have cleaned up all the records.
More details here - wisdomofsolomon.wordpress.com/.../dynamics-sl-solomon-reporting-framework-roiexe-part-2 - if you're interested.
Jeff, I was able to confirm that deleting the records was fine. There were many records hanging in the table. I don't know if this is a bug, but for new bank accounts with no activity in GL and where the user reconciled the account in Cash Manager, the record in wrkcabalances inherits the CuryGLBalance from the previous record. Everything else on the record appears the same as any other zero balance account (with GL activity). Have you ever heard of this issue?
That seems consistent with how Cash Manager calculates balances in the Bank Rec screen. Normally I would think that would be OK (last month's ending balance is this month's beginning balance)
I actually got a blog post on this as well - wisdomofsolomon.wordpress.com/.../cash-manager-gotchas
Here's a relevant excerpt:
"When the Bank Reconciliation screen calculates the Cash Manager balance (when there has been a previous Bank Rec), it goes to the previous Bank Rec record and calculates what the cash manager balance was at that point and then only considers CashSumD records between the previous recon date and the new recon date.
What this means is – if you “backdate” any transaction affecting cash (CA, AR, AP, GL) to a date earlier than the last completed Bank Reconciliation, that transaction’s affect on the Cash Manager balance won’t be recognized by the Bank Rec screen when calculating the Cash Manager balance as of the new Bank Rec.
If you have reconciled a Cash Account as of 11/30 and subsequently enter a transaction dated 11/15, when you try to do a Bank Rec for 12/31 – the Bank Rec screen’s calculation of the Cash Manager will be different than what you will see for that date in the Daily Cash Balances screen when you click the Balances by Date button. Once you have this situation, it will be hard to get it resolved without a very good understanding of Cash Manager operation."
I think that is part of it. Since the account has no previous activity there is no CashSumD record and somehow the calculation gets thrown off.
Example of what I see:
Bankacct CuryGLBalance GLBalance
10367 2321.48 2321.48
10368 2321.48 0
When I run the Bank Recon report I get the same GL balance for both accounts even though 10368 has never had any GL activity in the account. Again, this is only if I run the report for all accounts under the company id. If I run each account individually, I don't get the same answer.
The easy fix, from my perspective, is to tell the users not to process a bank reconciliation if the account has no activity (i.e. new bank account just created). But with a hundred or so accounts, it may not be feasible.
Hey, Jeff. I just found something in CustomerSource that sort of confirms my theory that this is a bug. Partner Only Article ID: 959273 - Last Review: December 12, 2008 - Revision: 1.1
The article describes my issue. The correction is in feature pack 1 and service pack 2. I have neither of them, yet.
Thanks so much for your help.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13