Results for “igs_ad_note_types”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_AD_NOTE_TYPES is a configuration table within the Oracle E-Business Suite IGS (Student System) product family. Its documented purpose is to hold setup details about note types — the categorical definitions that classify and control the free-text notes recorded against admissions and recruitment records. In the EBS 12.1.1 and 12.2.2 environments, the table is owned by the IGS schema and appears in the ETRM reference as part of the Student System module, which is flagged as obsolete in current documentation sets. The table is reported as "not implemented in this database" in the furnished metadata, meaning the described definition reflects a legacy or optional installation state rather than a guaranteed object in every environment.

From a dimensional modeling perspective, the mined foreign-key topology classifies IGS_AD_NOTE_TYPES as hub-leaning. This is a modeling suggestion rather than a physical assertion: the table supplies a stable, surrogate-keyed list of reference values that multiple dependent tables point to, which is the characteristic profile of a hub or reference entity in a Data Vault style model. Note-type definitions change infrequently relative to the transactional notes that consume them, reinforcing their treatment as slowly changing reference data.

Key Information Stored

The table's documented physical schema comprises ten columns. The primary key is defined by the constraint IGS_AD_NOTE_TYPES_PK on NOTES_TYPE_ID, a system-generated surrogate identifier that carries no business meaning and should be treated as the immutable row handle.

• NOTES_TYPE_ID — surrogate primary key; the value referenced by all dependent foreign keys.
• NOTES_CATEGORY — the higher-level grouping to which the note type belongs, allowing note types to be organized into functional families.
• NOTE_TYPE — the short code or name identifying the note type; the primary business-key candidate for user-facing identification.
• DESCRIPTION — the descriptive text explaining the intent and usage of the note type.
• CLOSED_IND — an active/inactive flag controlling whether the note type remains available for new note entry.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent modification and the login under which it occurred.

Because the documented metadata identifies only the surrogate primary key and does not publish a separate unique index, NOTE_TYPE combined with NOTES_CATEGORY is the practical business-key candidate for de-duplication and lookup logic.

Common Use Cases and Queries

Typical usage centers on validating note-type codes and driving dependent dropdowns. A standard extraction of active note types resembles:

SELECT notes_type_id, notes_category, note_type, description
FROM   igs_ad_note_types
WHERE  NVL(closed_ind,'N') = 'N';

Admissions reporting commonly joins the table to the transactional notes table to obtain readable type names alongside note text:

SELECT n.notes_type_id, t.note_type, n.note_text
FROM   igs_ad_appl_notes n, igs_ad_note_types t
WHERE  n.note_type_id = t.notes_type_id;

Setup auditing queries identify note types referenced by admissions application setup, typically by aggregating the multiple setup columns that point at this table to confirm which types are configured for the various application channels. Reconciliation reports compare the CODE values used in legacy extracts against the current note types to detect retired or renamed entries.

Related Objects

The documented referential relationships define the set of dependent objects that consume note-type identifiers. The most significant are:

• IGS_AD_APPL_NOTES — the transactional table storing individual notes; joined on IGS_AD_APPL_NOTES.NOTE_TYPE_ID = IGS_AD_NOTE_TYPES.NOTES_TYPE_ID.
• IGS_SS_ADMAPPL_SETUP — admissions application setup, which references this table three times through distinct columns: ACT_NOTE_TYPE_ID, PS_NOTE_TYPE_ID, and WE_NOTE_TYPE_ID, denoting the note types associated with specific application stages or channels.

Any query resolving note-type descriptions across admissions functions will therefore touch IGS_AD_APPL_NOTES and IGS_SS_ADMAPPL_SETUP, and implementations should account for the three separate join paths from the setup table when building reporting extracts.