Results for “igs_pe_person_types”

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

Overview

IGS.IGS_PE_PERSON_TYPES is a foundational reference (setup) table within the Oracle E-Business Suite Student System (IGS) module. It captures the distinct person types recognized by the institution, such as applicant, student, faculty, staff, or alumni. In Oracle EBS 12.1.1 and 12.2.2, the table serves as the central lookup that qualifies an individual's relationship to the institution and drives downstream processing logic across admissions, registration, and self-service functions. Per the ETRM metadata, the table is modified to capture the enrollment method type related to self service, meaning it participates in controlling how a person may enroll through web-based self-service channels in addition to its core classification role.

The primary key is constraint IGS_PE_PERSON_TYPES_PK, defined on the single column PERSON_TYPE_CODE. A unique index, IGS_PE_PERSON_TYPES_U1, also exists on PERSON_TYPE_CODE, confirming it as the business-key candidate that uniquely identifies each row. Based on the foreign-key relationship structure supplied in the metadata, the object is classified heuristically as hub-leaning in Data Vault modeling terms — that is, it behaves as a stable hub of unique person type business keys that multiple dependent tables reference. This classification is a modeling suggestion rather than a physical design fact.

The documented physical schema contains 10 columns under the IGS owner in the 12.1.1 ETRM data set.

Key Information Stored

The 10 documented columns capture the identity, descriptive, and audit attributes of each person type record:

• PERSON_TYPE_CODE — The primary key and unique business key. The enumerated identifier for each person type and the value propagated to all dependent tables.
• DESCRIPTION — The human-readable name or label presented to users for the person type.
• SYSTEM_TYPE — A system-level classification distinguishing seeded/system person types from institution-defined ones, governing how the record is treated by delivered logic.
• CLOSED_IND — A status flag indicating whether the person type is active or closed to new assignment.
• RANK — An ordering or precedence value used to sequence or prioritize person types in listings and selection logic.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle EBS WHO-column audit set recording creation and last modification context for each row.

The surrogate-vs-business-key distinction is relevant here: although PERSON_TYPE_CODE functions as both primary key and unique index (a characteristic of a natural-key hub), the audit columns provide the standard row-level traceability present in all EBS tables.

Common Use Cases and Queries

Because the table is a reference lookup, its most frequent use is as a joined dependency in reporting and as a validation source in data entry. Typical scenarios include:

• Listing all active person types for a setup or configuration screen: SELECT person_type_code, description FROM igs_pe_person_types WHERE closed_ind = 'N' ORDER BY rank;
• Resolving descriptive labels when reporting on person assignments by joining dependent tables back to this hub on PERSON_TYPE_CODE.
• Auditing recently modified setup records using LAST_UPDATE_DATE and LAST_UPDATED_BY to support change-control and reconciliation.
• Filtering by SYSTEM_TYPE where delivered versus institution-defined behavior must be distinguished.

Related Objects

The metadata identifies seven significant tables that reference IGS_PE_PERSON_TYPES through foreign keys, all joined on the person type column:

• IGS_PE_USR_ADISC_ALL — via PERSON_TYPE; user/advisor discipline associations.
• IGS_PE_USR_ARG_ALL — via PERSON_TYPE; user argument records.
• IGS_PE_USR_AVAL_ALL — via PERSON_TYPE; user availability records.
• IGS_PE_STUP_DATA_EMT_ALL — via PERSON_TYPE_CODE; student program data with enrollment method type, linking directly to the self-service enrollment modification noted in the description.
• IGS_PE_TYP_INSTANCES_ALL — via PERSON_TYPE_CODE; instances of person types.
• IGS_PE_PER_TYPE_MAP — via PERSON_TYPE_CODE; mapping between person types and related classification structures.

These dependencies underscore the table's role as a hub: any change to a PERSON_TYPE_CODE propagates across admissions, user-role, and enrollment-method processing within the Student System.