Skip to main content
California Department of Education Logo

SACS2011 Budget Software: Known Problems/Fixes

The sacs2010setup.exe file will not include fixes made subsequent to the SACS2011 software release. If any problems are found, we will list them here and provide any revised files or workaround instructions.

Problem: Technical Check CHK-RS-LOCAL-DEFINED

  • Users Affected: All users whose data contains locally-defined SACS resource codes that have not been rolled up to the CDE-defined resource codes.

  • Problem: Although technical review checks are supposed to run for one data type and one LEA at a time, this fatal check will flag an exception and display all "exception" account code strings for all data types and LEAs that are in the user's SACS software database and that do not pass this check.

  • Fix: Disable this check for Budget reporting periods. Save this chk-rs-local-defined.txt file (TXT; Revised 14-Jun-2011) to your C:\SACS2011\ subdirectory. To save, right click on the file name, click on Save Link As (or Save Target As), select the C:\SACS2011 subdirectory, then click Save. Do not save this file to C:\SACS2011\Update or you will encounter errors the next time you run a validation table update. Once the file is saved, open the software and go to File, Update Tables. Click Browse for Input, and select the chk-rs-local-defined.txt file. Click Open, then Update Tables.

  • Note Regarding Fix: When this check is disabled, no other TRC will flag locally defined resource codes that are not rolled up to state-defined resource codes. Technical review check CHECKRESOURCE no longer flags locally defined resource codes.

    CHK-RS-LOCAL-DEFINED will be reactivated in the SACS2011ALL release, but the severity will change from fatal to warning for one year only. In the SACS2012 software, the severity will be reinstated to fatal.

Problem: Components of Ending Fund Balance (CEFB)

  • Users Affected: Those who use the Form CEFB to enter or change any components, AND who do not use the “New Designation/Assignment/Commitment” buttons to enter the components at a detailed level for Other Designations, Object 9780 (estimated actual data) and/or Other Commitments, Object 9760, and Other Assignments, Object 9780 (budget data).

  • Users Not Affected: This problem does not affect users who do not use Form CEFB.

  • Problem: When the exported data file is subsequently "Other" imported, either by the same user or by another user such as a COE, objects 9760 and 9780 are replaced with zero values unless they were added as detailed lines using the “New Designation/Assignment/Commitment” buttons in Form CEFB.

    This problem does not occur if the data is subsequently “Officially” imported. It is only a problem if the data is subsequently “Other” imported.

  • Note Regarding Workaround: The following workaround should be completed as the last step before final export. If this workaround is completed and the user subsequently opens and saves Form CEFB, this workaround may need to be reapplied.
  • Workaround:

    Step #1—Open Form CEFB.

    Step #2—For each object 9760 and 9780 that should not equal zero, use the “New Designation/Assignment/Commitment” buttons to add a detailed line item (including a description and value).

    For example, if Other Commitments was originally entered on the “general” Object 9760 line, like this:

    Other Commitments 9760 $100.00

    Then a detailed line item will need to be entered instead, like this:

    Press “Add Commitment” button.

    Other Commitments 9760 $100.00 (now a locked, calculated field)
    Other Commitment $100.00 (newly keyed)

    Step #3—Save Form CEFB.

Problem: Technical Check CHK-FUNDxOBJECT, related to Components of Ending Fund Balance (CEFB)

  • Users Affected: Those who use the Form CEFB to enter or change any components for debt service funds 51, 52, 53, and 56, for 2010-11 estimated actuals only.

  • Users Not Affected: This problem does not affect users who do not use Form CEFB.

  • Problem: When the exported data file is subsequently "Other" imported, either by the same user or by another user such as a COE, Object 9780 is correctly recalculating to zero as expected since this object is not valid in these funds; however a CHK-FUNDxOBJECT exception may generate for account strings with a zero value for Object 9780 with these funds. Because CHK-FUNDxOBJECT is fatal, the user is unable to complete an official export.

  • Workaround Option #1: Allow LEAs to submit Budget datasets as "Other" export, instead of "Official" export, on the condition that: 1) the only fatal exception is CHK-FUNDxOBJECT; 2) the only flagged account strings in CHK-FUNDxOBJECT are for zero amounts; and 3) in the transmission e-mail or letter, the LEA provides an explanation for the fatal CHK-FUNDxOBJECT. District, JPA, and charter schools' use of this workaround will be at the discretion of the COE.

  • Workaround Option #2: This workaround should be completed as the last step before final export. For Workaround Option #2, follow these steps:

    Step #1--Open Form CEFB and select the 2010-11 Estimated Actuals data group; fund 51, 52, 53, or 56; and the appropriate resource.

    Step #2--For each Object 9780 that has the account code string with a zero value flagging in CHK-FUNDxOBJECT, enter a zero in the Other Designations Object 9780 "general" line. 

    Step #3—Save Form CEFB.

    Step #4—Run the TRC for estimated actual data. CHK-FUNDxOBJECT should not flag as an exception.

    Step #5—Officially export the data.

    Step #6—IMPORTANT! All subsequent importing of the data set must be officially imported or the problem will recur. Make sure the COE is aware of this when submitting the data file to them.

Problem: Known Problem with Windows 7

Some users have reported problems running the SACS software on Windows 7 64-bit PCs.

Workaround: Although we are researching possible workarounds, these problems are currently unresolved. If and when a workaround is identified, it will be posted here.

Problem: Run-time Error 429

Periodically, the required Microsoft Data Access Components (MDAC) file is not properly installed on Windows 98 machines, causing a run-time error 429 upon opening the Standardized Account Code Structure (SACS) software.

Fix: Be sure all other applications are closed, then download this MDAC file: mdactyp (EXE; 7MB). Once downloaded, double-click on the file to begin installation (be sure to read the prompts thoroughly). When the installation is completed, the SACS software should open properly.

Questions:   Financial Accountability & Information Services | sacsinfo@cde.ca.gov | 916-322-1770
Last Reviewed: Thursday, August 27, 2015
Recently Posted in Software & Forms
  • Charter School Alternative Form 2015-16 (updated 22-Aug-2016)
    Download the 2015-16 Charter School Unaudited Actuals Financial Report Alternative Form as well as instructions on how to complete the form.
  • Financial Reporting-Prior Years' SACS Software (added 08-Aug-2016)
    Standardized Account Code Structure (SACS) software used by local educational agencies to prepare budgets, interim reports, and year-end financial reports to the California Department of Education.
  • SACS2016ALL Software Release Letter (added 08-Jul-2016)
    This letter addressed to county and district chief business officials and charter school administrators.
  • SACS2016ALL Software: Known Problems/Fixes (added 30-Jun-2016)
    The sacs2016allsetup.exe file will not include fixes made subsequent to the SACS2016ALL software release. If any problems are found, we will list them here and provide any revised files or workaround instructions.
  • Financial Reporting-SACS2016 Budget Software (added 30-Jun-2016)
    Software used by local educational agencies to prepare budgets, interim reports, and year-end financial reports to the California Department of Education.