Search Results igs_gr_aprv_stat_pk

Overview

IGS_GR_APRV_STAT is a reference (lookup) table within the Oracle Student System (IGS) module, historically delivered as part of the Oracle E-Business Suite higher-education product family used with releases such as 12.1.1 and 12.2.2. The table stores the valid values that describe the approval status assigned to a graduand — that is, a student who has applied or been deemed eligible to graduate — as that record moves through the graduation approval workflow. Each row represents one discrete status code that can be assigned to a graduand approval record, along with its operational description and additional descriptive attributes.

The ETRM documentation formally classifies IGS as an Obsolete product area, and the implementation notes record that the object is not implemented in this database. This indicates the table exists as part of the historical IGS data model and documentation set, but is not deployed in the current environment instance referenced by the metadata. Practitioners encountering the object should treat it as legacy student-system schema rather than as an active configuration table in a standard EBS 12.1.1 / 12.2.2 installation.

From a heuristic Data Vault modeling perspective, IGS_GR_APRV_STAT is best classified as a satellite-style reference/lookup object rather than a hub or link. There is no FK/PK relationship data connecting it to other tables (the mined classification is "standalone"), meaning it functions as a self-contained code-and-description list that other graduand records may reference by value rather than through a documented foreign key.

Key Information Stored

The documented physical schema (ETRM 12.1.1) assigns the table to owner IGS with nine columns. The most significant include:

• GRADUAND_APPR_STATUS — the business key: the actual status code or short identifier representing a graduand approval state. This column is both the primary key (via IGS_GR_APRV_STAT_PK) and the sole unique-index candidate (IGS_GR_APRV_STAT_U1), confirming it as the natural business identifier.
• DESCRIPTION — the human-readable description of the status, used for display in forms and reports.
• S_GRUADAND_APPR_STATUS — the translated (language-specific) value of the status, following the IGS convention of prefixed translation columns (note the documented spelling "S_GRUADAND_APPR_STATUS").
• CLOSED_IND — a flag indicating whether the status represents a terminal or closed state in the approval lifecycle.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO (audit) columns tracking row creation and modification. Note the absence of an ORIG_SYSTEM/SYSTEM_ID pair, consistent with the standalone classification.

The surrogate primary key is thus represented by GRADUAND_APPR_STATUS, which equally serves as the business-key candidate — an uncommon but valid arrangement in legacy reference tables where the code itself is the identifier.

Common Use Cases and Queries

The principal use case is decoding status codes into readable labels during reporting, validation, and workflow analysis of graduand approval processes. A typical join would map a graduand approval record to this lookup on the status code:

SELECT a.graduand_id, s.graduand_appr_status, s.description FROM igs_gr_aprv_stat s, <graduand_approval_table> a WHERE a.graduand_appr_status = s.graduand_appr_status;

Reporting scenarios include: listing all available approval statuses for an LOV or picklist; identifying which statuses are terminal using CLOSED_IND; and validating that graduand records carry only values defined in this table. Because the object is documented as not implemented, any query against it must first be validated against the actual environment's data dictionary (for example, querying ALL_TABLES or DBA_TAB_COLUMNS for owner IGS). Where the table is absent, the analyst should fall back to the current graduation module's equivalent reference table.

Related Objects

The mined relationship model reports no foreign-key dependencies (standalone), so no confirmed join columns exist in the metadata. Conceptually, the objects most likely to depend on this lookup are the graduand approval and graduation processing entities within the IGS graduand schema, such as the table holding individual graduand approval records (referencing GRADUAND_APPR_STATUS as a value), the corresponding base-table LOV form, and any concurrent program or report that renders graduation approval status. Other status-lookup siblings in the IGS graduation family (for example, graduation status, application status, and conferment status tables) are related by convention rather than by documented constrained relationship. Because the classification is standalone, the safest guidance is to treat IGS_GR_APRV_STAT as an independent reference set and to establish any join relationships only after inspecting the live schema's actual constraints.