Search Results igs_or_org_note_type_v




Overview
Explore in AI Chat

Overview

IGS_OR_ORG_NOTE_TYPE_V is a reporting view within the Oracle E-Business Suite IGS (Student System) product family. In EBS 12.1.1 and 12.2.2 the IGS module is classified as obsolete, and this view is documented in the ETRM (E-Business Suite Technical Reference Manual) repository for metadata reference purposes. The view is described in the product documentation with the note "Not implemented in this database," meaning no physical database object definition was shipped or created in the reference environment from which the documentation was generated.

Functionally, the view presents configuration data describing organization note types in the Student System. It exposes the note type identifier, its description, and a set of applicability flags that determine whether a given note type applies at the institution, unit, or location level. Because it is a pass-through view over a single base table, it serves as a denormalized read layer for reporting and integration consumers who need a stable, named interface rather than accessing the underlying table directly.

Underlying Base Objects

The view is defined over one documented base object: the table IGS_OR_ORG_NOTE_TYPE, aliased as ONT in the view text. The view text is a straightforward projection with no joins, unions, or aggregations:

No additional referenced base objects are documented in the ETRM metadata. The mapping is one-to-one: every column in the view corresponds directly to a column of IGS_OR_ORG_NOTE_TYPE, plus the pseudo-column ROWID surfaced as ROW_ID.

Key Columns

  • ROW_ID — The ROWID of the underlying table row, exposed as an identifier for the source record. Useful for direct row addressing and for reconciliation back to the base table.
  • ORG_NOTES_TYPE — The primary business key; the short code identifying the organization note type.
  • NOTE_TYPE_DESCRIPTION — The descriptive text for the note type, suitable for display in reports and LOVs.
  • INST_FLAG — Indicates whether the note type is applicable at the institution level. This is the column most commonly associated with the "inst_flag" search term, and it is the primary applicability switch for institution-wide notes.
  • UNIT_FLAG — Indicates applicability at the organizational unit level.
  • LOCATION_FLAG — Indicates applicability at the location level.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each row and when.

The three FLAG columns together define the valid contexts in which a note type may be used, making them the critical filtering attributes for any query.

Common Use Cases and Queries

The principal use case is extracting the catalogue of organization note types and their applicability flags, either for configuration review or as reference data for downstream integration. A typical query listing all active institution-level note types is:

  • SELECT ORG_NOTES_TYPE, NOTE_TYPE_DESCRIPTION, INST_FLAG, UNIT_FLAG, LOCATION_FLAG FROM IGS_OR_ORG_NOTE_TYPE_V WHERE INST_FLAG = 'Y';

To audit changes to the configuration, the standard audit columns support delta extraction:

  • SELECT ORG_NOTES_TYPE, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM IGS_OR_ORG_NOTE_TYPE_V WHERE LAST_UPDATE_DATE >= :p_since;

Because the metadata states the view is not implemented in the documented database, any query against it will fail with an ORA-00942 until the object is created. Consumers should confirm object existence in the target environment and, where the view is absent, query IGS_OR_ORG_NOTE_TYPE directly using the same column list documented above.