Results for “igs_ad_appl_notes”

44 results




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

Overview

IGS_AD_APPL_NOTES is a transactional table within the Oracle E-Business Suite IGS (Student System) product family, documented as holding details of an applicant's notes. In the context of Oracle EBS 12.1.1 and 12.2.2, the object belongs to the legacy student and admissions data model, and the ETRM metadata flags the IGS product as obsolete. The documentation explicitly records an implementation note of "Not implemented in this database," meaning the table may exist only as a documented artifact or seed definition in certain environments rather than as an actively maintained operational object. Its role is to associate free-text or reference-based notes with a specific admission application, keyed by the applicant and application context.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This is a reasonable modeling suggestion because the table's primary key, APPL_NOTES_ID, is a surrogate identifier while the foreign keys connect an applicant application instance to a note type definition, producing a relationship record rather than a pure descriptive satellite. Modeling it as a link preserves the many-to-many style association between applications and note types.

Key Information Stored

The documented physical schema for 12.1.1 shows 16 columns owned by the IGS schema. The most significant columns are:

The true business-key candidates are the compound fields PERSON_ID, ADMISSION_APPL_NUMBER, NOMINATED_COURSE_CD, and SEQUENCE_NUMBER, which together identify an application instance, combined with NOTE_TYPE_ID to distinguish the note category. APPL_NOTES_ID remains the sole documented primary key.

Common Use Cases and Queries

Typical reporting use cases include retrieving all notes for a given applicant, listing notes by type, and reconciling note activity against admission applications. A representative query joins the table to its parent application instance and note type lookup:

  • Applicant note listing: SELECT a.APPL_NOTES_ID, a.PERSON_ID, a.ADMISSION_APPL_NUMBER, a.NOTE_TYPE_ID FROM IGS_AD_APPL_NOTES a WHERE a.PERSON_ID = :person_id ORDER BY a.ADMISSION_APPL_NUMBER, a.SEQUENCE_NUMBER;
  • Note type enrichment: SELECT a.APPL_NOTES_ID, t.NOTE_TYPE_ID FROM IGS_AD_APPL_NOTES a, IGS_AD_NOTE_TYPES t WHERE a.NOTE_TYPE_ID = t.NOTE_TYPE_ID;
  • Application reconciliation: join on PERSON_ID, ADMISSION_APPL_NUMBER, and NOMINATED_COURSE_CD against IGS_AD_PS_APPL_INST_ALL.

Because the table is documented as not implemented, queries should be preceded by an existence check against ALL_TABLES before use in production extracts.

Related Objects

The most significant related objects derive from the documented foreign-key relationships:

  • IGS_AD_PS_APPL_INST_ALL — parent application instance; joined via PERSON_ID, ADMISSION_APPL_NUMBER, and NOMINATED_COURSE_CD.
  • IGS_AD_NOTE_TYPES — note type lookup; joined via NOTE_TYPE_ID.
  • IGS_AD_APPL_NOTES_PK — the primary key constraint on APPL_NOTES_ID.
  • WHO audit and concurrent program columns link implicitly to FND_CONCURRENT_REQUESTS and FND_APPLICATION for request and program context.
  • Any IGS admission inquiry views or APIs that surface applicant notes will reference this table through the PERSON_ID and application keys.

Given the obsolete classification, integration effort should target current student system alternatives, while this object remains relevant for historical data lineage and migration analysis.