Search Results igs_pe_typ_instances_all

Overview

The table IGS_PE_TYP_INSTANCES_ALL is a core data entity within the Oracle E-Business Suite Student System (IGS) module, used in both releases 12.1.1 and 12.2.2. It serves as a central junction table that manages the association between a person and the various specific person type classifications they can hold within the institution. Its primary role is to record and track the distinct instances where a person is assigned a particular type, such as an applicant, student, instructor, or alumni. This table enables the complex, multi-role relationships typical in higher education, where a single individual can interact with the institution in several capacities simultaneously or over time.

Key Information Stored

The table stores the unique instance of a person type assignment. While the full column list is not detailed in the provided metadata, the foreign key relationships indicate critical data points. The primary key is TYPE_INSTANCE_ID, which uniquely identifies each person type record. Essential foreign key columns include PERSON_ID, linking to the core party in HZ_PARTIES, and PERSON_TYPE_CODE, referencing the valid type definitions in IGS_PE_PERSON_TYPES. For person types related to academic programs, the table stores COURSE_CD and CC_VERSION_NUMBER, linking to IGS_PS_VER_ALL (Course Version). For applicant-specific instances, it holds ADMISSION_APPL_NUMBER, NOMINATED_COURSE_CD, and SEQUENCE_NUMBER to link to application data in IGS_AD_PS_APPL_INST_ALL.

Common Use Cases and Queries

This table is fundamental for reporting and processes that depend on a person's institutional roles. A common use case is generating a list of all current active students, which requires joining this table to the person and person type tables and filtering by the relevant PERSON_TYPE_CODE and status. Another critical scenario is during the admissions process, where the system creates a person type instance for an applicant, which may later be updated or end-dated upon enrollment, potentially with a new "student" type instance created. A typical query pattern involves selecting person details filtered by a specific type:

• SELECT p.party_name, t.person_type_code FROM hz_parties p, igs_pe_typ_instances_all t, igs_pe_person_types pt WHERE p.party_id = t.person_id AND t.person_type_code = pt.person_type_code AND pt.system_type = 'STUDENT' AND t.end_date IS NULL;

Data integrity and validation logic within forms and APIs also heavily rely on this table to enforce business rules about valid role combinations and transitions.

Related Objects

IGS_PE_TYP_INSTANCES_ALL maintains documented foreign key relationships with several key tables, as per the provided metadata:

• HZ_PARTIES: Links via PERSON_ID to the Trading Community Architecture (TCA) foundation, providing the core person/party record.
• IGS_PE_PERSON_TYPES: Links via PERSON_TYPE_CODE to the master definition of valid person types within the Student System.
• IGS_PS_VER_ALL: Links via COURSE_CD and CC_VERSION_NUMBER for person type instances associated with a specific course version (e.g., a student in a particular program).
• IGS_AD_PS_APPL_INST_ALL: Links via the composite key of PERSON_ID, ADMISSION_APPL_NUMBER, NOMINATED_COURSE_CD, and SEQUENCE_NUMBER for person type instances specifically tied to an admission application.

These relationships position this table as a critical hub connecting person identity, role definition, academic program information, and the admissions lifecycle.