Results for “igs_pe_race”

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

Overview

The IGS_PE_RACE table is a core component of the Oracle E-Business Suite (EBS) Student System (IGS) module, which supports the administrative functions of educational institutions, including admissions, student records, and person management. As described in the ETRM metadata, IGS_PE_RACE stores the race information of a person. Within the broader EBS architecture, this table serves as a dependent child of the person record maintained in the Trading Community Architecture (TCA) layer, specifically HZ_PARTIES. It captures one or more racial classifications associated with an individual, a common requirement for regulatory, demographic, and reporting purposes in higher-education environments.

From a Data Vault modeling perspective, the metadata provides a heuristic classification of satellite-leaning. This suggests that IGS_PE_RACE is best modeled as a satellite table attached to a person hub (HZ_PARTIES or its IGS equivalent). The table does not represent an independent business entity; instead, it holds descriptive, potentially multi-valued attributes about a person, which is characteristic of satellite behavior. This classification is presented as a modeling suggestion derived from the foreign key structure rather than a formally documented designation.

Key Information Stored

The table’s documented physical schema contains seven columns. The most significant columns are described below; audit columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are standard EBS “who columns” that track record creation and modification but are not central to the business meaning of the data.

• PERSON_ID — A foreign key referencing HZ_PARTIES. This identifies the individual (party) to whom the race record belongs. It forms one half of the composite primary key.
• RACE_CD — The race classification code assigned to the person. This code typically corresponds to a lookup value defined within the IGS lookup framework. It forms the second half of the composite primary key.

The primary key, IGS_PE_RACE_PK, is a composite business key comprising (PERSON_ID, RACE_CD). Because a person may be associated with more than one race, the composite key allows multiple rows per person while preventing duplicate race entries for the same individual. There is no separate surrogate primary key documented; the unique index IGS_PE_RACE_PK simultaneously serves as the business-key candidate and the enforced uniqueness constraint.

Common Use Cases and Queries

IGS_PE_RACE is commonly used in demographic reporting, regulatory compliance reporting, and admissions processing. Typical queries retrieve all races for a given person or identify persons within a specific racial category.

A representative query to list all races for a person:

• SELECT person_id, race_cd FROM igs.igs_pe_race WHERE person_id = :p_person_id;

A reporting query to count persons per race code:

• SELECT race_cd, COUNT(DISTINCT person_id) FROM igs.igs_pe_race GROUP BY race_cd;

Because RACE_CD is typically tied to an IGS lookup, joins to the lookup tables (for example, IGS_LOOKUPS or FND_LOOKUP_VALUES) are common to retrieve descriptive race names for reports. The table also supports integration with external reporting systems that require demographic breakdowns by race.

Related Objects

The most significant related object is HZ_PARTIES, referenced via the foreign key IGS_PE_RACE.PERSON_ID → HZ_PARTIES. Additional related objects include:

• HZ_PERSON_PROFILES — Often joined on PERSON_ID to retrieve additional biographical details.
• IGS_PE_PERSON — The IGS-specific person table that frequently joins on PERSON_ID.
• FND_LOOKUP_VALUES / IGS_LOOKUPS — Provide the descriptive meaning of RACE_CD.
• HZ_PARTIES — The parent entity for the person hub.

These relationships support the satellite-leaning model, where IGS_PE_RACE depends on the person entity and provides descriptive demographic attributes.