Search Results race_cd




Overview
Explore in AI Chat

Overview

The IGS_PE_RACE table is a core data structure within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Student Management (formerly Oracle Campus Solutions) product family under the IGS (iGrants) schema. Its primary function is to store the race or ethnic classification information associated with a person, such as a student, faculty member, or staff. This table supports critical compliance reporting, demographic analysis, and diversity tracking mandated by educational and governmental institutions. It operates as a child table, linking race data to a specific person identifier, thereby enabling a person to have multiple race records if applicable.

Key Information Stored

The table's structure is concise, focusing on the essential link between a person and their race classification, along with standard audit columns. The key columns are:

  • PERSON_ID (NUMBER): The mandatory foreign key that uniquely identifies the individual in the person master table (e.g., IGS_PE_PERSON). This is part of the table's primary key.
  • RACE_CD (VARCHAR2(30)): The mandatory code representing the specific race or ethnic classification. This column is the other component of the primary key, allowing multiple race codes per person. Its values are typically validated by a lookup or value set within the application.
  • Standard WHO Columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These columns are ubiquitous in EBS and provide crucial audit trails for data creation and modification.

Common Use Cases and Queries

This table is central to generating demographic reports and ensuring regulatory compliance. A common operational use case is assigning or updating a person's race information via the application's person management interface, which performs underlying INSERT or UPDATE operations on this table. For reporting, analysts frequently join this table with the core person table and other demographic tables.

A fundamental query to retrieve all race information for a specific person would be:
SELECT race_cd, creation_date FROM igs.igs_pe_race WHERE person_id = :person_id ORDER BY race_cd;

For comprehensive demographic analysis, a join with the person base table is typical:
SELECT p.last_name, p.first_name, r.race_cd FROM igs.igs_pe_person p, igs.igs_pe_race r WHERE p.person_id = r.person_id;

Related Objects

Based on the provided metadata, the IGS_PE_RACE table has a defined dependency relationship. The table itself does not reference other objects, but it is referenced by an object in the APPS schema named IGS_PE_RACE. This APPS schema object is likely a public synonym or a view that provides a global access point to the underlying IGS table, a standard EBS architecture practice for encapsulation and security. The table's primary key index, IGS_PE_RACE_PK on (PERSON_ID, RACE_CD), enforces data integrity. The most significant related object, implied by the PERSON_ID foreign key, is the core person master table, IGS_PE_PERSON, which stores the primary biographical details for each PERSON_ID.