Search Results ins_sts

Overview

APPS.IGS_PE_PERSON_ID_TYP_V is a supplementary Oracle E-Business Suite view owned by the APPS schema. The ETRM metadata classifies its view type as a "supplementary view used to simplify forms coding," and includes Oracle's standard warning that querying or altering data through this view is not recommended because its definition may change dramatically in subsequent minor or major releases. This classification positions the view as a forms-support construct rather than a stable integration surface. In release 12.1.1 and 12.2.2 it exists to expose person identification type information, institution context, and related lookup values in a single flattened row shape usable by the Oracle Forms UI layer of the Student System (IGS) product family. Status is recorded as VALID, and the FND design data reference is IGS.IGS_PE_PERSON_ID_TYP_V.

Underlying Base Objects

The documented dependency list shows that APPS.IGS_PE_PERSON_ID_TYP_V references APPS.IGS_LOOKUP_VALUES, IGS_OR_INST_ORG_BASE_V, IGS_OR_INST_STAT, and IGS_PE_PERSON_ID_TYP. The core transactional entity is IGS_PE_PERSON_ID_TYP, which stores person identification type definitions. IGS_LOOKUP_VALUES supplies the decoded lookup meaning and related lookup metadata (LOOKUP_TYPE, MEANING) that the view exposes alongside the raw code. IGS_OR_INST_ORG_BASE_V contributes institution-level attributes such as institution code and name, while IGS_OR_INST_STAT provides institution status values including the paired status and its secondary (S_) form. The view is not referenced by any database object, confirming its role as a terminal presentation object consumed by forms rather than a building block for other views. The documented ETRM 12.2.2 metadata lists no additional referenced base objects beyond those above.

Key Columns

• ROW_ID (ROWID) — row identifier used by Forms for row-level operations.
• PERSON_ID_TYPE (VARCHAR2 10) and S_PERSON_ID_TYPE (VARCHAR2 30) — the person identification type code and its secondary/translated representation.
• DESCRIPTION (VARCHAR2 60) — description of the person ID type.
• PREFERRED_IND and UNIQUE_IND — flags indicating whether the ID type is preferred and whether values of that type must be unique.
• INSTITUTION_CD (VARCHAR2 30) and NAME (VARCHAR2 360) — institution code and institution name.
• INSTITUTION_STATUS (VARCHAR2 10) and S_INSTITUTION_STATUS (VARCHAR2 10) — institution status code and secondary status code.
• LOOKUP_TYPE (VARCHAR2 30) and MEANING (VARCHAR2 80) — decoded lookup context for the type.
• FORMAT_MASK (VARCHAR2 20) — input format mask applied to the identifier.
• REGION_IND (VARCHAR2) — Region Code Indicator, the column matching the user's search term.
• CLOSED_IND (VARCHAR2) — Closed Indicator.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The primary use case is Oracle Forms-driven maintenance of person identification type setup, where the view supplies pre-joined institution, status, lookup, and audit context so the form requires no hand-written join logic. Secondary use is ad hoc reporting on identification type configuration, particularly filtering by REGION_IND or CLOSED_IND. Because the view is flagged as non-recommended for direct querying, integrations should prefer the underlying base tables.

Representative query:

• SELECT PERSON_ID_TYPE, DESCRIPTION, INSTITUTION_CD, INSTITUTION_STATUS, REGION_IND, CLOSED_IND, FORMAT_MASK FROM APPS.IGS_PE_PERSON_ID_TYP_V WHERE NVL(CLOSED_IND,'N') = 'N' ORDER BY PERSON_ID_TYPE;
• SELECT PERSON_ID_TYPE, MEANING FROM APPS.IGS_PE_PERSON_ID_TYP_V WHERE REGION_IND = :region_code;

Consumers should treat the column list as potentially volatile across patch levels and validate against the deployed release before relying on REGION_IND or any other single column.