Results for “igs_pe_code_classes”

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

Overview

IGS_PE_CODE_CLASSES is a reference (lookup) table in the Oracle E-Business Suite Student System (IGS) product family, owned by the IGS schema. It describes the various code classes used throughout the student information model, providing a single controlled vocabulary of classification codes that other IGS entities reference for attributes such as religion, residency, military service, health insurance, and disability characteristics. Because it holds the definitive set of valid classification codes, it functions as an authoritative source of values rather than as a transactional record.

From a Data Vault modeling perspective, the metadata's heuristic classification places this table as hub-leaning. It carries a single-part surrogate primary key (CODE_CLASSES_ID) and is referenced by numerous descriptive attributes in downstream tables, which is characteristic of a hub or reference entity. Analysts designing a warehouse layer may therefore treat IGS_PE_CODE_CLASSES as a hub with its descriptive columns modeled as a satellite, or as a static reference/dimension table depending on reporting requirements.

Key Information Stored

The table contains ten documented columns, with the following being the most significant for query and integration purposes:

• CODE_CLASSES_ID — The surrogate primary key, enforced by the unique index IGS_PE_CODE_CLASSES_PK and also by IGS_PE_CODE_CLASSES_U1. All foreign key relationships from dependent tables resolve to this column.
• CLASS — Identifies the code class or category into which a given value falls; this is the primary grouping attribute used to segregate codes by domain.
• CODE — The business-facing code value itself, used as the display and validation value in the student system.
• DESCRIPTION — The human-readable description of the code class or code value, typically surfaced in list of values (LOV) windows and reports.
• CLOSED_IND — Indicates whether the code class is active or closed for new assignments; closed values should generally be excluded from current LOV queries.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording insert and update provenance.

The unique index IGS_PE_CODE_CLASSES_U1 on CODE_CLASSES_ID reinforces the surrogate key; no separate multi-column business key is documented, so CODE_CLASSES_ID is the sole unique identifier exposed by the metadata.

Common Use Cases and Queries

Typical usage involves resolving a stored foreign key back to its meaningful description, or validating that a code is still open before use. For example, to translate a religion code stored on a recruitment record:

• Lookup resolution: SELECT c.CODE, c.DESCRIPTION FROM IGS.IGS_PE_CODE_CLASSES c, IGS.IGS_AD_RECRUITMENTS r WHERE r.RELIGION_ID = c.CODE_CLASSES_ID;
• Active value lists: SELECT CODE_CLASSES_ID, CODE, DESCRIPTION FROM IGS.IGS_PE_CODE_CLASSES WHERE CLOSED_IND = 'N' ORDER BY CODE;
• Class-based filtering: Restrict a query to a particular classification domain using the CLASS column to populate a validation LOV.
• Audit reporting: Query CREATED_BY and LAST_UPDATE_DATE to track when reference codes were introduced or amended.

Because it is a shared reference table, it is frequently joined in reporting extracts and ETL loads across the student system to denormalize coded attributes into readable form.

Related Objects

The table is referenced through foreign keys by a range of IGS entities, confirming its role as a shared reference source. The most significant dependent tables and their join columns are:

• IGS_AD_RECRUITMENTS via RELIGION_ID.
• IGS_PE_RES_DTLS_ALL via RESIDENCY_STATUS_ID and RESIDENCY_CLASS_ID.
• IGS_PE_MIL_SERVICES_ALL via MILITARY_TYPE_ID, SEPARATION_TYPE_ID, ASSISTANCE_STATUS_ID, and ASSISTANCE_TYPE_ID.
• IGS_PE_PERS_DISABLTY via SPECIAL_ALLOW_ID, SUPPORT_LEVEL_ID, and SPECIAL_SERVICE_ID.
• IGS_PE_HLTH_INS_ALL via INSURANCE_ID.
• IGS_PE_TEACH_PERIODS_ALL via TEACH_PERIOD_RESID_STAT_ID.
• IGS_PE_SN_SERVICE via SPECIAL_SERVICE_CODE.
• IGS_FI_FEE_AS_RATE via RESIDENCY_STATUS_ID.

These relationships reinforce the hub-leaning classification: a single surrogate key is consumed by many descriptive attributes across the personal, recruitment, financial, and service domains of the Student System.