Search Results igs_gr_note_type_u1

Overview

IGS.IGS_GR_NOTE_TYPE is a reference (lookup) table in the Oracle E-Business Suite student system, owned by the IGS schema and registered in FND Design Data as IGS.IGS_GR_NOTE_TYPE. It describes the available graduation note types — that is, the institution-defined categories of free-text notes that staff may attach to a graduation ceremony record. Its functional home is the graduation ceremony maintenance flow, specifically the form GRDF2510, where the value of GRD_NOTE_TYPE drives how notes are classified and later retrieved for a ceremony.

The table is small, has no foreign keys to other database objects, and is exposed to the applications layer through the APPS synonym IGS_GR_NOTE_TYPE. From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone, which suggests it is best treated as a reference or hub-style entity: a stable, low-volume list of coded business concepts with no dependent link table required. It carries no descriptive child tables and no intersection semantics, so it functions purely as an enumerated set of valid note categories.

Storage is allocated in the APPS_TS_TX_DATA tablespace with PCTFREE 10, which is appropriate for a table that is almost entirely read-only after setup. The associated unique index resides in APPS_TS_TX_IDX.

Key Information Stored

The documented physical schema for the 12.1.1 reference environment contains seven columns. The most significant are:

• GRD_NOTE_TYPE (VARCHAR2(10), mandatory) — the institution-defined note type code relating to a graduation ceremony. This is the business key of the table and the column used in GRDF2510 when notes are created.
• DESCRIPTION (VARCHAR2(60)) — the human-readable meaning of the note type, displayed to users selecting a type during ceremony note entry.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS "Who" audit columns, recording row creation and last modification context. These are present for audit compliance and are not business-meaningful.

The primary key is defined as IGS_GR_NOTE_TYPE_PK on GRD_NOTE_TYPE. A separate unique index, IGS_GR_NOTE_TYPE_U1, is also defined on GRD_NOTE_TYPE over tablespace APPS_TS_TX_IDX and represents the documented business-key candidate. Because the primary key and the unique index cover the same single column, GRD_NOTE_TYPE is unambiguously the surrogate-free natural key of the entity; there is no separate system-generated identifier column in the documented column list.

Common Use Cases and Queries

The table is typically queried to populate selection lists, to validate incoming note-type values, and to join descriptive text onto graduation note transactions in reports. A direct extraction is straightforward:

• Lookup validation: SELECT GRD_NOTE_TYPE, DESCRIPTION FROM IGS.IGS_GR_NOTE_TYPE WHERE GRD_NOTE_TYPE = :code;
• List-of-values / picklist source: SELECT GRD_NOTE_TYPE, DESCRIPTION FROM IGS.IGS_GR_NOTE_TYPE ORDER BY GRD_NOTE_TYPE;
• Reporting join: drive ceremony note extracts through the APPS synonym and join on GRD_NOTE_TYPE to obtain readable text, filtering on LAST_UPDATE_DATE for incremental extracts.
• Setup verification: confirm that a required institution-defined note type exists before running graduation processing, avoiding validation failures in GRDF2510.

Because of the tiny row count, queries against this object carry negligible cost; the unique index on GRD_NOTE_TYPE supports exact-match lookups, while sequential scans are acceptable for full-list retrieval.

Related Objects

The documented dependency data states that IGS_GR_NOTE_TYPE does not reference any database object and is referenced only by the APPS synonym IGS_GR_NOTE_TYPE. Consequently, no formal foreign-key relationships are published in the ETRM metadata. Practically, the object participates in the following relationships:

• APPS.IGS_GR_NOTE_TYPE — the APPS-layer synonym through which application code and reports resolve the table.
• Graduation ceremony note transaction tables (for example, the graduation note records maintained through GRDF2510) — these carry GRD_NOTE_TYPE as a denormalized or foreign reference to this lookup.
• IGS_GR_NOTE_TYPE_PK and IGS_GR_NOTE_TYPE_U1 — the primary key constraint and unique index enforcing uniqueness of GRD_NOTE_TYPE.
• GRDF2510 — the Oracle Forms screen that consumes this table when notes are created against a ceremony.

Referential integrity for the consuming graduation tables is enforced at the application layer rather than through declared database constraints, which is consistent with the standalone classification reported in the metadata.