Results for “veteran_meaning”

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

Overview

IGS_PE_PERSON_SV is a secured database view owned by the APPS schema within the IGS — Student System product of Oracle E-Business Suite. In release 12.1.1 and 12.2.2, this view presents person-level biographical, demographic, and enrollment-related attributes consolidated from the underlying person and person-detail entities. Its purpose, as documented in the ETRM metadata, is to expose and manipulate secured information about persons stored in the database, giving downstream forms, reports, concurrent programs, and integration interfaces a single, filtered access path to party records without requiring each consumer to reconstruct the multi-table joins and the security predicates themselves.

The name suffix "_SV" conventionally denotes a security view. This indicates that row-level access is governed by Oracle EBS security policies, and that the view is intended to be queried rather than directly maintained by ad hoc SQL. The view is documented as VALID in the ETRM repository, confirming that it is a compiled, deployable object in the IGS schema family.

Underlying Base Objects

The ETRM metadata for this object lists no explicitly documented base tables, though the view text in the documentation excerpt shows that it is defined over at least the HZ_PARTIES family of tables (aliased as P for party attributes), a person-detail table (aliased as PD, contributing PROOF_OF_INS, PROOF_OF_IMMU, LEVEL_OF_QUAL, MILITARY_SERVICE_REG, VETERAN, and the archive and purge indicators), and a person profile table (aliased as PP, supplying PERSON_NAME, GENDER, DATE_OF_DEATH, and DATE_OF_BIRTH). Lookup views L1, L2, and L3 resolve the SEX, PRE_NAME_ADJUNCT, and VETERAN codes to their descriptive MEANING values, and a PERSON_ID_TYPE table (PIT) supplies PERSON_ID_TYPE and API_PERSON_ID.

Three database functions are invoked inline to derive additional attributes: IGS_EN_GEN_007.ENRP_GET_STUDENT_IND to flag student status, IGS_EN_GEN_003.ENRP_GET_ENCMBRD_IND to flag encumbered persons, and IGS_EN_GEN_003.GET_STAFF_IND to flag staff members. Because these are called for every row retrieved, the view can be relatively expensive on large people populations, and its performance profile depends heavily on effective indexing of the party key.

Key Columns

• PERSON_ID, PERSON_NUMBER, PERSON_NAME, PARTY_TYPE — the primary identifying attributes of the party record, derived from the party table.
• STUDENT_IND, ENCUMBERED_IND, STAFF_MEMBER_IND — computed indicators exposing enrollment, encumbrance, and staffing status.
• SURNAME, GIVEN_NAMES, MIDDLE_NAME, SUFFIX, PRE_NAME_ADJUNCT, PRE_NAME_ADJUNCT_MEANING, TITLE, TITLE_NAME, CONTEXT_BLOCK_NAME, PREFERRED_NAME, PREFERRED_GIVEN_NAME — the full name and form-of-address set, including the lookup meaning for the pre-name adjunct.
• VETERAN, VETERAN_MEANING — the military veteran indicator and its decoded description; the latter is the column most directly relevant to queries searching on "veteran_meaning."
• MILITARY_SERVICE_REG — the military service registration attribute accompanying the veteran flag.
• DECEASED_IND, DECEASED_DATE, BIRTH_DT, SEX, SEX_MEANING — vital-status and demographic columns.
• EMAIL_ADDR, SALUTATION, PROOF_OF_INS, PROOF_OF_IMMU, LEVEL_OF_QUAL_ID — contact and qualification attributes.
• ARCHIVE_EXCLUSION_IND, ARCHIVE_DT, PURGE_EXCLUSION_IND, PURGE_DT — data-retention control flags.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical usage includes student biographical reports, veteran-status extracts for regulatory or benefits reporting, and integration feeds that require a consolidated person record with security applied. A representative query lists persons flagged as veterans with the decoded meaning:

SELECT person_id, person_number, full_name, veteran, veteran_meaning FROM apps.igs_pe_person_sv WHERE veteran = 'Y';

Reports requiring the preferred name and contact block can select PREFERRED_NAME, TITLE_NAME, EMAIL_ADDR, and CONTEXT_BLOCK_NAME, while retention utilities can filter on ARCHIVE_EXCLUSION_IND and PURGE_EXCLUSION_IND. Because the view performs function calls and lookup joins per row, queries should constrain on indexed columns such as PERSON_ID or PERSON_NUMBER rather than scanning the full person population.