Results for “igs_pe_person_id_type_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_PE_PERSON_ID_TYPE_V is a read-only database view owned by the APPS schema in the Oracle E-Business Suite environment (12.1.1 and 12.2.2). It belongs to the IGS product family, commonly referred to as the Oracle Student System, and specifically to the person and alternate identifier areas of that module. The view exposes the relationship between a person's preferred identifier type and the corresponding alternate person identifier records, providing a compact, filtered projection that reporting layers and integrations can consume without embedding the join and date-filter logic themselves.

Its practical role is that of a convenience view: it returns only the identifier rows whose type is flagged as preferred and whose validity window currently covers the system date. This makes it suitable for operational reporting, concurrent program queries, and inbound/outbound integration extracts where a single active identifier per person/type is expected.

Underlying Base Objects

The view is defined over two documented base tables:

• IGS_PE_PERSON_ID_TYP (aliased PIT) — the identifier type definition table, which holds each PERSON_ID_TYPE and a PREFERRED_IND flag.
• IGS_PE_ALT_PERS_ID (aliased API) — the alternate person identifier table, which stores the actual identifier values (API_PERSON_ID) linked to a person (PE_PERSON_ID), with START_DT and END_DT validity dates.

The join is performed on PERSON_ID_TYPE equality between the two tables. The view further restricts results with two predicates: PIT.PREFERRED_IND = 'Y', and SYSDATE BETWEEN API.START_DT AND NVL(API.END_DT, SYSDATE). The second predicate means an open-ended identifier (null END_DT) remains visible indefinitely, while expired identifiers are excluded. Note that the view does not enforce a one-row-per-person guarantee at the database level; where multiple rows satisfy the predicates, all are returned.

Key Columns

• PERSON_ID_TYPE — the identifier type code from IGS_PE_PERSON_ID_TYP; identifies the classification of the alternate person ID (for example, national ID, passport, or institution-specific identifier).
• API_PERSON_ID — the actual alternate person identifier value stored in IGS_PE_ALT_PERS_ID.
• PE_PERSON_ID — the internal person identifier linking the row back to the person record, typically used to join to person or party tables elsewhere in IGS.

Because only three columns are exposed, the view is deliberately narrow; all descriptive attributes of the identifier type must be obtained by joining back to IGS_PE_PERSON_ID_TYP.

Common Use Cases and Queries

Typical scenarios include producing a current preferred identifier listing for a person, validating that an identifier exists before an integration hand-off, and driving concurrent extracts that require active identifiers only. A straightforward query returns all preferred identifiers:

SELECT person_id_type, pe_person_id, api_person_id FROM apps.igs_pe_person_id_type_v;

To retrieve the preferred identifier for a specific person:

SELECT api_person_id FROM apps.igs_pe_person_id_type_v WHERE pe_person_id = :p_person_id AND person_id_type = :p_type;

To combine identifier values with their type descriptions:

SELECT v.pe_person_id, v.api_person_id, t.description FROM apps.igs_pe_person_id_type_v v, apps.igs_pe_person_id_typ t WHERE t.person_id_type = v.person_id_type;

Because the view already applies the preferred and date predicates, callers should avoid re-imposing PREFERRED_IND filters, which are not exposed as columns. Queries should be schema-qualified with APPS and run under an appropriate IGS responsibility to respect row-level security and grants.