Search Results igs_gr_crmn_note_all_n2

Overview

IGS.IGS_GR_CRMN_NOTE_ALL is a transactional table within the Oracle EBS Student System (IGS) schema that describes the mappings of notes to graduation ceremonies. Each row associates a discrete note — identified by a reference number and classified by an institution-defined note type — with a specific graduation ceremony round. The table is registered in FND Design Data as IGS.IGS_GR_CRMN_NOTE_ALL and carries a status of VALID in the documented environment, indicating it is an active, supported object in both EBS 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the heuristic Data Vault classification of this object is satellite-leaning. The primary key, IGS_GR_CRMN_NOTE_PK (GRD_CAL_TYPE, GRD_CI_SEQUENCE_NUMBER, CEREMONY_NUMBER, REFERENCE_NUMBER), combines descriptive business attributes with an operating unit context rather than a single generated surrogate identifier, which is characteristic of a satellite attached to a parent ceremony hub. The foreign key relationship to IGS_GR_CRMN_ALL reinforces this reading, positioning IGS_GR_CRMN_NOTE_ALL as a dependent detail structure rather than an independent entity hub.

Key Information Stored

The table contains eleven documented columns. The most significant fall into two groups: ceremony identification and note identification.

• GRD_CAL_TYPE (VARCHAR2, 10) — the graduation calendar type the ceremony round belongs to; part of the primary key.
• GRD_CI_SEQUENCE_NUMBER (NUMBER) — the calendar instance of the graduation calendar for that ceremony round; part of the primary key.
• CEREMONY_NUMBER (NUMBER) — uniquely identifies a graduation ceremony; part of the primary key.
• REFERENCE_NUMBER (NUMBER) — the reference number of a particular note; part of the primary key and also indexed individually.
• GRD_NOTE_TYPE (VARCHAR2, 10) — an institution-defined note type relating to a graduation ceremony. This is the column most commonly searched under the term "grd_note_type" and is a frequent filter for note categorization. It is covered by the non-unique index IGS_GR_CRMN_NOTE_ALL_N2.
• ORG_ID (NUMBER, 15) — the operating unit identifier, enabling multi-org data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns providing audit lineage for each row.

The unique index IGS_GR_CRMN_NOTE_ALL_U1 (GRD_CAL_TYPE, GRD_CI_SEQUENCE_NUMBER, CEREMONY_NUMBER, REFERENCE_NUMBER) mirrors the primary key and serves as the strongest business-key candidate. A second non-unique index, IGS_GR_CRMN_NOTE_ALL_N3, supports lookups by REFERENCE_NUMBER alone. The primary key itself is a composite natural key rather than a generated surrogate.

Common Use Cases and Queries

Typical use cases involve reporting all notes attached to a ceremony round, filtering by note type, and auditing note population across operating units. A common pattern joins to the parent ceremony table to resolve ceremony descriptions:

• Retrieve all notes for a given ceremony: SELECT * FROM IGS.IGS_GR_CRMN_NOTE_ALL WHERE GRD_CAL_TYPE = :cal_type AND GRD_CI_SEQUENCE_NUMBER = :seq AND CEREMONY_NUMBER = :ceremony;
• Filter by note type: WHERE GRD_NOTE_TYPE = :note_type (index N2).
• Look up a specific note by reference number (index N3).
• Exclude standard Who columns in student-facing extracts; include ORG_ID in any multi-org report to satisfy operating unit security.

Because the table is satellite-leaning and stores only mappings, queries should avoid treating it as a source of ceremony attributes; those reside in the parent IGS_GR_CRMN_ALL structure.

Related Objects

The most significant relationships documented are:

• IGS.IGS_GR_CRMN_ALL — the parent ceremony table; IGS_GR_CRMN_NOTE_ALL.GRD_CAL_TYPE references IGS_GR_CRMN_ALL. Join on the graduation calendar type and related ceremony keys.
• APPS.IGS_GR_CRMN_NOTE_ALL — the APPS synonym/view layer through which application code and reports normally access the table.
• Reference number lookups and note-type validation — GRD_NOTE_TYPE is institution-defined; validation typically resolves through the graduation note type reference data maintained in IGS lookup/validation objects.
• ORG_ID / operating unit — joins to HR operating unit and organization structures for multi-org reporting.

The object references no further database objects beyond its listed foreign key, confirming its role as a leaf-level detail satellite within the graduation ceremony model.