The operational unit (OPU) is part of the 30 digit USAS account code that defines the location of education activities and is defined at the district level. The OPU interface allows the user to define these Operational Unit codes with three digits which will be considered valid by the system when entering USAS accounts in the various processing programs.

Create an OPU

Open

1. From the Core menu select 'OPUs.'

2. Click on .

3. Enter in the required information:

   1. The description should not contain a carriage return as this causes problems with EMIS H data.

   2. Check the box if the OPU is the Central Office OPU.

      
      
      

4. Click on to create the OPU.  Click on  to not create the OPU and return to the OPU grid.

Search/View OPU

The OPU Grid allows the user to search for existing operational units on the system. Click on  to view the details of a particular OPU.

Edit an OPU

Existing OPUs may be modified. All the fields except for the OPU code are modifiable.

1. Search desired OPU on grid.

2. Click on the edit icon to edit the OPU.

3. Make the desired changes.

4. Click on  to save the changes on the OPU.  Click on to not post the changes and return to the OPU grid.

Delete an OPU

1. Search the desired OPU on grid.

2. Click on the delete icon  to delete the desired OPU.

3. Click on  to confirm the deletion.

Import OPUs

The Import OPUs option may be used to import new OPUs from a spreadsheet (CSV format).   Please refer to the OPU Import Criteria for further details on the CSV file format.  We've also provided a template spreadsheet for districts to use. 

1. From the Core menu select "OPUs"

2. To import a CSV file, click on 

3. Click on "Choose File", browse for the file (.CSV) and click "Open" or select the file by double-clicking on the file name.

4. The selected filename will be visible to verify the system is ready to load the proper file.

5.  Click on "Load" to process the chosen file and post the transactions. 
   
   

   Open

   

6. A message box will appear showing the number of Records Loaded and the Number of Errors.  

7. An output file named “USASLOADERR.CSV” will be created containing the number of records loaded or records with errors. 

 a.   If there are records that did not load, the file will contain only those records that did not load successfully and will provide error messages explaining why.  

                 b.  If there were no errors, the file will say "No errors. Records loaded: #" where # is the number of records successfully loaded

8. If an error occurs, open the output CSV file, make the necessary corrections, and re-import the corrected output file. 

OPU Import Criteria

Please use the containing the fields in the proper format (listed in the table below).  If you are not using the template spreadsheet and instead you are creating a spreadsheet of your own, the field names are not case sensitive, but must be entered exactly as shown below making sure to include the spaces between words.  (i.e CENTRAL OFFICE and central office are both acceptable, but CentralOffice causes an error.)  Please note, the fields specified below as "Required field" are the only fields that must appear in the spreadsheet.  All other fields are optional.

More Information

The OPU is the USAS dimension that identifies facilities of the school system. An operational unit is identified as a permanent operational entity such as a school, administration building, warehouse, department, office, etc. This dimension is used to identify costs by unit or facility and is assigned by the school district.  By using the OPU codes, the user is also able to sort reports according to the operational units defined in the OPU interface. Such an option is useful to management as they examine spending patterns in the individual buildings in their districts. The entity type is set to "C" if the OPU is set up to track central office expenses. Otherwise, the entity type is left blank.

When defining OPUs, you must include the following:

1. A three digit number between zero and 998.

2. A description of that number. The OPU description should not contain a carriage return/enter as this will cause problems with the data collector.

3. The IRN associated with the OPU entered.

4. An OPU of "000" must be entered with the district IRN.