Results for “igs_re_thesis”

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

Overview

IGS_RE_THESIS is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 view owned by the APPS schema within the IGS (Student System) product family. It exposes research thesis data maintained by higher-education institutions, including thesis titles, submission and lodgement dates, examination results, and publication embargo information. The view is a secured, operational-layer reporting interface rather than a base table; it presents the organization-filtered row set for the current session and shields callers from the underlying multi-org partitioning logic of its parent table.

From a reporting and integration standpoint, IGS_RE_THESIS is the recommended access point for external reports, extracts, and interfaces that must respect Oracle Multi-Org Access Control (MOAC). Because the view resolves the active organization from the session's CLIENT_INFO setting, any consumer querying it sees only the thesis records for the organization(s) the connecting responsibility is authorized to access. The embargo_expiry_dt column, which the user specifically searched for, is exposed directly by this view, making it the standard target for queries about thesis publication embargo periods.

Underlying Base Objects

The documented view definition selects from a single base object, IGS_RE_THESIS_ALL, aliased as TAB. The view text projects the base table's ROWID as ROW_ID along with its principal business columns, and applies a WHERE clause on ORG_ID. That predicate compares the base table's ORG_ID against the value parsed from USERENV('CLIENT_INFO'); when CLIENT_INFO is not populated, both sides of the comparison resolve to NULL and are coalesced to the sentinel value -99, so that records with a NULL ORG_ID remain visible.

This is the classic Oracle-seeded multi-org view pattern: IGS_RE_THESIS_ALL holds all operating-unit rows, while IGS_RE_THESIS performs the policy enforcement and presents only the rows the session is entitled to see. The view itself stores no data; all reads and writes are delegated to the base table.

Key Columns

• ROW_ID — the ROWID of the base-table row, used for row identification by Oracle Forms and certain integration patterns.
• ORG_ID — the operating unit that owns the thesis record; drives the multi-org filter.
• PERSON_ID — identifies the student (person) associated with the thesis.
• CA_SEQUENCE_NUMBER / SEQUENCE_NUMBER — keys used to relate the thesis to the student's course attempt and to its own registration sequence.
• TITLE, FINAL_TITLE_IND, SHORT_TITLE, ABBREVIATED_TITLE — the thesis title and its variants, together with the indicator of whether the title is final.
• THESIS_RESULT_CD — the coded outcome of thesis examination.
• EXPECTED_SUBMISSION_DT, LIBRARY_LODGEMENT_DT — the expected submission date and the date the thesis was lodged with the library.
• LIBRARY_CATALOGUE_NUMBER — library-assigned reference number for the deposited thesis.
• EMBARGO_EXPIRY_DT — the date on which any publication embargo on the thesis expires; until this date the thesis may be withheld from public release.
• EMBARGO_DETAILS — descriptive text recording the terms or reasons for the embargo.
• THESIS_FORMAT, THESIS_TOPIC, CITATION, COMMENTS — presentation format, subject matter, citation string, and free-text remarks.
• LOGICAL_DELETE_DT — soft-delete timestamp; rows with a populated value are logically removed rather than physically deleted.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include identifying theses whose embargo period is about to lapse so that repository access can be released, tracking outstanding library lodgements, and extracting examination results for reporting. A representative query for embargo management follows:

SELECT person_id, title, library_lodgement_dt, embargo_expiry_dt
FROM apps.igs_re_thesis
WHERE embargo_expiry_dt IS NOT NULL
AND embargo_expiry_dt <= SYSDATE
AND logical_delete_dt IS NULL;

For upcoming embargo expirations within a window, the predicate can be adjusted to BETWEEN SYSDATE AND SYSDATE + 30. Because the view enforces MOAC automatically, no additional ORG_ID filter is required in these statements, provided the connecting responsibility has the intended organization context set.