Results for “igs_ps_unit_ofr_note”

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

Overview

IGS_PS_UNIT_OFR_NOTE is a transactional table in the IGS (Student System) product schema of Oracle E-Business Suite, holding the free-text notes attached to a specific unit offering. A unit offering represents a scheduled, deliverable instance of a unit (course) within a calendar type and version; this table acts as the child that carries the narrative or informational notes associated with that offering, classified by note type. It is populated and maintained by the Student System's unit offering maintenance forms and concurrent processes, and it is referenced wherever offering notes must be displayed, printed, or transmitted (for example, prospectus extracts, handbook output, and self-service offering inquiry).

From a data-modeling perspective, the mined relationship data classifies this object heuristically as a link. This reflects its structure as an association between three independent business entities — the unit offering, the note type, and the underlying note text — resolved through the composite key. This classification should be treated as a modeling suggestion rather than a prescriptive design statement.

Key Information Stored

The table comprises ten documented columns. The most significant are:

• UNIT_CD — the unit (course) code identifying the offering to which the note belongs.
• VERSION_NUMBER — the version of the unit offering, allowing multiple co-existing versions of the same unit.
• CAL_TYPE — the calendar type under which the offering is delivered (for example, academic year or teaching period calendar).
• REFERENCE_NUMBER — the reference to the note text record itself, pointing into the global note store IGS_GE_NOTE.
• CRS_NOTE_TYPE — the note type code that categorizes the note, sourced from IGS_PS_NOTE_TYPE_ALL.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit tracking of row creation and modification.

The primary key, IGS_PS_UNIT_OFR_NOTE_PK, is a composite business key over (UNIT_CD, VERSION_NUMBER, CAL_TYPE, REFERENCE_NUMBER); there is no separate surrogate single-column identifier, so the business key itself functions as the unique row identifier. A unique index, IGS_PS_UNIT_OFR_NOTE_U1, enforces the same four-column combination, confirming that a given note reference may be attached only once to a given unit offering version and calendar type.

Common Use Cases and Queries

Typical reporting and integration scenarios include extracting all notes for an offering presented to students, validating that mandatory note types are attached before an offering is published, and migrating offering notes between environments.

• Retrieve notes for a specific offering: SELECT n.reference_number, n.crs_note_type FROM igs_ps_unit_ofr_note n WHERE n.unit_cd = :unit AND n.version_number = :version AND n.cal_type = :cal;
• Join to the note text store to obtain the actual narrative: SELECT t.note_text FROM igs_ps_unit_ofr_note n, igs_ge_note t WHERE n.reference_number = t.reference_number AND n.unit_cd = :unit;
• List note types in use per offering by joining IGS_PS_NOTE_TYPE_ALL on CRS_NOTE_TYPE.
• Audit recently changed notes using LAST_UPDATE_DATE and LAST_UPDATED_BY for change-tracking reports.

Related Objects

Dependencies are defined through the documented foreign keys:

• IGS_PS_UNIT_OFR — parent offering; join on UNIT_CD, VERSION_NUMBER, and CAL_TYPE.
• IGS_GE_NOTE — the note text store; join on REFERENCE_NUMBER.
• IGS_PS_NOTE_TYPE_ALL — note type validation; join on CRS_NOTE_TYPE.

These three parents govern integrity: notes cannot exist without a valid offering, a valid note record, and a valid note type.