Search Results igs_or_org_notes_n1

Overview

IGS.IGS_OR_ORG_NOTES is a transactional table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 IGS (Student Systems / Oracle Student System) schema. It stores free-text notes associated with institutions, organizational units, and locations, allowing implementers and end users to attach descriptive or qualifying information to organizational structures without altering the base entity records. The table is registered under FND Design Data as IGS.IGS_OR_ORG_NOTES, carries a VALID status, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a modeling perspective, the heuristic Data Vault classification for this object is a link. The table sits between organizational structure entities (institutions, units, locations) and a note-type reference table, resolving a many-to-many-style association keyed by structural identity and note type. Each row therefore represents a single note occurrence tied to one organization structure record and one note type, with effective dating through START_DATE and END_DATE.

Key Information Stored

The combined primary and unique business key is defined by the unique index IGS_OR_ORG_NOTES_U1 over ORG_STRUCTURE_ID, ORG_STRUCTURE_TYPE, ORG_NOTE_SEQUENCE, and ORG_NOTE_TYPE. Together these columns represent the business-key candidate that the table enforces for uniqueness; there is no separate single-column surrogate key documented. The most important columns are:

• ORG_STRUCTURE_ID (VARCHAR2 30) — identifier of the organization structure (institution, unit, or location) to which the note belongs.
• ORG_STRUCTURE_TYPE (VARCHAR2 30) — discriminator indicating whether the note applies to a location, organization, or institution.
• ORG_NOTE_SEQUENCE (NUMBER 15) — a sequence-generated ordering value that distinguishes multiple notes of the same type on the same structure.
• ORG_NOTE_TYPE (VARCHAR2 10) — the classification of the note, validated against IGS_OR_ORG_NOTE_TYPE.
• NOTE_TEXT (VARCHAR2 2000) — the actual note content, capped at 2000 characters.
• START_DATE (DATE) — the effective start date from which the note applies.
• END_DATE (DATE) — the effective end date beyond which the note no longer applies.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns capturing audit and concurrency information.

Common Use Cases and Queries

Typical usage includes retrieving all active notes for a given institution or unit as of a point in time, and reporting note-type distributions across organizational structures. Because START_DATE and END_DATE define validity, date-filtered predicates are common.

A frequent query pattern is to fetch currently effective notes for one structure:

• SELECT ORG_STRUCTURE_ID, ORG_STRUCTURE_TYPE, ORG_NOTE_TYPE, NOTE_TEXT FROM IGS.IGS_OR_ORG_NOTES WHERE ORG_STRUCTURE_ID = :id AND ORG_STRUCTURE_TYPE = :type AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE + 1);
• Join to the note type reference to resolve descriptions: SELECT n.*, t.NOTE_TYPE_DESCRIPTION FROM IGS.IGS_OR_ORG_NOTES n, IGS.IGS_OR_ORG_NOTE_TYPE t WHERE n.ORG_NOTE_TYPE = t.ORG_NOTE_TYPE.
• Uniqueness and duplicate detection using the U1 key, ordered by ORG_NOTE_SEQUENCE to reconstruct note history.

The standard full-column extraction documented for the object is a straightforward SELECT of all twelve columns from IGS.IGS_OR_ORG_NOTES ordered by the key columns.

Related Objects

The following objects are most significant to IGS_OR_ORG_NOTES based on documented dependencies:

• IGS.IGS_AD_LOCATION_ALL — referenced via ORG_STRUCTURE_ID for location-based structures.
• IGS.IGS_OR_ORG_NOTE_TYPE — the note-type validation reference joined on ORG_NOTE_TYPE.
• APPS synonym IGS_OR_ORG_NOTES — the APPS-layer synonym through which application code accesses the base table.
• Organization structure base tables (institution and unit definitions) that share the ORG_STRUCTURE_ID / ORG_STRUCTURE_TYPE key pattern.
• The IGS_OR_ORG_NOTES_U1 and IGS_OR_ORG_NOTES_N1 indexes, which support key-based and note-type-based lookups respectively.