Results for “igs_ps_catlg_notes_all”
23 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGS_PS_CATLG_NOTES_ALL is a table within the Oracle E-Business Suite Student System (IGS) product family. The ETRM metadata classifies IGS as an obsolete module in the EBS 12.1.1 and 12.2.2 reference environments, and it is explicitly documented as not implemented in the reference database. The table's declared purpose is to describe catalog notes — the free-text and instructional annotations that accompany academic catalog versions in the Student System.
From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link. Its two outbound foreign keys tie a catalog version to a note type, forming a many-to-many association between those two hubs, with the SEQUENCE and NOTE_TEXT attributes carried as descriptive payload. This classification is a heuristic derived from the FK topology rather than a documented Oracle designation.
Key Information Stored
The table contains thirteen documented columns. The surrogate primary key is CATALOG_NOTE_ID, enforced by the unique index IGS_PS_CATLG_NOTES_ALL_U1. A second unique index, IGS_PS_CATLG_NOTES_ALL_U2, covers the composite of CATALOG_VERSION_ID, NOTE_TYPE_ID, and SEQUENCE; this composite is the strongest business-key candidate, guaranteeing that a given note type appears only once per sequence position within a catalog version.
CATALOG_NOTE_ID— surrogate primary key and system-assigned identifier for each catalog note row.CATALOG_VERSION_ID— foreign key toIGS_PS_CATLG_VERS_ALL, establishing the catalog version to which the note belongs.NOTE_TYPE_ID— foreign key toIGS_PS_NOTE_TYPES, classifying the note (for example, admissions note, deadline note, or eligibility note).SEQUENCE— ordering position of the note within its catalog version and note type grouping.NOTE_TEXT— the actual note content presented against the catalog.CREATE_DATEandEND_DATE— effective dating attributes controlling when the note is active.ORG_ID— multi-org operating unit discriminator, indicating the table participates in the EBS multi-organization security model.CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE,LAST_UPDATE_LOGIN— the standard EBS audit columns tracking who created and last modified each row.
The _ALL suffix conventionally signals a multi-org table in EBS, consistent with the presence of ORG_ID.
Common Use Cases and Queries
The principal use case is retrieving the notes displayed against a published catalog version, typically filtered by note type and ordered by sequence. A representative query joins the version and note-type lookup tables:
SELECT n.CATALOG_NOTE_ID, n.SEQUENCE, n.NOTE_TEXT FROM IGS_PS_CATLG_NOTES_ALL n WHERE n.CATALOG_VERSION_ID = :version_id AND n.ORG_ID = :org_id ORDER BY n.SEQUENCE;— renders the ordered note list for one catalog version.SELECT t.DESCRIPTION, COUNT(*) FROM IGS_PS_CATLG_NOTES_ALL n, IGS_PS_NOTE_TYPES t WHERE n.NOTE_TYPE_ID = t.NOTE_TYPE_ID GROUP BY t.DESCRIPTION;— reports note distribution by type.SELECT * FROM IGS_PS_CATLG_NOTES_ALL WHERE TRUNC(CREATE_DATE) >= :start_date AND (END_DATE IS NULL OR END_DATE >= SYSDATE);— isolates currently active notes for catalog maintenance reporting.
Data-migration and integration teams also use the composite unique key to detect duplicates or gaps in sequence numbering when loading catalog content from external sources.
Related Objects
The most significant related objects are the tables reached through its documented foreign keys and the constraints that govern its rows:
IGS_PS_CATLG_VERS_ALL— parent catalog version table, joined onCATALOG_VERSION_ID; the primary dependency for any catalog note query.IGS_PS_NOTE_TYPES— note classification lookup, joined onNOTE_TYPE_ID.IGS_PS_CATLG_NOTES_PK— the primary key constraint onCATALOG_NOTE_ID.IGS_PS_CATLG_NOTES_ALL_U1andIGS_PS_CATLG_NOTES_ALL_U2— the unique indexes providing surrogate and business-key uniqueness respectively.IGS_PS_CATLG_ALL— the base catalog table, reached transitively through the version table for catalog-level reporting.
Because the module is marked obsolete and the table is not implemented in the reference database, consumers should confirm object existence before relying on any query in a live 12.1.1 or 12.2.2 environment.
-
Describes all the catalogs note.
-
Describes all the catalogs note.
Not implemented in this database·Explore IGS module →
-
Table: IGS_PS_NOTE_TYPES 12.2.2
Entity to capture the catalog versions.
Not implemented in this database·Explore IGS module →
-
View: IGS_PS_CATLG_NOTES 12.1.1
APPS.IGS_PS_CATLG_NOTES·↳ IGS_PS_CATLG_NOTES_ALL·Explore IGS module →
-
Table: IGS_PS_CATLG_VERS_ALL 12.2.2
Entity to capture the catalog versions.
Not implemented in this database·Explore IGS module →
-
View: IGS_PS_CATLG_NOTES 12.2.2
Not implemented in this database·Explore IGS module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.