Search Results igs_pe_res_dtls_all




Overview
Explore in AI Chat

Overview

The IGS_PE_RES_DTLS_ALL 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 detailed residency information for students. Residency data is critical for determining tuition fee calculations, eligibility for state or federal financial aid, reporting requirements, and compliance with institutional policies. As an "ALL" table, it is designed to support the multi-organization architecture of EBS, meaning it can store data partitioned by the operating unit, allowing a single installation to manage data for multiple institutions or legal entities. Its role is to maintain a historical and current record of a student's residency classification and status over time, often linked to specific academic calendar periods.

Key Information Stored

The table's structure is designed to uniquely identify a student's residency record for a given period. The primary identifier is the system-generated RESIDENT_DETAILS_ID. The table's unique key, however, is a composite of business-oriented columns: PERSON_ID (linking to the student), RESIDENCY_CLASS_CD (a classification code), CAL_TYPE (calendar type), and SEQUENCE_NUMBER (calendar sequence). This design enforces that a student has only one residency record per classification per academic calendar instance. Other crucial columns include RESIDENCY_STATUS_ID and RESIDENCY_CLASS_ID, which are foreign keys to code lookup tables defining the specific statuses and classes of residency (e.g., "In-State," "Out-of-State," "International").

Common Use Cases and Queries

A primary use case is generating reports for tuition billing and financial aid office reviews to verify student residency eligibility. Another is during the admissions process, where residency data is captured and validated. Common queries involve joining with person and calendar tables to produce student lists. For example, to find all students with a specific residency class for the current academic term, a query might join IGS_PE_RES_DTLS_ALL with HZ_PARTIES and IGS_CA_INST_ALL. Auditing changes is also a key function, facilitated by the related history table (IGS_PE_RES_DTLS_H). A typical pattern is to retrieve the most current residency record for active students, which often requires filtering on calendar dates or the latest sequence number per person.

Related Objects

The table is integral to the Student System's data model, with several documented foreign key relationships:

  • HZ_PARTIES: The PERSON_ID column links to this Trading Community Architecture (TCA) table to retrieve the student's core person/party information.
  • IGS_CA_INST_ALL: The columns CAL_TYPE and SEQUENCE_NUMBER link to this table to associate the residency detail with a specific academic calendar instance (e.g., "SEMESTER 2024").
  • IGS_PE_CODE_CLASSES: This lookup table is referenced twice: via RESIDENCY_STATUS_ID and RESIDENCY_CLASS_ID, providing the valid values and descriptions for residency codes.
  • IGS_PE_RES_DTLS_H: This history table tracks changes to records in IGS_PE_RES_DTLS_ALL, using the composite key of PERSON_ID and RESIDENCY_CLASS_CD to maintain an audit trail.
These relationships ensure data integrity and enable comprehensive reporting across the student lifecycle.