Search Results note_type_description

Overview

APPS.IGS_OR_ORG_NOTE_TYPE_V is a supplementary view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. Its FND Design Data reference is IGS.IGS_OR_ORG_NOTE_TYPE_V, indicating it belongs to the Oracle iGS (Intelligent Grants System / Student System lineage) product family associated with the IGS_OR (Organizations) module. The view is documented with VALID status in ETRM 12.2.2 metadata.

According to the ETRM documentation, this is explicitly described as a "supplementary view used to simplify forms coding." Oracle issues a formal warning: "Oracle does not recommend you query or alter data using this view. It may change dramatically in subsequent minor or major releases." Consequently, the view exists primarily to support Oracle Forms-based user interface logic within the IGS product suite rather than to serve as a stable, supported integration surface. Developers seeking to use the view for reporting or integration purposes should treat its existence as a convenience rather than a contractual interface and consider sourcing data from the underlying base table directly.

Underlying Base Objects

The ETRM dependency metadata identifies the base object referenced by this view as APPS.IGS_OR_ORG_NOTE_TYPE. This is an Oracle base table that stores organization note type definitions — reference data describing the categories of notes that may be attached to organizations within the IGS organization data model. The view does not appear to reference any additional tables or join to other views, meaning it is a single-table projection.

Consistent with its classification as a supplementary forms-coding view, IGS_OR_ORG_NOTE_TYPE_V does not introduce derived columns or computed expressions. It exposes the columns of the underlying table in a form convenient for the Oracle Forms block that drives the Organization Note Types setup screen. The ETRM documentation confirms that APPS.IGS_OR_ORG_NOTE_TYPE_V is not referenced by any database object, reinforcing its role as a leaf-level convenience view rather than a shared dependency for other database components.

Key Columns

The view projects the following columns, as documented in ETRM:

• ROW_ID (ROWID) — Standard Oracle row identifier inherited from the base table, used by Forms for row-level DML operations.
• ORG_NOTES_TYPE (VARCHAR2, 10) — The primary business key: a short code identifying the organization note type.
• NOTE_TYPE_DESCRIPTION (VARCHAR2, 60) — The descriptive text associated with the note type code, displayed on the setup form.
• INST_FLAG (VARCHAR2) — Indicator controlling whether the note type is applicable at the institution level.
• UNIT_FLAG (VARCHAR2) — Indicator controlling whether the note type is applicable at the organizational unit level.
• LOCATION_FLAG (VARCHAR2) — Indicator controlling whether the note type is applicable at the location level.
• CREATION_DATE, CREATED_BY — Standard audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login session responsible.

The three flags (INST_FLAG, UNIT_FLAG, LOCATION_FLAG) collectively scope the note type to the appropriate organizational level, which is the core functional purpose of this reference data.

Common Use Cases and Queries

Typical usage arises when the IGS organization setup forms need to present the list of note types available for a given organizational level. Because the ETRM documentation cautions against querying the view directly, a defensive approach is to select from the base table APPS.IGS_OR_ORG_NOTE_TYPE whenever possible. Where the view must be used, a standard query is:

• Retrieving all note types for display:
  SELECT ORG_NOTES_TYPE, NOTE_TYPE_DESCRIPTION, INST_FLAG, UNIT_FLAG, LOCATION_FLAG FROM APPS.IGS_OR_ORG_NOTE_TYPE_V;
• Filtering to note types applicable to organizational units:
  SELECT ORG_NOTES_TYPE, NOTE_TYPE_DESCRIPTION FROM APPS.IGS_OR_ORG_NOTE_TYPE_V WHERE UNIT_FLAG = 'Y';
• Filtering to institution-level note types:
  SELECT ORG_NOTES_TYPE, NOTE_TYPE_DESCRIPTION FROM APPS.IGS_OR_ORG_NOTE_TYPE_V WHERE INST_FLAG = 'Y';

Because the object is not referenced by any other database object, there are no dependencies to break from downstream code; however, any custom code extended against this view should be reviewed against each patch or upgrade, since Oracle's stated position is that the view may change dramatically between releases.