Search Results aborig_torres_cd




Overview
Explore in AI Chat

Overview

The IGS_PE_ABORG_TORESCD table is a core reference data table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Oracle's Higher Education product) module. It functions as a user-defined lookup table that standardizes and stores codes for identifying individuals of Australian Aboriginal or Torres Strait Islander descent. Its primary role is to provide a validated list of codes for consistent data entry and reporting, directly supporting compliance with governmental reporting requirements, such as those mandated by DETYA (Department of Education, Training and Youth Affairs) element 316. The table's status as VALID and its storage in the APPS_TS_SEED tablespace confirm its active role in the application's data architecture.

Key Information Stored

The table's structure is designed to manage both the code values and their associated metadata. The most critical columns include:

  • ABORIG_TORRES_CD (VARCHAR2(10), Primary Key): The unique user-defined identifier for a specific classification.
  • GOVT_ABORIG_TORRES_CD (NUMBER): A numeric mapping to a standardized government code (e.g., 1 for descent, 2 for not of descent, 9 for no information), enforced via a foreign key to the IGS_PE_GOV_ABRGRESCD table.
  • DESCRIPTION (VARCHAR2(60)): A clear explanation of the code's meaning.
  • CLOSED_IND (VARCHAR2(1)): A flag indicating whether the code is active or has been disabled for future selection.
  • NOTES (VARCHAR2(2000)): A free-text field for administrative notes.
  • Standard WHO Columns (CREATED_BY, CREATION_DATE, etc.): Audit columns tracking record creation and modification.

Common Use Cases and Queries

This table is central to student demographic data management and statutory reporting. A primary use case is populating dropdown lists in application forms where a user must select a student's indigenous status. For reporting, it is joined to student data tables to generate demographic summaries for internal analysis or government compliance. Common SQL patterns include querying active codes for a lookup or joining to student statistics.

Sample Query: Retrieve all active codes with their government mapping:
SELECT atc.aborig_torres_cd, atc.govt_aborig_torres_cd, atc.description FROM igs.igs_pe_aborg_torescd atc WHERE atc.closed_ind IS NULL OR atc.closed_ind != 'Y' ORDER BY atc.aborig_torres_cd;

Sample Query: Join to student data for a report:
SELECT s.student_id, atc.description FROM igs.igs_pe_statistics s JOIN igs.igs_pe_aborg_torescd atc ON s.aborig_torres_cd = atc.aborig_torres_cd WHERE atc.closed_ind IS NULL;

Related Objects

The table's integrity is maintained through defined key relationships within the IGS schema. The documented dependencies are:

  • Primary Key: IGS_PE_ABORG_TORESCD_PK on the ABORIG_TORRES_CD column.
  • Referenced Foreign Key: The GOVT_ABORIG_TORRES_CD column references the IGS_PE_GOV_ABRGRESCD table, ensuring code mappings align with a master government standard list.
  • Referencing Foreign Key: The ABORIG_TORRES_CD column is referenced by the IGS_PE_STATISTICS table. This is the most critical relationship, as it links the code definition to the actual student demographic data stored in the statistics table.