Search Results igs_pe_eit_perm_res_v




Overview
Explore in AI Chat

Overview

The IGS_PE_EIT_PERM_RES_V view is a reporting and integration object in the Oracle E-Business Suite Student System (IGS) product family. Owned by the APPS schema, it exposes person-level permanent residency information that has been captured through the institution's Extra Information Types (EIT) mechanism on the HZ/TPerson entity. The name itself reflects its purpose: IGS (Student System), PE (Person), EIT (Extra Information Type), and PERM_RES (Permanent Residency).

Institutions use this view to surface permanent-residency attributes that are not held in standard person or student records, specifically a person's permanent residence country and the document number associated with that residency record. Because the residency data is stored as generic EIT information, this view provides the business-friendly translation and filtering required for downstream use — reporting, regulatory extracts, student financial aid processing, admissions workflows, and integrations with external residency or immigration systems.

The view is available in both Oracle EBS 12.1.1 and 12.2.2 against the same APPS-owned definition. Its status is VALID, indicating it is a compiled, queryable object in a supported environment.

Underlying Base Objects

Although the ETRM metadata references no explicitly documented base objects, the embedded view text identifies the objects used in the SQL definition:

  • IGS_PE_EIT — the primary table holding Extra Information Type rows for persons. This is where the permanent residency information type (PE_INT_PERM_RES) is stored, including PEI_INFORMATION1 and PEI_INFORMATION2 attribute values.
  • FND_TERRITORIES_VL — the standard Oracle territories lookup view, used here to translate the stored territory code into a human-readable territory short name.

The view performs an inner join between these two objects, driving T.INFORMATION_TYPE = 'PE_INT_PERM_RES'. The join predicate links T.PEI_INFORMATION1 (the permanent residence country code) to TER.TERRITORY_CODE from FND_TERRITORIES_VL. Consequently, only EIT records whose country value matches a valid territory definition are returned, and only for the permanent residence information type.

Key Columns

  • ROW_ID — the ROWID of the source row in IGS_PE_EIT, providing a stable physical identifier.
  • PE_EIT_ID — the primary key of the Extra Information Type record; useful for joins back to the base table.
  • PERSON_ID — the unique identifier of the person associated with the residency record; joins to the person/party model.
  • INFORMATION_TYPE — always PE_INT_PERM_RES in this view, identifying the EIT category.
  • PERM_RES_CNTRY — alias of PEI_INFORMATION1; the permanent residence territory/country code.
  • MEANING — the territory short name derived from FND_TERRITORIES_VL (though the column list designates this position as DESCRIPTION).
  • DOCUMENT_NUM — alias of PEI_INFORMATION2; the residency document reference, the columnmost relevant to the user's search term.
  • START_DATE / END_DATE — the effective dating of the residency record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical uses include generating residency verification letters, supporting tuition classification (in-state versus out-of-state or international residency), validating residency for financial aid, and exporting data to immigration or government systems.

Example: retrieve permanent residency details for a specific person.

  • SELECT person_id, perm_res_cntry, meaning, document_num, start_date, end_date FROM apps.igs_pe_eit_perm_res_v WHERE person_id = :p_person_id;

Example: locate a person by residency document number.

  • SELECT person_id, perm_res_cntry, document_num FROM apps.igs_pe_eit_perm_res_v WHERE UPPER(document_num) LIKE UPPER('%'||:p_doc_num||'%');

Example: count current residents by country.

  • SELECT perm_res_cntry, meaning, COUNT(*) FROM apps.igs_pe_eit_perm_res_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE) GROUP BY perm_res_cntry, meaning;