Search Results pe_int_perm_res

Overview

APPS.IGS_PE_EIT_PERM_RES_V is a reporting view in the Oracle E-Business Suite, delivered as part of the Student System (IGS) product family. It exposes a filtered, decoded projection of the IGS_PE_EIT extra-information table restricted to a single information type: permanent residency records identified by the discriminator value PE_INT_PERM_RES. The user search term "pe_int_perm_res" corresponds directly to that INFORMATION_TYPE literal embedded in the view's WHERE clause, confirming that this view is the intended access point for permanent-residency data held in the generic person extra-information framework.

The view's role is to present person-level permanent-residency attributes in a denormalized, human-readable form suitable for reporting, extracts, and downstream integration. Rather than requiring callers to know the underlying positional extra-information columns (PEI_INFORMATION1 through PEI_INFORMATIONn), the view renames and joins them, and it resolves the country code into a descriptive territory name. It is a read-only construct and carries no documented base table ownership of its own; all data resides in the referenced base objects.

Underlying Base Objects

The documented view text defines the object over two sources:

• IGS_PE_EIT — the core person extra-information table that stores arbitrary, user-defined attributes keyed by person and information type. Incremental extra-information slots are exposed as PEI_INFORMATION1..n columns.
• FND_TERRITORIES_VL — the multilingual territory (country) validation view, joined on TERRITORY_CODE to translate the stored territory code into its short name.

The join predicate is T.PEI_INFORMATION1 = TER.TERRITORY_CODE, combined with the filter T.INFORMATION_TYPE = 'PE_INT_PERM_RES'. The ETRM metadata for 12.2.2 records no separately documented referenced base objects beyond this view text, so the relationship is a straightforward inner join between the extra-information table and the territories validation view. Because it is an inner join, rows whose PEI_INFORMATION1 value does not match a valid, translated territory code are excluded from the result set.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_PE_EIT row, provided for uniquely identifying source records.
• PE_EIT_ID — primary identifier of the extra-information record.
• PERSON_ID — the person to whom the permanent-residency information belongs; the primary linkage key for joining to person and student records.
• INFORMATION_TYPE — always PE_INT_PERM_RES in this view, identifying the record category.
• PERM_RES_CNTRY — the permanent-residency country, sourced from PEI_INFORMATION1 and holding the territory code.
• MEANING — the translated territory short name from FND_TERRITORIES_VL, giving the readable country description.
• DOCUMENT_NUM — sourced from PEI_INFORMATION2, typically the residency or supporting document reference.
• START_DATE / END_DATE — the effective period of the residency record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns describing record creation and maintenance.

Common Use Cases and Queries

The view is typically used to report permanent-residency status for a person or cohort, to feed downstream residency determinations, and to produce extracts requiring country descriptions rather than raw codes. A representative query follows:

• Current residency by 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 AND (end_date IS NULL OR end_date >= SYSDATE);
• Residency by country across a population: SELECT meaning, COUNT(*) FROM APPS.IGS_PE_EIT_PERM_RES_V GROUP BY meaning ORDER BY 2 DESC;
• Records missing a document reference: SELECT person_id, meaning, start_date FROM APPS.IGS_PE_EIT_PERM_RES_V WHERE document_num IS NULL;
• Effective-dated listing: filter on START_DATE and END_DATE to isolate residency records active at a point in time.

Because the view is read-only and derived, it should be queried rather than modified directly; maintenance of permanent-residency data is performed against IGS_PE_EIT through the appropriate Student System maintenance functions.