Results for “final_title_ind”

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

Overview

The IGS_RE_THESIS_V view belongs to the IGS (Student System) product family within Oracle E-Business Suite, a module designated as obsolete in the current release documentation. The view was originally authored to support the thesis maintenance forms within the Oracle Student System, providing a consolidated projection that surfaces both stored columns from the thesis entity and derived, virtual columns computed at query time. Its principal design objective was to spare form-level logic from repeatedly reconstructing calculated values such as thesis status and a logical delete indicator; instead, these expressions are embedded directly in the view definition so that the maintenance forms can bind and display them with minimal application code.

Because the view is not implemented in the current database, it exists only as documented metadata in the ETRM repository for releases 12.1.1 and 12.2.2. No runtime object is present, and no referenced base objects are recorded in the documented metadata beyond the single table appearing in the view text. This view therefore has no active role in production reporting or integration in the modern EBS stack; it is retained for historical reference, upgrade archaeology, and impact analysis when legacy customizations are encountered.

Underlying Base Objects

The only object referenced by the view text is the table IGS_RE_THESIS, aliased as THES. The SELECT list projects columns directly from that table and adds two computed expressions that are not physical columns. The documented metadata records no other base objects, and no owner is listed, reflecting the fact that the object is not instantiated. For environments where the legacy object may still exist, the effective dependency set would consist of IGS_RE_THESIS plus the PL/SQL function IGS_RE_GEN_002.RESP_GET_THE_STATUS, invoked within the view text.

Key Columns

• PERSON_ID, CA_SEQUENCE_NUMBER, SEQUENCE_NUMBER — the composite identifier linking a thesis record to a person and its contextual and sequential position.
• TITLE, SHORT_TITLE, ABBREVIATED_TITLE, FINAL_TITLE_IND — descriptive attributes of the thesis, including the indicator of whether the title is final.
• THESIS_STATUS — a virtual column computed by calling IGS_RE_GEN_002.RESP_GET_THE_STATUS, passing person, contextual sequence, sequence, a literal 'Y', the logical delete date, and the thesis result code. This is the derived status the maintenance forms display.
• THESIS_RESULT_CD — the raw result code stored on the base table, supplied as an input to the status function.
• EXPECTED_SUBMISSION_DT, LIBRARY_LODGEMENT_DT, LIBRARY_CATALOGUE_NUMBER — submission and lodgement tracking attributes.
• EMBARGO_EXPIRY_DT, EMBARGO_DETAILS — embargo information governing restrictions on thesis access.
• THESIS_FORMAT, THESIS_TOPIC, CITATION, COMMENTS — free-form and descriptive content associated with the thesis.
• LOGICAL_DELETE_INCLUDE_IND — a virtual column using DECODE(NVL(LOGICAL_DELETE_DT, NULL), NULL, 'N', 'Y'), yielding 'N' when no logical delete date exists and 'Y' otherwise.
• LOGICAL_DELETE_DT — the logical deletion timestamp on the base record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns carried through unchanged.

Common Use Cases and Queries

Historically, the primary use case was thesis maintenance form support: forms queried this view to display the computed thesis status and logical delete indicator without reimplementing the derivation logic. Reporting scenarios would query the view to obtain a person's thesis list with status and embargo detail in a single pass.

A representative query mirrors the view's own projection, for example selecting PERSON_ID, SEQUENCE_NUMBER, TITLE, THESIS_STATUS, THESIS_RESULT_CD, EXPECTED_SUBMISSION_DT, EMBARGO_EXPIRY_DT, and LOGICAL_DELETE_INCLUDE_IND from IGS_RE_THESIS_V, filtered by PERSON_ID and ordered by CA_SEQUENCE_NUMBER and SEQUENCE_NUMBER. Because the object is documented as not implemented, such queries should be validated against the actual database before reliance; where the view is absent, equivalent logic must be reconstructed directly over IGS_RE_THESIS and the RESP_GET_THE_STATUS function.