Results for “reference_number”

50+ results




Overview
Explore in AI Chat

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

Overview

IGS_GE_NOTE is a generic note repository table within the Oracle E-Business Suite Student System (IGS) product family. Although the IGS product line is documented as obsolete in current EBS releases, the table structure and its relationships remain relevant for institutions maintaining historical IGS data, for migrations to Oracle Student Cloud or PeopleSoft Campus Solutions, and for archival reporting on EBS 12.1.1 and 12.2.2 environments. The table functions as a centralized store for free-text and object-linking notes attached to many major student-system entities, including courses, units, persons, offers, and enrollment constructs. Notes may be plain text, or they may reference an OLE (Object Linking and Embedding) object such as a Word document or Excel spreadsheet stored externally.

Under a heuristic Data Vault classification derived from the foreign-key topology, IGS_GE_NOTE is hub-leaning. Its single-column primary key, REFERENCE_NUMBER, behaves like a hub business key, and the numerous dependent NOTE tables function as satellites carrying context-specific note associations. This classification is a modeling suggestion rather than a documented architectural fact.

Key Information Stored

The table is relatively narrow, with nine documented columns. The most significant include:

  • REFERENCE_NUMBER — the primary key (IGS_GE_NOTE_PK) and unique-index candidate (IGS_GE_NOTE_U1); it uniquely identifies each note record and is the column targeted by every foreign key relationship.
  • S_NOTE_FORMAT_TYPE — indicates the format or category of the note, distinguishing text notes from OLE-linked notes.
  • NOTE_TEXT — holds the actual textual content of the note when the note is a plain-text entry.
  • NOTE_OLE — stores the OLE object reference or binary pointer for notes that embed external documents such as Word or Excel files.
  • LAST_UPDATE_DATE, CREATION_DATE — standard audit timestamps for record lifecycle tracking.
  • CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO-column audit fields identifying the user and session responsible for the record.

The primary key REFERENCE_NUMBER is a surrogate-style identifier, while IGS_GE_NOTE_U1 enforces uniqueness on the same column and serves as the business-key candidate for downstream joins.

Common Use Cases and Queries

Typical reporting scenarios involve retrieving all notes attached to a specific student, unit, or offering. Because the note association is normalized into child tables such as IGS_PE_PERS_NOTE or IGS_PS_UNIT_OFR_NOTE, a join on REFERENCE_NUMBER is required. For example:

  • Retrieve all notes for a person: SELECT g.REFERENCE_NUMBER, g.S_NOTE_FORMAT_TYPE, g.NOTE_TEXT FROM IGS_GE_NOTE g JOIN IGS_PE_PERS_NOTE p ON p.REFERENCE_NUMBER = g.REFERENCE_NUMBER WHERE p.PERSON_ID = :person_id;
  • Identify OLE-linked notes only: SELECT REFERENCE_NUMBER, NOTE_OLE FROM IGS_GE_NOTE WHERE NOTE_OLE IS NOT NULL;
  • Audit recently modified notes: SELECT REFERENCE_NUMBER, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM IGS_GE_NOTE WHERE LAST_UPDATE_DATE > SYSDATE - 30;

These patterns support student services dashboards, compliance audits, and migration extracts where note content must be preserved alongside its source entity.

Related Objects

IGS_GE_NOTE is referenced by numerous child tables, each representing a note association for a specific student-system entity. The most significant include:

These relationships confirm the table's role as a shared note hub, with each dependent table supplying the foreign-key context that gives a note its meaning.