Search Results igs_gr_crmn_note_pk




Overview
Explore in AI Chat

Overview

The IGS_GR_CRMN_NOTE_ALL table is a core data entity within the Oracle E-Business Suite Student System (IGS) module, specifically for releases 12.1.1 and 12.2.2. It serves a critical administrative function by defining and storing the mappings between textual notes and specific graduation ceremonies. This table enables institutions to attach contextual information, instructions, or important announcements to individual ceremonies, ensuring that ceremony-specific details are properly recorded and can be referenced by other system processes and reports. Its role is to maintain the relationship between a ceremony and its associated notes, acting as a junction entity within the graduation management framework.

Key Information Stored

The table's structure is designed to uniquely identify a note-to-ceremony link through a composite primary key. The key columns are GRD_CAL_TYPE and GRD_CI_SEQUENCE_NUMBER, which together identify the graduation calendar period. The CEREMONY_NUMBER pinpoints the specific event within that period, and the REFERENCE_NUMBER identifies the particular note being attached. While the provided metadata does not list all columns, the foreign key relationships imply these columns are central. The table likely contains additional columns for controlling data such as creation date, last update date, and the ORG_ID for multi-org support, as indicated by the "_ALL" suffix in the table name.

Common Use Cases and Queries

This table is primarily accessed for administrative setup and reporting related to graduation events. A common use case is retrieving all notes configured for a specific upcoming ceremony to verify or publish correct information. System interfaces may query this table to pull notes for inclusion in printed ceremony programs or official communications. A typical reporting query would join to the ceremony master table (IGS_GR_CRMN_ALL) and a notes table (not explicitly named in the metadata) to produce a list. For example: SELECT note.text, crmn.ceremony_date FROM igs_gr_crmn_note_all crmn_note JOIN igs_gr_crmn_all crmn ON crmn_note.grd_cal_type = crmn.grd_cal_type AND crmn_note.grd_ci_sequence_number = crmn.grd_ci_sequence_number AND crmn_note.ceremony_number = crmn.ceremony_number WHERE crmn.grd_cal_type = 'MAIN_2024'; Data maintenance tasks involve inserting new mappings when a note is created for a ceremony or deleting them when information becomes obsolete.

Related Objects

The table has a direct and essential foreign key relationship with the graduation ceremony master table, IGS_GR_CRMN_ALL. This relationship enforces referential integrity, ensuring a note mapping cannot exist without a valid parent ceremony. The join is performed on three key columns that uniquely identify a ceremony:

  • IGS_GR_CRMN_NOTE_ALL.GRD_CAL_TYPE references IGS_GR_CRMN_ALL
  • IGS_GR_CRMN_NOTE_ALL.GRD_CI_SEQUENCE_NUMBER references IGS_GR_CRMN_ALL
  • IGS_GR_CRMN_NOTE_ALL.CEREMONY_NUMBER references IGS_GR_CRMN_ALL
The table is also referenced by its primary key constraint, IGS_GR_CRMN_NOTE_PK. It is logically related to the underlying notes table (which stores the actual note text referenced by REFERENCE_NUMBER), though this specific relationship is not detailed in the provided metadata. Program units and views within the Graduation subsystem will likely depend on this table to present consolidated ceremony information.