Results for “igs_en_unit_set_note”

25 results




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

Overview

IGS_EN_UNIT_SET_NOTE is a transactional detail table within the Oracle E-Business Suite IGS – Student System product family. As the name implies, it stores free-text notes that are attached to unit sets — the catalog entities that group academic units (subjects or modules) into coherent structures such as programs of study, enrollment categories, or curriculum pathways. In Oracle EBS 12.1.1 and 12.2.2 the object is flagged as obsolete and, per the ETRM implementation metadata, is not implemented in the reference database. The table nonetheless remains part of the documented schema shipped with the Student System data model, and DBA scripts, upgrade utilities, and reverse-engineering tools may still reference it.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is a link. The table associates a unit set with a note record and a note type, rather than owning descriptive attributes of a single business entity. Its grain is defined by the composite primary key, and it exists primarily to record the many-to-many style association between unit sets and the notes stored in the general notes table.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

The unique index IGS_EN_UNIT_SET_NOTE_U1 on (UNIT_SET_CD, VERSION_NUMBER, REFERENCE_NUMBER) is coextensive with the primary key IGS_EN_UNIT_SET_NOTE_PK, confirming that the combination of unit set, version, and note reference is the business key. There is no separate surrogate identifier column; the table relies entirely on the natural composite key.

Common Use Cases and Queries

Typical use cases centre on retrieving or reporting notes attached to unit sets. A common pattern joins the note reference to IGS_GE_NOTE to obtain the note text:

  • Listing all notes for a given unit set and version, ordered by creation date.
  • Reporting notes by note type using CRS_NOTE_TYPE joined to IGS_PS_NOTE_TYPE_ALL.
  • Auditing which users created or modified unit-set notes during a period.
  • Validating orphaned note references — notes in IGS_GE_NOTE that no longer link to any unit set.

A representative query shape is: SELECT n.UNIT_SET_CD, n.VERSION_NUMBER, n.REFERENCE_NUMBER, gt.NOTE_TEXT FROM IGS_EN_UNIT_SET_NOTE n, IGS_GE_NOTE gt WHERE n.REFERENCE_NUMBER = gt.REFERENCE_NUMBER AND n.UNIT_SET_CD = :unit_set. Because the object is obsolete, such queries should be qualified against the specific release before being embedded in production reports.

Related Objects

The following related objects are documented through the foreign-key metadata:

  • IGS_EN_UNIT_SET_ALL – Parent unit set records; joined on UNIT_SET_CD and VERSION_NUMBER.
  • IGS_GE_NOTE – General note repository holding the actual note text; joined on REFERENCE_NUMBER.
  • IGS_PS_NOTE_TYPE_ALL – Note type reference data; joined on CRS_NOTE_TYPE.
  • IGS_EN_UNIT_SET_NOTE_PK / _U1 – Primary key constraint and unique index enforcing the composite business key.

These relationships confirm that the table functions as an association between unit sets and notes, and that its lifecycle is governed by the parent unit set definition.