Search Results igs_re_thesis_result




Overview
Explore in AI Chat

Overview

IGS_RE_THESIS_RESULT is a reporting and integration view within the Oracle E-Business Suite IGS (Student System) module. It exposes thesis result reference data — the coded lookup values used to record the outcome of a student's thesis, dissertation, or comparable research requirement. In the ETRM documentation set for release 12.2.2, the object is classified under "IGS - Student System (Obsolete)," and the implementation notes state that it is "Not implemented in this database." The view therefore exists as a documented schema object definition rather than as an active, populated artifact in the reference environment. Its role in EBS reporting and integration is nonetheless well defined: it presents a single, OU-filtered projection of thesis result codes so that concurrent programs, Oracle Reports, OAF pages, and external interfaces can resolve a stored code into a human-readable description without querying the underlying transaction-owner table directly.

Underlying Base Objects

The view text is defined entirely over one base table, IGS_RE_THESIS_RESULT_ALL. The ETRM metadata records no additional referenced base objects, and the SELECT list maps each view column to a similarly named column in the base table, plus a synthesized ROW_ID derived from TAB.ROWID. Because the base table carries the _ALL suffix, it is an organization-enabled (multi-org) table, and the view supplies the standard EBS organizational security predicate. That predicate compares the table's ORG_ID against the operating unit returned by USERENV('CLIENT_INFO'): the first ten bytes of CLIENT_INFO are parsed and converted to a number, with a single leading space treated as NULL, and NVL logic substitutes -99 so that rows with a null ORG_ID resolve consistently. The result is that each query returns only the thesis result codes visible to the caller's current operating unit, which is the conventional mechanism by which IGS lookup views enforce multi-org access.

Key Columns

  • ROW_ID — the base table ROWID, providing a stable physical row identifier for the exposed record.
  • ORG_ID — the operating unit that owns the thesis result code; the driving column of the view's security filter.
  • THESIS_RESULT_CD — the primary business key, a coded value representing a thesis outcome. This is the value stored on student thesis records.
  • DESCRIPTION — the translated, user-facing text for the code, and the column most frequently selected by reports.
  • S_THESIS_RESULT_CD — the system-level or seeded variant of the thesis result code, typically the value shipped by Oracle and used to distinguish delivered codes from institution-defined ones.
  • CLOSED_IND — a flag indicating whether the result code is inactive; closed codes should be excluded from new data entry lists.
  • COMMENTS — free-form descriptive text attached to the code.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit columns capturing who created and last modified the row, when, and through which login.

Common Use Cases and Queries

Typical usage is to populate a validation list on a thesis entry form, to supply a parameter list of values for a report on thesis outcomes, or to join descriptive text onto thesis transaction data for extracts. The following query returns the active, OU-visible thesis result codes ordered for display:

SELECT thesis_result_cd, description, s_thesis_result_cd
FROM igs_re_thesis_result
WHERE NVL(closed_ind, 'N') = 'N'
ORDER BY description;

Where the view returns no rows — as the ETRM note "Not implemented in this database" anticipates — the equivalent data can be retrieved from the base table for the appropriate organization. Any integration extract that must be portable across environments should reference the view rather than hard-code IGS_RE_THESIS_RESULT_ALL, since the view already applies the multi-org predicate and spares the calling code from reproducing the CLIENT_INFO parsing logic.