Results for “igs_pe_note_type”

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

Overview

IGS_PE_NOTE_TYPE is a reference (lookup) table within the Oracle E-Business Suite Student System module (IGS). It defines the valid categories of notes that may be recorded against a person in the institution's person-management model. Rather than storing the narrative text of a note, this table stores the classification that governs how a note is grouped, filtered, reported, and in many institutional configurations, secured. Every person note in the system is stamped with a value drawn from this table, which makes it a foundational control object for the student and person information subsystem.

The ETRM metadata records that this entity is not implemented in this database for the referenced environment. This notation indicates the table is part of the shipped IGS schema metadata but was not deployed (that is, no physical segment was created, typically because the corresponding product or feature set was not licensed or installed). Consultants should confirm physical presence in the target instance via ALL_TABLES before writing dependent SQL.

From a Data Vault modeling perspective, the documented foreign-key topology classifies this object as hub-leaning. The table presents a stable, low-volatility business concept whose primary key is the single column PE_NOTE_TYPE, and which is referenced by multiple dependent tables. This makes it a natural candidate for a hub entity in a Data Vault or dimensional staging layer, with each dependent note table acting as a link or satellite that joins back to it.

Key Information Stored

The documented metadata identifies a narrow column set, consistent with a code/description reference table. The principal columns are:

• PE_NOTE_TYPE — the business key and primary key column, constrained by IGS_PE_NOTE_TYPE_PK. It holds the short code identifying the note category (for example, advising, disciplinary, or general contact notes) and is the value propagated into all dependent note tables.
• Descriptive attributes associated with the code, typically a meaning/description pair and a system-assigned enabled indicator, drawn from the standard IGS reference-table pattern.

Because the primary key is defined on PE_NOTE_TYPE itself rather than on a synthetic sequence-generated identifier, the business key and the surrogate key coincide here. There is no separate hidden surrogate column documented. In Data Vault terms this simplifies hub construction: the hub hash key is derived directly from the PE_NOTE_TYPE code, with the code retained as the business key. No alternate unique index is documented beyond the primary key, so consumers should treat PE_NOTE_TYPE as the sole guaranteed unique identifier.

Common Use Cases and Queries

The most common requirement is decoding note types on person-note listings, and validating that only active types are offered in entry forms. A representative reporting query joins the note table to this type table:

• List all valid note types for a drop-down or LOV population: SELECT pe_note_type FROM igs_pe_note_type ORDER BY pe_note_type;
• Produce a decoded note register for a person: SELECT n.person_id, n.pe_note_type, t.description FROM igs_pe_pers_note n, igs_pe_note_type t WHERE n.pe_note_type = t.pe_note_type AND n.person_id = :person_id;
• Count note volume by category for a term or date range, grouping on PE_NOTE_TYPE after joining to the administrative note table.
• Identify orphaned or invalid note rows whose type code no longer exists in this reference table, useful during data migration or cleanup.

Because the object is reported as not implemented in some environments, migration scripts should test for its existence and degrade gracefully when the IGS person-note feature is absent.

Related Objects

The documented foreign-key relationships establish the following dependent objects, all of which reference IGS_PE_NOTE_TYPE through the PE_NOTE_TYPE column:

• IGS_PE_PERS_NOTE — the primary person-note table; joined on IGS_PE_PERS_NOTE.PE_NOTE_TYPE = IGS_PE_NOTE_TYPE.PE_NOTE_TYPE.
• IGF_AP_PERS_NOTE — the financial-aid (IGF) person-note table; joined on IGF_AP_PERS_NOTE.PE_NOTE_TYPE = IGS_PE_NOTE_TYPE.PE_NOTE_TYPE. The cross-module reference to an IGS lookup from the IGF schema illustrates the shared person model across Student System and Financial Aid.

Related supporting objects typically include the IGS person entity and the reference-table maintenance forms and concurrent programs that seed and validate note-type codes. These three tables constitute the core relationship set documented in the ETRM metadata and should anchor any impact analysis for changes to note-type values.