Results for “igs_pe_person_v”

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

Overview

IGS_PE_PERSON_V is a reporting view within the Oracle E-Business Suite IGS (Student System) product family. In the ETRM 12.2.2 documentation the object is listed as belonging to the IGS - Student System module, which is flagged as Obsolete, and the implementation metadata records the view as "Not implemented in this database." This means that while the view definition exists in the ETRM repository as a reference artifact, it is not deployed in the instance against which the metadata was captured. Practically, the view serves as a consolidated person-centric projection that joins core party/person records (the HZ/PER-style person foundation) with IGS-specific student, staff, and encumbrance indicators. It presents a single denormalized row per person, exposing identity, name components, demographic attributes, and status flags (student, staff, encumbered, deceased) so that downstream reports, concurrent programs, or integration interfaces can resolve an IGS person without repeatedly invoking the underlying IGS generator functions.

Underlying Base Objects

The ETRM documentation for this object records no explicit referenced base objects, so the lineage must be inferred from the view text. The primary source alias is P, which supplies the party/person identity and name columns (PARTY_ID, PARTY_NUMBER, PARTY_NAME, PERSON_LAST_NAME, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_TITLE, KNOWN_AS, EMAIL_ADDRESS, SALUTATION, VALIDATED_FLAG, and audit columns). A second person alias PP contributes FULL_NAME, GENDER, DATE_OF_BIRTH, and DATE_OF_DEATH, and supports the derived DECEASED_IND. A personal-details alias PD contributes proof-of-insurance, proof-of-immunization, level-of-qualification, military service, veteran, archive, purge, and fund-authorization attributes. Lookup aliases L1, L2, and L3 resolve meanings for sex, pre-name adjunct, and veteran respectively, and PIT supplies person identifier type and API person ID. Because the SELECT also invokes IGS_EN_GEN_007.ENRP_GET_STUDENT_IND, IGS_EN_GEN_003.ENRP_GET_ENCMBRD_IND, and IGS_EN_GEN_003.GET_STAFF_IND, the view depends on IGS enrollment and general PL/SQL generator packages in addition to the SQL base objects.

Key Columns

• PERSON_ID / PERSON_NUMBER: party identifier and formatted party number used as the person key.
• PERSON_NAME / FULL_NAME / TITLE_NAME: display forms of the person's name, including a title-prefixed variant.
• SURNAME, GIVEN_NAMES, MIDDLE_NAME, SUFFIX, PRE_NAME_ADJUNCT, PRE_NAME_ADJUNCT_MEANING: decomposed name elements for letter generation and sorting.
• STUDENT_IND, STAFF_MEMBER_IND, ENCUMBERED_IND: derived flags resolved via IGS generator functions.
• SEX, SEX_MEANING, BIRTH_DT, DECEASED_IND, DECEASED_DATE: demographic and life-status attributes.
• PREFERRED_NAME, PREFERRED_GIVEN_NAME, INITIAL_NAME, INITIAL_LAST_NAME: preferred and initial-form name derivatives.
• EMAIL_ADDR, SALUTATION, PROOF_OF_INS, PROOF_OF_IMMU, LEVEL_OF_QUAL_ID, MILITARY_SERVICE_REG, VETERAN, VETERAN_MEANING: contact and student-specific detail attributes.
• ARCHIVE_EXCLUSION_IND, ARCHIVE_DT, PURGE_EXCLUSION_IND, PURGE_DT: data-retention control columns.

Common Use Cases and Queries

The view is typically used to enumerate IGS persons with their student/staff classification, to drive correspondence and letter generation using the name and salutation columns, and to feed integrations that require a single person row. A representative query follows.

SELECT person_id,
       person_number,
       full_name,
       student_ind,
       staff_member_ind,
       encumbered_ind,
       sex_meaning,
       birth_dt,
       deceased_ind
FROM   igs_pe_person_v
WHERE  student_ind = 'Y'
ORDER  BY surname, given_names;

Because the student, staff, and encumbrance indicators are computed by IGS_EN_GEN_007 and IGS_EN_GEN_003 functions, filtering on those columns can be expensive; restricting on party or name attributes first is advisable. Given the module's Obsolete status and the "Not implemented in this database" note, scripts referencing IGS_PE_PERSON_V should be validated against the target instance before use in 12.1.1 or 12.2.2.