Search Results igs_ps_unt_ofr_pat_n




Overview
Explore in AI Chat

Overview

The table IGS_PS_UNT_OFR_PAT_N is a data object within the Oracle E-Business Suite (EBS) Student System (IGS). Its primary function is to store descriptive notes associated with a Unit Offering Pattern, which defines the specific scheduling and delivery mode (e.g., on-campus, online) for a unit of study in a given academic period. This table serves as a critical junction, linking textual notes to their corresponding academic offering patterns. It is important to note that the ETRM documentation explicitly marks the IGS Student System as "Obsolete" and states this specific table is "Not implemented in this database." This indicates it was part of a legacy data model that may not be present or actively used in standard Oracle EBS 12.1.1 or 12.2.2 deployments, though its structure informs the historical design of student information systems.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each note record. The key columns are UNIT_CD (the unit code), VERSION_NUMBER (the unit version), CAL_TYPE (the calendar type, e.g., semester), CI_SEQUENCE_NUMBER (the sequence number for the calendar instance), and REFERENCE_NUMBER (a foreign key to the actual note text). Beyond the key, a significant column is CRS_NOTE_TYPE, which is a foreign key referencing a note type classification table. This column allows for categorizing notes (e.g., administrative, prerequisite, delivery instructions). The table does not store the note text directly; instead, it uses the REFERENCE_NUMBER to join to a central notes repository table, IGS_GE_NOTE.

Common Use Cases and Queries

In implementations where this table is active, its primary use case is to retrieve all administrative or descriptive notes attached to a specific unit offering for display in academic catalogs, student enrollment systems, or administrative reports. A typical query would join the note linkage table to the master note text and the unit offering pattern details. For example, to find all notes for a particular unit offering, a developer might use a SQL pattern such as: SELECT n.note_text, nt.note_type_name FROM igs_ps_unt_ofr_pat_n link JOIN igs_ge_note n ON link.reference_number = n.reference_number JOIN igs_ps_note_type_all nt ON link.crs_note_type = nt.note_type WHERE link.unit_cd = :p_unit_cd AND link.cal_type = :p_cal_type; Given its "not implemented" status, direct operational use in standard EBS is unlikely, but understanding this pattern is valuable for data migration or integration with legacy systems.

Related Objects

The table's integrity is maintained through defined foreign key relationships with three core tables in the Student System model, as documented in the ETRM metadata:

  • IGS_PS_UNIT_OFR_PAT_ALL: This is the parent table for the Unit Offering Pattern itself. The relationship is established via the columns UNIT_CD, VERSION_NUMBER, CAL_TYPE, and CI_SEQUENCE_NUMBER. Every note record must correspond to a valid, existing offering pattern.
  • IGS_GE_NOTE: This is the central repository for note text. The relationship is via the REFERENCE_NUMBER column. The IGS_PS_UNT_OFR_PAT_N table stores only the reference ID, pointing to the full note details in IGS_GE_NOTE.
  • IGS_PS_NOTE_TYPE_ALL: This table provides a classification for notes. The CRS_NOTE_TYPE column in IGS_PS_UNT_OFR_PAT_N references this table to categorize the note's purpose (e.g., "Prerequisite Information," "Delivery Mode Details").