Results for “igs_ps_catlg_notes_all_u1”

6 results




Overview
Explore in AI Chat

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

Overview

IGS.IGS_PS_CATLG_NOTES_ALL is a transactional table in the Oracle EBS IGS (Intelligent Grants System / Student Systems) schema that stores free-text notes attached to academic catalog versions. This object belongs to the product family commonly deployed in higher-education and grants-management implementations of EBS 12.1.1 and 12.2.2, where catalog versions are built and published as part of curriculum or program administration. The table is registered in FND Design Data as IGS.IGS_PS_CATLG_NOTES_ALL, holds a status of VALID, and resides in the APPS_TS_TX_DATA tablespace with APPS_TS_TX_IDX for its indexes.

The documented table carries 13 columns and a single primary key, IGS_PS_CATLG_NOTES_PK, on CATALOG_NOTE_ID. Heuristic Data Vault classification, derived from the foreign-key structure, suggests this table functions as a link object: it associates a catalog version (CATALOG_VERSION_ID) with a note type (NOTE_TYPE_ID) and its payload text. The "_ALL" suffix and presence of ORG_ID indicate the table is enabled for Multi-Org, so rows are partitioned by operating unit.

Key Information Stored

The most significant columns are:

  • CATALOG_NOTE_ID — surrogate primary key and unique identifier for each catalog note; the sole column of unique index IGS_PS_CATLG_NOTES_ALL_U1.
  • CATALOG_VERSION_ID — foreign key to IGS_PS_CATLG_VERS_ALL, identifying the catalog version the note belongs to.
  • NOTE_TYPE_ID — foreign key to IGS_PS_NOTE_TYPES, classifying the note (for example, internal, published, or structured categories).
  • SEQUENCE — ordering value that, together with CATALOG_VERSION_ID and NOTE_TYPE_ID, forms the business-key unique index IGS_PS_CATLG_NOTES_ALL_U2.
  • NOTE_TEXT — the free-form note content (VARCHAR2(2000)); the primary payload of the row.
  • CREATE_DATE and END_DATE — effective dating that allows notes to be valid over a bounded window.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns for audit and concurrency tracking.
  • ORG_ID — operating unit identifier, enabling Multi-Org security for the row.

The non-unique index IGS_PS_CATLG_NOTES_ALL_N2 on NOTE_TYPE_ID supports queries filtered by note category, which is a common access path when producing notes reports.

Common Use Cases and Queries

Catalog notes are typically retrieved for review and publishing screens, for audit reporting of annotations attached to a catalog version, and for extracting textual context alongside catalog structure. A baseline query is the documented cut-and-paste SQL:

  • Selecting CATALOG_NOTE_ID, CATALOG_VERSION_ID, NOTE_TYPE_ID, CREATE_DATE, END_DATE, SEQUENCE, and NOTE_TEXT in SEQUENCE order to reconstruct the notes list for a given catalog version.
  • Filtering on NOTE_TYPE_ID to isolate a specific note category, supported by IGS_PS_CATLG_NOTES_ALL_N2.
  • Applying ORG_ID in the WHERE clause to respect Multi-Org security when the query is not executed through the standard ORG security mechanism.
  • Using END_DATE to exclude expired notes from current reporting.

Related Objects

The following objects are the most significant dependencies for this table:

  • IGS.IGS_PS_CATLG_VERS_ALL — joined via IGS_PS_CATLG_NOTES_ALL.CATALOG_VERSION_ID = IGS_PS_CATLG_VERS_ALL.CATALOG_VERSION_ID.
  • IGS.IGS_PS_NOTE_TYPES — joined via IGS_PS_CATLG_NOTES_ALL.NOTE_TYPE_ID = IGS_PS_NOTE_TYPES.NOTE_TYPE_ID.
  • APPS.IGS_PS_CATLG_NOTES_ALL — the APPS synonym/view layer that most application queries reference instead of the IGS base table.
  • The primary key constraint IGS_PS_CATLG_NOTES_PK and unique constraints IGS_PS_CATLG_NOTES_ALL_U1 and IGS_PS_CATLG_NOTES_ALL_U2, which enforce row identity and business-key uniqueness.

No other database objects are documented as being referenced by this table in the supplied metadata.