Search Results igs_gr_note_type_pk

Overview

IGS_GR_NOTE_TYPE is a reference (lookup) entity within the Oracle E-Business Suite IGS — Student System product family, specifically the Graduation (GR) sub-module. As documented in the ETRM 12.1.1 physical schema, the table describes the available graduation note types — categorical qualifiers attached to a student's graduation record (for example, distinctions, honors, exit remarks, or administrative annotations recorded at the point of graduation conferral). The entity functions as a validation list: graduation note records elsewhere in the schema reference a note type value defined here, ensuring consistent coding of graduation commentary.

An important qualification accompanies this object. The ETRM metadata records the implementation status as "Not implemented in this database," and the product is flagged as Obsolete. In Oracle EBS 12.1.1 and 12.2.2 installations this table is therefore not physically present in a standard delivered schema; it survives only as a documented artifact — an intended design that was never shipped or was retired. Consultants encountering the name are typically working from legacy specifications, data-migration source mappings, or upgrade gap analyses rather than from a live object. The table should be treated as a design-of-record reference, not as a queryable runtime entity.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. No incoming or outgoing relationships were mined, meaning the object sits outside the connected constraint graph. Were it modeled formally, the absence of link relationships and its role as a coded reference list suggest it would best be represented as a small reference hub (or a code-and-description satellite attached to such a hub), keyed by its business code.

Key Information Stored

The documented physical schema comprises seven columns. The most significant are:

• GRD_NOTE_TYPE — the business key. This is the sole unique-index candidate (via IGS_GR_NOTE_TYPE_U1) and is also the column named in the primary-key constraint IGS_GR_NOTE_TYPE_PK. It carries the abbreviated note-type code used to tag graduation records. In this schema the primary key is the business code itself rather than a system-generated surrogate.
• DESCRIPTION — the human-readable expansion of the note type, used in list-of-values presentation, reports, and form field prompts.
• CREATED_BY, CREATION_DATE — the standard Oracle EBS WHO audit columns recording the user and timestamp of initial row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the corresponding audit columns capturing the most recent modification, its author, and the login session under which it occurred.

Because both the unique index and the primary key resolve to GRD_NOTE_TYPE, there is no separate surrogate identifier to distinguish from the business-key candidate. The remaining six columns are descriptive or audit metadata.

Common Use Cases and Queries

The practical use cases are constrained by the object's non-implemented status. The most common activities are:

• Migration and data-load mapping. When moving legacy student data into IGS or a successor system, GRD_NOTE_TYPE supplies the code set into which source note values must be translated. A typical pattern is a lookup query against the source extraction to validate that all incoming codes resolve.
• Gap analysis during upgrades. In 12.1.1 to 12.2.2 upgrade assessments, the table appears on object-comparison reports with a "not implemented" disposition, confirming no DDL or data migration effort is required.
• Logical-model documentation. Because the table is documented but absent, it is cited in data dictionaries and entity-relationship diagrams for completeness.

A representative validation query, confirmed against the documented column list, is:

SELECT note_type.grd_note_type,
       note_type.description
  FROM igs_gr_note_type note_type
 WHERE note_type.grd_note_type = :p_note_type_code;

On a live environment this statement fails with ORA-00942 (table or view does not exist), which itself serves as a diagnostic confirming the metadata's implementation flag.

Related Objects

The mined relationship data reports no foreign-key dependencies in either direction, so no join columns to parent or child tables are documented for this entity. Candidate related objects in the wider IGS Graduation model — identified by naming convention rather than by documented constraints — include the graduation record entity (the graduation/degree-awarded table that would carry a GRD_NOTE_TYPE foreign key), the graduation status and graduation reason reference tables, the person/student core tables supplying CREATED_BY and LAST_UPDATED_BY references to FND_USER, and the standard IGS graduation inquiry forms and concurrent programs that would present note-type list-of-values. All such relationships remain unconfirmed in the ETRM metadata and should be verified against a live, implemented IGS schema before reliance.