Search Results special_allow_id

Overview

The IGS_PE_PERS_DISABLTY table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (OSM) or related educational modules under the IGS (iGrants/Student) schema. Its primary function is to store and manage detailed disability information for individuals (typically students) within the system. The table acts as a central repository for recording a person's specific disabilities, associated support requirements, and administrative details such as eligibility for accommodations and the source of the information. It plays a critical role in enabling institutions to track, report on, and provide necessary support services for individuals with disabilities, ensuring compliance and facilitating student services operations.

Key Information Stored

The table's columns capture a comprehensive range of data points related to a person's disability profile. Key fields include the mandatory PERSON_ID and DISABILITY_TYPE, which together with START_DATE form a unique key (IGS_PE_PERS_DISABLTY_U2) to track disability records over time. The IGS_PE_PERS_DISABLTY_ID serves as the primary unique identifier. Administrative flags such as ELIG_EARLY_REG_IND and DOCUMENTED indicate specific accommodations and verification status. Notably, several columns related to specific services and allowances—including the user-searched SPECIAL_ALLOW_ID, along with SUPPORT_LEVEL_ID, SPECIAL_SERVICE_ID, and CONTACT_IND—are explicitly documented as OBSOLETED in the provided metadata, indicating they are likely deprecated in these EBS versions. The table also includes standard WHO columns for auditing and date ranges (END_DATE) to manage the active period of a disability record.

Common Use Cases and Queries

This table is central to disability reporting and service management. Common operational and reporting scenarios include generating lists of students with active disabilities for accommodation planning, verifying eligibility for early course registration, and auditing the source and documentation of disability information. A typical query to find all current, documented disabilities for a specific person would leverage the date and indicator fields.

• Sample Query: Retrieve Active Disability Records
  SELECT person_id, disability_type, start_date, elig_early_reg_ind, info_source FROM igs.igs_pe_pers_disablty WHERE person_id = :p_person_id AND (end_date IS NULL OR end_date > SYSDATE);
• Reporting Use Case: Creating a report for the disabilities office listing all students eligible for early registration, including their disability type and interview date, if applicable.
• Data Integrity: Due to the obsolete status of columns like SPECIAL_ALLOW_ID, any custom integrations or reports referencing these fields should be reviewed and potentially migrated to newer, supported data points or related tables.

Related Objects

Based on the dependency and key information provided, this table has defined relationships with other entities in the IGS schema. The unique indexes suggest its integration points.

• Primary Key Relationship: The IGS_PE_PERS_DISABLTY_ID column is the primary key, enforced by the unique index IGS_PE_PERS_DISABLTY_U1. This ID is the likely foreign key reference for any child tables or detail records that store information specific to a single disability entry.
• Foreign Key Relationship (Probable): The PERSON_ID column is almost certainly a foreign key referencing a core person or party table, such as IGS_PE_PERSON or HZ_PARTIES, to link the disability data to the individual's master record.
• Lookup Dependencies: The DISABILITY_TYPE column likely references a user-defined lookup table (e.g., IGS_LOOKUPS) containing the institution-defined values for disability classifications. Similarly, the INTERVIEWER_ID would reference a person/employee table.
• Obsolete Column References: The obsolete columns (SPECIAL_ALLOW_ID, SUPPORT_LEVEL_ID, SPECIAL_SERVICE_ID) historically pointed to related allowance, support level, and service definition tables, but these relationships are no longer valid for active development in versions 12.1.1 and 12.2.2.