Search Results igs_ps_note_type

Overview

The view IGS_PS_NOTE_TYPE is a legacy Oracle E-Business Suite object belonging to the IGS – Student System product family, a module now classified as obsolete in the EBS 12.1.1 and 12.2.2 release streams. The view exposes student system note type reference data — the coded list of note categories used to classify observations, comments, or annotations recorded against student records within the Oracle Student System (OSS) application.

From a reporting and integration standpoint, IGS_PS_NOTE_TYPE functions as the organization-secured (multi-org) reporting layer over its single base table. It is intended to present note type rows filtered by the operating unit context of the querying session, allowing concurrent programs, reports, and interfaces to retrieve only those note types that belong to the appropriate organization. Because IGS is obsolete, this view is rarely populated in modern EBS instances and is retained principally for backward compatibility with customizations or historical data migrations.

Underlying Base Objects

According to the documented ETRM view text, IGS_PS_NOTE_TYPE is defined strictly over a single base object:

• IGS_PS_NOTE_TYPE_ALL — the multi-org (partitioned by ORG_ID) base table holding all note type definitions across operating units.

No other referenced base objects are documented. The view is a thin projection wrapper: it selects the ROWID as ROW_ID and passes through every significant column of IGS_PS_NOTE_TYPE_ALL. Its principal logic is the organization security predicate, which compares the row's ORG_ID against the operating unit identifier derived from the session's USERENV('CLIENT_INFO') value. The DECODE/SUBSTRB construct extracts a ten-character organization identifier when the first character is not a space, defaulting to -99 when no value is present. Only rows matching the session's organization context (or the shared -99 set) are returned. ETRM notes that the view is not implemented in the documented reference database, meaning the base table may be absent in a standard install.

Key Columns

• ROW_ID — the base table ROWID, uniquely identifying each note type row.
• CRS_NOTE_TYPE — the primary business key; the coded identifier for the student note type.
• DESCRIPTION — the human-readable description of the note type.
• ORG_ID — the operating unit that owns the note type; drives the view's organization security filter.
• CREATED_BY / CREATION_DATE — audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — standard "WHO" audit columns capturing the most recent modification user, date, and login session.

Common Use Cases and Queries

Typical usage involves joining note type codes to student note transactions when generating reports, validating lookup values during data conversion, or extracting reference data for downstream integration. The following query lists all note types visible to the current operating unit context:

SELECT crs_note_type, description, org_id
FROM igs_ps_note_type
ORDER BY crs_note_type;

A join pattern resolving note types against student note entries would resemble:

SELECT n.student_id, n.crs_note_type, t.description
FROM igs_ps_student_notes n, igs_ps_note_type t
WHERE n.crs_note_type = t.crs_note_type;

Because the view applies organization security automatically, developers should ensure the correct operating unit is initialized in CLIENT_INFO before querying; otherwise, only the default -99 (global) note types are returned. Given the obsolete status of the IGS product, these constructs should be treated as legacy reference only.