Search Results igs_pe_hz_parties

Overview

The IGS_PE_HZ_PARTIES table is a core data object within the Oracle E-Business Suite Student System (IGS), specifically designed to store and manage descriptive attributes for a person. Its primary role is to serve as the central person entity within the now-obsolete IGS module, linking individual person records to the broader Oracle Trading Community Architecture (TCA) framework via the HZ_PARTIES table. This integration indicates a design where student and person data was intended to be synchronized with the master party model used across other EBS applications. The ETRM metadata explicitly notes this table as "Not implemented in this database," suggesting it may have been a planned component in certain deployments or its functionality was superseded or consolidated elsewhere in later releases of EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on the unique identification of a person and their associated institutional context. The primary key, PARTY_ID, is the critical foreign key column linking directly to the foundational HZ_PARTIES table, ensuring a single source of truth for party information. A second unique key, OSS_ORG_UNIT_CD, suggests the table was designed to categorize persons within specific organizational units. Additional important foreign keys, such as INST_PRIORITY_CODE_ID and SEC_SCHOOL_LOCATION_ID, point to the storage of contextual attributes like institutional priority codes and secondary school location references, which are typical for student administration systems. These columns indicate the table's purpose in extending the generic HZ_PARTIES record with student-specific attributes.

Common Use Cases and Queries

In a functional implementation, this table would be central to person-centric queries and reporting within the Student System. Common operational use cases would include retrieving a comprehensive student profile, validating person-organization relationships, and supporting processes for admissions, enrollment, and academic advising. A typical query pattern would join this table to HZ_PARTIES and related code tables to build a complete person view. For example, a basic retrieval of student details might follow this pattern:

• SELECT hp.party_name, iphp.oss_org_unit_cd, iphp.inst_priority_code_id FROM igs_pe_hz_parties iphp, hz_parties hp WHERE iphp.party_id = hp.party_id AND hp.party_type = 'PERSON';

Reporting use cases would leverage its relationships to track faculty assignments, supervisor linkages, and person-specific attribute values stored in dependent tables.

Related Objects

The IGS_PE_HZ_PARTIES table has defined relationships with several key objects, as documented in its foreign key constraints. It is a parent table to multiple entities in the student system, including IGS_PE_ACAD_INTENTS (Academic Intentions), IGS_EN_SPLACE_FACS (Faculty for Enrollment), IGS_EN_SPLACE_SUPS (Supervisors for Enrollment), IGS_SC_PER_ATTR_VALS (Person Attribute Values), and IGS_SV_BTCH_SUMMARY (Service Batch Summary). Crucially, it is a child table to the central HZ_PARTIES table from the TCA model and references code classes via IGS_AD_CODE_CLASSES. This web of relationships underscores its intended position as a pivotal hub between the universal TCA party model and the specialized operational tables of the Student System.