Showing posts with label ledger. Show all posts
Showing posts with label ledger. Show all posts
Wednesday, June 4, 2008
Illegal Connections
Finally, I was able to modify the Ledger and Teller modules to FLASH THE STATUS of the consumer when it's current status is "ILLEGAL", whether or not it is ACTIVE or INACTIVE.
Thursday, November 8, 2007
BCMS improvement, plus possible bug
First, the good news. DPP requested me to include the Suffix in the Search window when looking for a name in the Ledger module. I did it one better: I included the middle name, too.
Now for the bad news. Agnes complained that the Miscellaneous Report-Final VAT Report is inconsistent with the "FINAL VAT Detailed Collection report per pay type". Particularly with the Oct. 2, 2007 Final VAT remittance of Account # 32780 (168 Victoria Square). I was at a loss why the report was not seeing the 2 payment details for that single O.R., and had spent several minutes looking for the problem on the query statement when I noticed my Payment Editor that the bill_no_id fields for the 2 "invisible" details was too high (>7,000,000) particularly because the bill_no was for the month of August 2007 and the bill_no_id for the 3rd detail was only in the 2,200,000 range and that was for Sept 2007! So I merely corrected the bill_no_id and the bill_date (which contained the "current" date for that posting - 10/02/2007 - instead of the real bill_date which is 08/14/2007).
I'll have to do experiments on this to catch the bug. Low priority, though.
Now for the bad news. Agnes complained that the Miscellaneous Report-Final VAT Report is inconsistent with the "FINAL VAT Detailed Collection report per pay type". Particularly with the Oct. 2, 2007 Final VAT remittance of Account # 32780 (168 Victoria Square). I was at a loss why the report was not seeing the 2 payment details for that single O.R., and had spent several minutes looking for the problem on the query statement when I noticed my Payment Editor that the bill_no_id fields for the 2 "invisible" details was too high (>7,000,000) particularly because the bill_no was for the month of August 2007 and the bill_no_id for the 3rd detail was only in the 2,200,000 range and that was for Sept 2007! So I merely corrected the bill_no_id and the bill_date (which contained the "current" date for that posting - 10/02/2007 - instead of the real bill_date which is 08/14/2007).
I'll have to do experiments on this to catch the bug. Low priority, though.
Tuesday, July 17, 2007
BCMS User-Friendliness Updates
After the last time I made changes and improvements to BCMS, I've done the following:
1. Fixed the "not unpressed buttons" issue on the Consumer Ledger and Consumption buttons in the Ledger module.
2. Gave access to Disconnection clerk to the overpayment application module because she needs to see which (and how many) months the receivables were for. Initially, she only wanted me to force the Ledger tab in the Ledger module to display the last entry, but I was not able to find a way, at first.
3. In relation to #2, found the way to force the listviews on the Ledger module to ensure that the last item is visible [listview.listitems(listview.listiems.count-1).ensurevisible or some such hocus-pocus].
4. Switched the listviews in the Ledger module not to HIDE the SELECTION highlight when out of focus.
5. Added Syntax-error Prevention code on Bill Posting module when searching for areas.
6. Pressing ENTER on Area field will now erase the contents, if it already has been looked up prior.
7. Added TOTALs to the financial columns in Overpayment module.
8. Switched reports on Rose's new PC to the Epson FX-1170 driver.
1. Fixed the "not unpressed buttons" issue on the Consumer Ledger and Consumption buttons in the Ledger module.
2. Gave access to Disconnection clerk to the overpayment application module because she needs to see which (and how many) months the receivables were for. Initially, she only wanted me to force the Ledger tab in the Ledger module to display the last entry, but I was not able to find a way, at first.
3. In relation to #2, found the way to force the listviews on the Ledger module to ensure that the last item is visible [listview.listitems(listview.listiems.count-1).ensurevisible or some such hocus-pocus].
4. Switched the listviews in the Ledger module not to HIDE the SELECTION highlight when out of focus.
5. Added Syntax-error Prevention code on Bill Posting module when searching for areas.
6. Pressing ENTER on Area field will now erase the contents, if it already has been looked up prior.
7. Added TOTALs to the financial columns in Overpayment module.
8. Switched reports on Rose's new PC to the Epson FX-1170 driver.
Thursday, June 28, 2007
BCMS: Historical data on consumers
Finally got to finish the Connection History and Meter History tabs in the Consumer Ledger! :-)
Subscribe to:
Posts (Atom)
