Search Results thesis_result

Overview

IGS_RE_THESIS_RESULT_V is a supplementary (non-materialized) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGS.IGS_RE_THESIS_RESULT_V. It is delivered as part of the Oracle Student System (formerly Oracle iLearning/Student Records) module, specifically within the research and thesis tracking (IGS_RE) functional area. Its stated purpose is to simplify forms coding for thesis result lookup windows, consolidating the base thesis result table with lookup-driven meaning and description attributes so that Forms blocks and List of Values (LOV) components can be populated from a single, denormalised source.

Oracle's ETRM documentation explicitly cautions that this is a supplementary view intended to simplify forms coding, and that Oracle does not recommend querying or altering data through it. Because its definition may change dramatically across minor or major releases, custom reporting or integration code should avoid hard dependencies on its column list or joins. In practice the view functions as a lightweight reference layer over the authoritative thesis result code table, exposing decoded display text alongside the coded value.

Underlying Base Objects

According to the documented dependency information, APPS.IGS_RE_THESIS_RESULT_V references the following objects:

• IGS_RE_THESIS_RESULT — the base (primary) table holding thesis result records, including the result code, description, closed indicator, comments, and the FINAL_RESULT_IND flag.
• IGS_LOOKUPS_VIEW — the standard IGS lookup view used to decode lookup codes into their user-facing meanings, supplying the MEANING column and related translated attributes.

The view joins these two sources so that each thesis result row also carries the decoded lookup meaning. No other database object references this view, confirming it is a terminal reporting helper rather than a component of a larger dependency chain. The documented metadata does not expose the precise join predicate; practitioners should treat IGS_RE_THESIS_RESULT as the system of record.

Key Columns

• THESIS_RESULT_CD (VARCHAR2 10) — the coded thesis result value, the primary business key for a result type.
• DESCRIPTION (VARCHAR2 60) — human-readable description of the thesis result.
• MEANING (VARCHAR2 80) — decoded lookup meaning associated with the result code, typically the value displayed in LOVs and forms.
• FINAL_RESULT_IND (VARCHAR2) — indicator distinguishing whether a given thesis result represents a final outcome; this is the column the user searched for.
• CLOSED_IND (VARCHAR2) — flag indicating whether the result code is closed/inactive and therefore unavailable for new assignments.
• S_THESIS_RESULT_CD (VARCHAR2 30) — system (internal) result code, generally used for integration or legacy mapping.
• COMMENTS (VARCHAR2 2000) — free-form notes attached to the result definition.
• ROW_ID (ROWID) and the standard WHO/audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

This view is most often used to drive LOVs and forms validation in thesis result maintenance, to filter only final-outcome results, and to reconcile lookup meanings against stored codes.

• All active thesis results: SELECT thesis_result_cd, description, meaning FROM apps.igs_re_thesis_result_v WHERE NVL(closed_ind,'N') = 'N';
• Final results only: SELECT thesis_result_cd, description FROM apps.igs_re_thesis_result_v WHERE final_result_ind = 'Y';
• Lookup reconciliation: compare MEANING against IGS_LOOKUPS_VIEW values to detect uncustomised or orphaned result codes.
• Forms LOV usage: the view is queried by the thesis result block to populate list items and validation handlers.

Because Oracle warns that the view may change without notice, production integrations should query the base table IGS_RE_THESIS_RESULT directly and resolve meanings through IGS_LOOKUPS_VIEW where stable behaviour is required.