Search Results pe_res_class

Overview

APPS.IGS_PE_RES_DTLS_V is a seeded Oracle E-Business Suite database view belonging to the Student System (IGS) product family, specifically the People/Person entity (PE) module. It exposes residency classification and residency status detail records held for persons (typically students or applicants) in the institution's records. The view joins the primary residency details table to Oracle lookup values that translate internal codes into user-readable descriptions, and it enriches each record with person number information and academic calendar instance dates. Because it presents decoded, denormalized data in a single queryable object, it functions as a reporting and integration surface rather than as a transactional store; consumers never insert into it. Institutions commonly expose it through BI Publisher reports, OBIEE/OTBI analyses, custom concurrent programs, and inbound/outbound interfaces that require residency data keyed to a person and calendar.

Underlying Base Objects

The documented view definition references four objects:

• IGS_PE_RES_DTLS — the primary detail table (aliased RD) holding one row per residency detail record, including RESIDENT_DETAILS_ID, person reference, codes, evaluation data, descriptive flexfields (ATTRIBUTE1–20), calendar and sequence keys, and audit columns.
• IGS_LOOKUP_VALUES (aliased CC1) — joined on RESIDENCY_CLASS_CD = LOOKUP_CODE with LOOKUP_TYPE = 'PE_RES_CLASS' to supply the residency class description. This is the join implied by the user search term "pe_res_class."
• IGS_LOOKUP_VALUES (aliased CC2) — a second instance joined on RESIDENCY_STATUS_CD = LOOKUP_CODE with LOOKUP_TYPE = 'PE_RES_STATUS' to supply the residency status description.
• IGS_PE_PERSON_BASE_V (aliased PE) — joined on PERSON_ID to expose the person number.
• IGS_CA_INST_ALL (aliased CI) — joined on CAL_TYPE and SEQUENCE_NUMBER to supply calendar instance start date, end date, and description.

Table aliases in the view text follow the standard naming: RD for details, CC1/CC2 for the two lookup joins, PE for person, and CI for calendar instance.

Key Columns

• ROW_ID, RESIDENT_DETAILS_ID, PERSON_ID, PERSON_NUMBER — row identifier, surrogate primary key, and person identification.
• RESIDENCY_CLASS / RESIDENCY_CLASS_DESC — the residency class code and its decoded meaning from lookup type PE_RES_CLASS.
• RESIDENCY_STATUS / RESIDENCY_STATUS_DESC — the residency status code and decoded meaning from lookup type PE_RES_STATUS.
• EVALUATION_DATE, EVALUATOR, COMMENTS — when and by whom the residency determination was evaluated, plus free-text notes.
• START_DT, END_DT, CAL_TYPE, SEQUENCE_NUMBER, CALENDAR_DESC — calendar instance context for the record.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–20 — descriptive flexfield content.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include listing all residency determinations for a student, reporting by residency class for tuition/fee purposes, and extracting decoded values for integration. A simple lookup by class code:

• SELECT person_number, residency_class_desc, residency_status_desc, evaluation_date FROM apps.igs_pe_res_dtls_v WHERE residency_class = 'IN_STATE';
• SELECT * FROM apps.igs_pe_res_dtls_v WHERE person_id = :p_person_id ORDER BY evaluation_date DESC;
• SELECT residency_class_desc, COUNT(*) FROM apps.igs_pe_res_dtls_v GROUP BY residency_class_desc;

Because the view resolves PE_RES_CLASS and PE_RES_STATUS into descriptions, it is preferred over querying IGS_PE_RES_DTLS directly whenever user-facing output is required.