Search Results igs_ad_pnmembr_nots

Overview

The table IGS_AD_PNMEMBR_NOTS is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically supporting the admissions functionality. It serves as a repository for notes generated by panel members during the application review process. When an application is assigned to a panel for evaluation, individual members can create and version notes related to their assessment. This table is critical for maintaining a formal, auditable record of the deliberation and feedback provided by each panel member, ensuring transparency and continuity in the admissions decision-making workflow. Its existence underscores the structured, committee-based review processes common in higher education admissions managed by Oracle EBS.

Key Information Stored

The table's structure is designed to uniquely identify and version notes linked to a specific panel member on a specific application panel. The primary key is a composite of three columns, which together enforce data integrity for note versions. The key columns, as defined by the primary key IGS_AD_PNMEMBR_NOTS_PK, are:

• PANEL_DTLS_ID: A foreign key that links the note to the specific application instance panel (in IGS_AD_PNMEMBR_DTLS).
• MEMBER_PERSON_ID: A foreign key identifying the individual panel member (person) who authored the note.
• NOTES_VERSION_NUM: A numeric sequence that tracks different versions of notes created by the same member for the same panel, allowing for updates and revisions over time.

While the specific content column for the note text is not listed in the provided metadata, it is implied by the table's description. The table would logically contain at least one column (e.g., NOTE_TEXT or MEMBER_NOTES) to store the actual commentary, along with standard audit columns like CREATION_DATE and CREATED_BY.

Common Use Cases and Queries

This table is primarily accessed to review the complete evaluation history for an application. Common operational and reporting scenarios include generating a consolidated report of all panel member feedback for a given application, auditing changes to a specific member's notes over time, and ensuring all assigned members have submitted their assessments. A typical query would join this table with the panel member details (IGS_AD_PNMEMBR_DTLS) and person tables to retrieve readable information.

Sample SQL Pattern:
SELECT pmd.panel_dtls_id, pmd.member_person_id, ppn.full_name, pmn.notes_version_num, pmn.note_text, pmn.creation_date
FROM igs_ad_pnmembr_nots pmn,
igs_ad_pnmembr_dtls pmd,
per_all_people_f ppn
WHERE pmn.panel_dtls_id = pmd.panel_dtls_id
AND pmn.member_person_id = pmd.member_person_id
AND pmd.member_person_id = ppn.person_id
AND SYSDATE BETWEEN ppn.effective_start_date AND ppn.effective_end_date
AND pmd.panel_dtls_id = :p_panel_dtls_id
ORDER BY pmd.member_person_id, pmn.notes_version_num;

Related Objects

The table IGS_AD_PNMEMBR_NOTS has a direct and essential relationship with the IGS_AD_PNMEMBR_DTLS table, as indicated by its foreign key constraints. It references IGS_AD_PNMEMBR_DTLS on the composite key (PANEL_DTLS_ID, MEMBER_PERSON_ID). This means a note record cannot exist without a corresponding record defining that member's assignment to the panel. The table is a child object within a hierarchy likely rooted in an application panel header table. While not listed in the metadata, it may be referenced by various Student System forms, reports, and APIs that manage panel reviews and is integral to the admissions workflow controlled by the underlying Oracle EBS application logic.