{{ model.title }}
This page is currently being edited by {{ model.editingBy }}.SmartFusion Modules -> Utility Billing -> Bill Run Wizard
Recent Changes:
6.204
- Added a check for invalid zip codes to the bill run errors report.
6.203
- Added a check for fixed services to the error report to check if taxable is checked without a transaction code.
6.176
- Added an error if the usage is greater than or equal to 99 million to handle situations where really high usage was causing the service charge being calculated to be so high that it was causing arithmetic overflow errors when running the calculate report.
6.76
- Added an exception report that catches possible meter errors that could cause the application to crash. So far it is only checking for usage that is high enough to cause an overflow error.
Introduction
This page details the functionality of finding bill run errors and the report that displays them.
Explanation
This report will list any errors than may cause the initial bill run calculations to crash. It will output the needed data in order to located the offending accounts, meters, or locations so that the user may correct the issue.
Exceptions:
Overflow Usage Error - Usage greater than Maximum integer value
High Usage Error - Usage greater than or equal to 99,000,000
Overflow Current Reading Error - Current Reading greater than Maximum integer value
Overflow Previous Reading Error - Previous Reading greater than Maximum integer value
Fixed Service Transaction Code Is Zero - If taxable is checked without a transaction code
Scenario to produce error:
- go to a meter, set number of dials to be 10 or more.
- set a current usage on the customer for that meter to be less than the previous usage and have it treated as a rollover.
- set it close enough to the previous usage but under will result in a total usage that is far higher than the allowed maximum integer.
If an account calculates a usage on a meter that is greater than the maximum integer (2,147,483,647)
This can be reproduced by giving a meter a high number of dials that could potentially create a maximum number greater than the maximum allowed integer. This report will list that so there are no issues.