Search Results archive_exclusion_ind




Overview
Explore in AI Chat

Overview

IGS_PE_PERSON_LKUPV_V is a dictionary view owned by the APPS schema within the IGS (Student System) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates person-level biographical, demographic, identification, and data-retention attributes from the Oracle Trading Community Architecture (TCA) party model and the IGS person extensions into a single flattened record per party. Its primary role is to serve as a lookup and reporting source for student, staff, and contact records accessed by IGS forms, concurrent programs, and integration interfaces, allowing callers to resolve a party to a person number, name, gender, staff flag, deceased indicator, and lifecycle-management flags without joining the underlying TCA tables directly.

The view is catalogued with a status of VALID and returns exactly one current profile row per party for the genders sourced from HZ_PERSON_PROFILES, using date-effective filtering. Because it exposes the ARCHIVE_EXCLUSION_IND column, it is frequently used by data-retention, archiving, and purge programs to determine whether a person is exempt from archive or purge processing.

Underlying Base Objects

The view text joins four documented sources:

  • HZ_PARTIES (alias P) — the master party record; the driving table of the join.
  • IGS_PE_HZ_PARTIES (alias PD) — the IGS-specific party extension holding deceased, archive, and purge attributes. This table is outer-joined to HZ_PARTIES on PARTY_ID, so parties without an IGS extension row are still returned.
  • HZ_PERSON_PROFILES (alias PP) — date-effective person profile data, restricted to CONTENT_SOURCE_TYPE = 'USER_ENTERED' and rows where SYSDATE falls between the effective start and end dates. Unlike the IGS table, this join is a standard inner join, so a current user-entered profile is required for a row to appear.
  • FND_LOOKUP_VALUES (alias L1) — supplies the decoded gender meaning from the HZ_GENDER lookup type, outer-joined on LOOKUP_CODE with VIEW_APPLICATION_ID = 222, SECURITY_GROUP_ID = 0, and the language derived from USERENV('LANG').

The view also invokes the PL/SQL function IGS_EN_GEN_003.GET_STAFF_IND per row to derive the staff-member indicator.

Key Columns

Common Use Cases and Queries

The most frequent use is identifying persons eligible for or excluded from archive and purge routines. A retrieval of non-excluded persons resembles:

  • SELECT person_number, surname, given_names, archive_exclusion_ind, purge_exclusion_ind FROM igs_pe_person_lkupv_v WHERE archive_exclusion_ind = 'N';
  • Filtering deceased records: SELECT person_id, surname FROM igs_pe_person_lkupv_v WHERE deceased_ind = 'Y';
  • Locating staff members: SELECT person_number, surname, staff_member_ind FROM igs_pe_person_lkupv_v WHERE staff_member_ind = 'Y';
  • Joining to enrollment or registration tables on PERSON_ID to obtain demographics for reporting extracts.

Because the profile join is date-effective and inner, queries return only parties with a current user-entered profile. The staff indicator is computed at runtime via a function call, so performance-sensitive batch operations should account for per-row evaluation cost.