Validate Crosswalk Codes

Contents

1 Overview

2 Exception Report

3 How-to

4 Selection Criteria

5 Tables Diagram

Step 1 -- Validate Account Descriptions

The first step in creating new crosswalks is to link each district account description, or dimension, to an equivalent state reporting value. The goal is for each district-defined dimension value to reference one, and only one, state value. Each state value may be referenced by many district-defined dimension values. The state dimension values are stored in the System Crosswalk Codes (WA001SysXwalkCodes) table.

You should have already successfully completed Step 1A, using one of the following steps:

1. Created new account descriptions, using either Modify Crosswalk Codes to manually link descriptions, or Create Crosswalk Descriptions program where the system mass creates district description values to compliant state reporting values.)

2. Cloned crosswalk accounts and descriptions from a previous year, using Clone Crosswalks for Fiscal Year, followed by Clone Crosswalk Accounts for Fiscal Year.

Step 1B -- Validate Crosswalk Descriptions

Use this program to validate that each district account dimension, with a state reportable fund type as recognized by OSPI, has a valid crosswalk value for the selected fiscal year. Each state equivalent value that exists for the fiscal year you select must be included in the Washington State table of OPSI approved values.

An exception report is generated that lists any records with invalid crosswalk values for the selected fiscal year. The report lists the dimension, indicator, system code, description, crosswalk, and error description. Use the modify, clone, or create functions to correct any exceptions, and then repeat the validation process.Completion sets the Valid Descriptions"flag" to "Yes".