Search Results igs_or_org_note_types_pk

Overview

IGS_OR_ORG_NOTE_TYPE is a reference (lookup) table in the IGS — Student System product of Oracle E-Business Suite, owned by the IGS schema. It stores user-defined structures or classifications that describe note types available for organizational structure entities such as institutions, organizational units, or locations. In practical terms, the table acts as the master list of organizational note categories: each row defines a note type that can subsequently be attached to an institution, an organizational unit, or a location through the transactional notes table IGS_OR_ORG_NOTES.

From a Data Vault modeling perspective, the heuristic classification supplied in the metadata is hub-leaning. This is consistent with the table's structure: it holds a stable, uniquely keyed set of business concepts (note types) that are referenced by dependent tables, rather than transactional detail. A hub would be modeled on the business key ORG_NOTES_TYPE, with the remaining descriptive and date-stamp attributes carried in a satellite. Practically, the table functions as a controlled code list that governs which organizational notes may be captured and how they are classified.

Key Information Stored

The documented physical schema for 12.1.1 contains 10 columns. The most significant are:

• ORG_NOTES_TYPE — the primary key column, defined by the primary key constraint IGS_OR_ORG_NOTE_TYPES_PK and also backed by the unique index IGS_OR_ORG_NOTE_TYPE_U1. This is the business-key candidate that uniquely identifies each note type and is the column referenced by child tables.
• NOTE_TYPE_DESCRIPTION — the user-defined descriptive text explaining the purpose or classification of the note type, used in list-of-values displays and reporting.
• INST_FLAG — indicates whether the note type is available for use against institution records.
• UNIT_FLAG — indicates whether the note type is available for organizational units.
• LOCATION_FLAG — indicates whether the note type is available for location records.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified the row, and when.

The ORG_NOTES_TYPE column is the sole surrogate/business key; the descriptive and flag columns act as payload. Because the unique index IGS_OR_ORG_NOTE_TYPE_U1 covers ORG_NOTES_TYPE, the table enforces uniqueness on the business key independently of the primary key constraint.

Common Use Cases and Queries

The primary use case is validating and presenting the set of note types available when a user adds descriptive information to an institution, organizational unit, or location. Applications read this table to build the note type list of values, and conditional logic on INST_FLAG, UNIT_FLAG, and LOCATION_FLAG filters the list to only the note types valid for the entity being edited.

A typical reporting query retrieves all note types with their descriptions and applicability flags:

• SELECT org_notes_type, note_type_description, inst_flag, unit_flag, location_flag FROM igs.igs_or_org_note_type;
• SELECT n.org_notes_type, t.note_type_description, n.org_id FROM igs.igs_or_org_notes n JOIN igs.igs_or_org_note_type t ON n.org_note_type = t.org_notes_type; — the standard join used to resolve note type text against actual organizational notes.

Common reporting scenarios include auditing which note types are enabled for each organizational entity class, producing reference data listings for configuration reviews, and reconciling notes captured against institutions versus units versus locations by grouping on the flag columns.

Related Objects

The most significant related object is the transactional child table that references this lookup:

• IGS_OR_ORG_NOTES — the notes table whose column ORG_NOTES_TYPE carries a foreign key back to IGS_OR_ORG_NOTE_TYPE. This relationship is confirmed by the documented FK metadata; it is the principal dependency on this reference table.

The organizational entities described in this table's purpose — institutions, organizational units, and locations — are represented elsewhere in the IGS schema and consume this note type list through the IGS_OR_ORG_NOTES table. Reporting and integration code typically resolves note type descriptions through the join shown above rather than reading the code column alone.