Search Results igs_ps_ofr_note
Overview
The IGS_PS_OFR_NOTE table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS). It functions as the central repository for associating descriptive notes with specific program offerings. A program offering refers to an instance of an academic program (course) scheduled for a particular academic calendar period and version. This table does not store the note text itself but instead maintains the relationships between an offering and its corresponding notes, which are stored in the generic notes repository (IGS_GE_NOTE). Its primary role is to enable the attachment of contextual information—such as administrative instructions, special requirements, or delivery details—to a scheduled program, ensuring this critical information is available to users and integrated processes within the student lifecycle.
Key Information Stored
The table's structure is defined by its composite primary key, which uniquely identifies a note linkage for a program offering. The key columns are COURSE_CD (the program code), VERSION_NUMBER (the program version), CAL_TYPE (the academic calendar type of the offering), and REFERENCE_NUMBER (the unique identifier of the note in the IGS_GE_NOTE table). A critical additional column is CRS_NOTE_TYPE, which classifies the note (e.g., administrative, prerequisite, fee information) by referencing the IGS_PS_NOTE_TYPE_ALL table. This type classification allows for organized retrieval and application-specific display of notes based on their purpose.
Common Use Cases and Queries
A primary use case is the retrieval of all notes for a specific program offering to display on a student's course schedule or an advisor's screen. For example, an institution may attach notes regarding changed room locations or special session dates. Common reporting involves listing all active offerings that have a particular type of note, such as a health and safety warning. A typical SQL pattern to fetch note text for an offering would join IGS_PS_OFR_NOTE to IGS_GE_NOTE on the REFERENCE_NUMBER and filter on the offering's identifiers.
- Sample Query: SELECT n.note_text, nt.note_type_name FROM igs_ps_ofr_note ofrn JOIN igs_ge_note n ON ofrn.reference_number = n.reference_number JOIN igs_ps_note_type_all nt ON ofrn.crs_note_type = nt.note_type WHERE ofrn.course_cd = 'BSC-CHEM' AND ofrn.cal_type = 'SEMESTER';
Related Objects
The table's integrity and functionality are defined by its relationships with other key Student System tables, as documented by its foreign key constraints.
- IGS_PS_OFR_ALL: This is the parent table for the program offering itself. The foreign key on (COURSE_CD, VERSION_NUMBER, CAL_TYPE) ensures every note association is linked to a valid, existing offering.
- IGS_GE_NOTE: This table stores the actual note text and metadata (creator, date). The foreign key on REFERENCE_NUMBER points to the specific note record being associated with the offering.
- IGS_PS_NOTE_TYPE_ALL: This table defines the valid note types. The foreign key on the CRS_NOTE_TYPE column ensures the note association is categorized using a controlled list of types.
-
Table: IGS_PS_OFR_NOTE
12.2.2
product: IGS - Student System (Obsolete) , description: This table describes the notes associated with a program offering. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_PS_NOTE_TYPE_ALL
12.2.2
product: IGS - Student System (Obsolete) , description: This entity describes the available program note types. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_PS_OFR_ALL
12.2.2
product: IGS - Student System (Obsolete) , description: This entity describes an offering of a university program within a calendar type. , implementation_dba_data: Not implemented in this database ,
-
Table: IGS_GE_NOTE
12.2.2
product: IGS - Student System (Obsolete) , description: This table is used to store notes that may be recorded against many major entities for example courses, units, persons. The note may be an OLE object like word document, excel spreadsheet, and so on. , implementation_dba_data: Not implemented in this database ,