Search Results igs_pe_pers_disablty




Overview
Explore in AI Chat

Overview

The IGS_PE_PERS_DISABLTY table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. It serves as the central repository for storing and managing disability-related information for persons, which are typically students or applicants. Its primary role is to record the specific disabilities a person has reported, along with associated details regarding special requirements, support levels, and services. This data is critical for enabling institutions to comply with accessibility regulations, provide appropriate accommodations, and manage student support services effectively across both EBS 12.1.1 and 12.2.2 versions.

Key Information Stored

The table captures a comprehensive disability profile for a person. The primary key is a surrogate key, IGS_PE_PERS_DISABLTY_ID. The logical unique key combines PERSON_ID, DISABILITY_TYPE, and START_DATE, allowing a person to have a history of records for the same disability type over time. Essential columns include PERSON_ID, linking to the HZ_PARTIES table to identify the individual, and DISABILITY_TYPE, a foreign key to IGS_AD_DISBL_TYPE that classifies the disability. The table also stores temporal data (START_DATE, END_DATE) and foreign keys to code lookup tables (IGS_PE_CODE_CLASSES) for SPECIAL_ALLOW_ID, SUPPORT_LEVEL_ID, and SPECIAL_SERVICE_ID, which categorize the accommodations and support required. Additional columns may capture details like an INTERVIEWER_ID (linked to HZ_PARTIES), verification status, and descriptive comments.

Common Use Cases and Queries

This table is central to disability reporting, accommodation planning, and compliance auditing. Common operational and reporting scenarios include generating lists of students with active disabilities for disability services offices, identifying students eligible for specific exam accommodations, and producing statistical reports on disability prevalence for regulatory bodies. A typical query pattern involves joining to person (HZ_PARTIES) and disability type (IGS_AD_DISBL_TYPE) tables.

Sample SQL Pattern:
SELECT ppd.person_id, hp.party_name, adt.disability_name, ppd.start_date
FROM igs.igs_pe_pers_disablty ppd,
     hz_parties hp,
     igs_ad_disbl_type adt
WHERE ppd.person_id = hp.party_id
AND ppd.disability_type = adt.disability_type
AND ppd.end_date IS NULL -- For current disabilities
AND SYSDATE BETWEEN ppd.start_date AND NVL(ppd.end_date, SYSDATE);

Related Objects

The IGS_PE_PERS_DISABLTY table maintains integral relationships with several key EBS objects, as documented by its foreign key constraints.

  • HZ_PARTIES (Trading Community Architecture): Linked via PERSON_ID (the person with the disability) and INTERVIEWER_ID (the staff member who recorded the information). This is the master source for person/party data.
  • IGS_AD_DISBL_TYPE (Student System): Linked via DISABILITY_TYPE. This table provides the valid list and descriptions of disability classifications.
  • IGS_PE_CODE_CLASSES (Student System): Linked via three separate foreign keys: SPECIAL_ALLOW_ID, SUPPORT_LEVEL_ID, and SPECIAL_SERVICE_ID. This table stores the code values for types of allowances, levels of support, and specific services.
  • IGS_PE_SN_SERVICE (Student System): This table references IGS_PE_PERS_DISABLTY via its DISABILITY_ID column, linking specific disability records to student support service instances.
  • IGS_PE_SN_CONTACT (Student System): Similar to the service table, this object references the disability record via its DISABILITY_ID column, linking disabilities to support contacts.