To the greatest degree possible, anomalies in the software are eliminated through extensive testing. However, it is virtually impossible to predict every bug simply because there will be usage methods and unique scenarios attempted in production that could not have been predicted by FCMAT during testing. As such, FCMAT will use this Web site to convey information about known issues with the software. This site will be updated daily.

Please be sure to conduct a “reasonability check” of your projection(s) to validate completeness/correctness to your satisfaction. To conduct a reasonability check, review your revenue and expenditure totals, and the corresponding impact to ending fund balances to ensure that the projection data is calculating correctly based on your expectations and projection assumptions.

FCMAT is available to conduct a cursory review of your projection(s) should you desire. If you discover a problem with Budget Explorer, please report it directly to Andrew Prestage for immediate resolution.

Thank you for your continued use and support of Budget Explorer!

Known Issues as of Monday, August 29, 2005:

1. Calculation Error on Inflation Increase

Where Problem Occurs: This problem appears in the SACS RL Calculation Screen.
Description of Problem: The software is incorrectly calculating the amount on line 2. Currently, it is multiplying the amount entered in line 1 by the StCOLA variable, generating an incorrect inflation increase amount. It SHOULD multiply the Prior Year Statewide Average RL per ADA (from the St Avg RL system table) by the STCOLA variable to generate the correct inflation increase.
Date Reported: Monday, August 29, 2005
Reported By: Andy Prestage

2. LOT-Unr Rule Problem

Where Problem Occurs: In all resources (restricted and unrestricted) “Other State Revenues” screen “State Lottery Revenue” object detail line (object 8560).
Description of Problem: The system is programmed to automatically include the LOT-Unr rule. A problem occurs when there is no amount (a zero) in the base year field, causing the software to add the value associated with the LOT-Unr rule to both projected years. For example, if the LOT-Unr rule is set to $117 in the 1st projected year and $110 in the 2nd projected year, the software will display $117 in Proj Year 1 and $227 in Proj Year 2, even if there is a zero in the base year field. To fix this, make it so that the software computes the % change from one year to the next in LOT-Unr, NOT THE ACTUAL DOLLAR AMOUNT, and apply the % change to the base year amount ONLY IF THERE IS A NON-ZERO VALUE AVAILABLE TO BE APPLIED TO. Be sure to allow the software to apply the LOT-Unr rule even if a value is created by the Manual Input rule, or any other rule that produces a non-zero value, whether it be in the base year or any of the projected years.
Date Reported: Wednesday, July 20, 2005
Reported By: Andy Prestage