OperatingBudgetManual2015

Operating Budget Manual – August 2010

b. Critical Errors – After it is determined there are no fatal errors, there are several checks run against the data and if these checks result in errors, the file can be uploaded but not finalized until the errors are fixed. These are called “critical” errors. Some include i. Invalid Account Number – the account number does not exist in the campus’ chart of accounts ii. Invalid sub-object code - the sub-object does not exist or is not valid iii. Input Fund not equal Chart Fund xxxxx – the fund in the Excel file (column A) does not match the fund in the Chart of Accounts associated with the account number iv. Allocation to Master Account Invalid – the account has sub- accounts but the Form 1 is loading to a master account v. Fund data does not match targets – data upload does not match campus targets, by fund c. Warnings – there are additional checks to the data that warn the user of inconsistency, but that might be valid. The user should review these warnings and if unintentional, make the necessary changes to the file. If the warning is correct and intentional, the file can still be finalized. Some include i. $$ missing for 0000 object / $$ missing for 0400 object - FTE with no dollars for 0000 or 0400 ii. FTE missing for 0000 object / FTE missing for 0400 object – dollars with no FTE for 0000 or 0400



0

d. Information – Not technically errors, these are messages telling the user about the status of an upload. These include the date/time and userid of the last submitted or finalized file. Note : Messages are sorted by importance to the process. First will be fatal errors; fatal errors are listed by themselves. If the file passes all the fatal error tests, then

61