Search Results school_dst_code




Overview

The HR_S_US_CITY_SCHOOL_DSTS table is a reference data table within the Oracle E-Business Suite (EBS) Human Resources (HR) module. It serves as a foundational repository for mapping and validating United States school district codes to their corresponding geographic locations. Its primary role is to maintain the hierarchical relationship between a school district and the specific city, county, and state in which it resides. This structured data is critical for ensuring data integrity in processes that require precise geographic and jurisdictional information related to employees or organizational reporting, particularly for U.S.-specific legislative or reporting requirements within the PER product family.

Key Information Stored

The table's structure is designed to uniquely identify a school district within its geographic hierarchy. The primary key, as documented, is a composite of four columns, establishing this precise linkage. The most critical columns are:

  • SCHOOL_DST_CODE: The unique identifier for a specific school district.
  • STATE_CODE: The code representing the U.S. state where the district is located.
  • COUNTY_CODE: The code for the county within the specified state.
  • CITY_CODE: The code for the city within the specified county and state.

Together, these columns form the primary key constraint HR_S_US_CITY_SCHOOL_DSTS_PK, ensuring that each combination of district, state, county, and city is unique within the system.

Common Use Cases and Queries

This table is predominantly used in validation and reporting scenarios. A common use case is validating an address or a tax jurisdiction against approved school districts during data entry or batch processing. For reporting, it enables the generation of demographic or compliance reports segmented by school district geography. A typical query pattern involves joining this table to employee address or assignment tables to associate personnel with their relevant school district for tax withholding purposes. For example, to list all school district codes for a specific state and county, one might use:

SELECT SCHOOL_DST_CODE, CITY_CODE FROM HR.HR_S_US_CITY_SCHOOL_DSTS WHERE STATE_CODE = 'CA' AND COUNTY_CODE = '001';

Another critical pattern is using the table to decode a full geographic description for a given SCHOOL_DST_CODE by joining to related state, county, and city reference tables.

Related Objects

Based on the provided relationship data, the HR_S_US_CITY_SCHOOL_DSTS table is centrally linked through its primary key. Other tables and views within the HR schema will likely have foreign key constraints referencing the HR_S_US_CITY_SCHOOL_DSTS_PK. These related objects could include tax withholding tables, address validation entities, or reporting views that require school district context. The join would typically be performed on some or all of the primary key columns: SCHOOL_DST_CODE, STATE_CODE, COUNTY_CODE, and CITY_CODE. For precise identification of these dependent objects, one must consult the EBS data dictionary views, such as USER_CONSTRAINTS, to find tables where these columns form a foreign key back to this table's primary key constraint.