Results for “appl_notes_id”

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

Overview

IGS_AD_APPL_NOTES_V is a reporting view within the Oracle E-Business Suite Student System (IGS) module, historically delivered as part of the Oracle Student System product line. The view exposes admissions application notes — free-form or categorized annotations attached to a person's admission application record — by joining the base notes table to the note type reference table. Its principal purpose is to denormalize the note type identifier into human-readable category, type, and description values, so that operational reports, concurrent programs, and integration extracts can present admissions notes without requiring the caller to perform the lookup join independently.

Within IGS, admissions staff record notes against an application to capture advising commentary, document receipt confirmation, decision rationale, and correspondence history. The view is typically consumed by Oracle Reports, BI Publisher data templates, and custom PL/SQL blocks that render an applicant's note history. Under ETRM 12.1.1 and 12.2.2 the object is designated as obsolete and documented as "Not implemented in this database," indicating that the view definition remains catalogued in the ETRM repository but the object is not created in a standard, freshly installed release 12 environment. Its presence in the data dictionary is therefore informational rather than operational, and any reference to it should be validated against the deployed schema before use.

Underlying Base Objects

The documented view text defines the object over two base tables joined on the note type identifier:

• IGS_AD_APPL_NOTES (aliased AN) — the transactional table holding admissions application notes; supplies the surrogate key, person reference, application number, nominated course, sequence, note type, reference note, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).
• IGS_AD_NOTE_TYPES (aliased NT) — the reference table for note types; supplies NOTES_CATEGORY, NOTE_TYPE, and DESCRIPTION.

The join predicate is AN.NOTE_TYPE_ID = NT.NOTES_TYPE_ID, an inner join. Consequently, any application note whose NOTE_TYPE_ID does not resolve to a row in IGS_AD_NOTE_TYPES is excluded from the result set. The view also projects AN.ROWID as ROW_ID. ETRM documents no other referenced base objects at the 12.2.2 level; in particular, no lookup to a person or application header table is included, so PERSON_ID and ADMISSION_APPL_NUMBER are exposed as raw key values rather than resolved names or statuses.

Key Columns

• ROW_ID — the physical row identifier of the underlying IGS_AD_APPL_NOTES row; useful for targeted DML or duplicate detection.
• APPL_NOTES_ID — the primary key of the application note, and the column most commonly supplied as a bind parameter when retrieving a single note.
• PERSON_ID — the party identifier of the applicant to whom the note belongs.
• ADMISSION_APPL_NUMBER and NOMINATED_COURSE_CD — the admission application reference and the course nominated on that application.
• SEQUENCE_NUMBER — ordering attribute that establishes the note's position within the application's note list.
• NOTE_TYPE_ID — foreign key to IGS_AD_NOTE_TYPES; carried through alongside the resolved values.
• REF_NOTES_ID — self-referencing link to a related note, supporting threaded or follow-up notes.
• NOTES_CATEGORY, NOTE_TYPE, DESCRIPTION — the descriptive attributes resolved from IGS_AD_NOTE_TYPES, providing the reporting-friendly classification of each note.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns for provenance and change tracking.

Common Use Cases and Queries

Typical scenarios include producing an applicant note history for admissions review, auditing notes entered in a date range, and extracting note volume by category for management reporting. A representative query retrieving all notes for a given applicant, ordered by sequence, is:

• SELECT appl_notes_id, person_id, admission_appl_number, nominated_course_cd, sequence_number, notes_category, note_type, description, creation_date
• FROM igs_ad_appl_notes_v
• WHERE person_id = :p_person_id
• ORDER BY admission_appl_number, sequence_number;

A category summary follows the same pattern, grouping by notes_category and counting rows. Because the view is documented as not implemented, queries should first confirm existence via ALL_VIEWS or ALL_OBJECTS before execution, and any dependency in custom code should be reviewed during upgrade remediation between 12.1.1 and 12.2.2.