Results for “get_fk_igs_re_thesis_result”

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

Overview

IGS_RE_THESIS_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the Student System (IGS) product family as an "OTHER" API. In EBS 12.1.1 and 12.2.2 it provides the core programmatic interface for maintaining thesis records held by higher-education institutions within the Research and Thesis Tracking (RE) module. The package encapsulates the DML operations required to create, modify, lock, and delete thesis rows in the underlying IGS_RE_THESIS_ALL table, applying the institution's validation rules before any change is committed. It underpins the thesis maintenance forms and any integrated processes that register a candidate's thesis, link it to a candidature, and record its examination results. Because it is a table-handler style package, its primary role is to centralize business validation, message stack control, and row-level locking for thesis data rather than to expose a standalone business transaction.

Key Procedures and Functions

The package exposes ten documented procedures and functions that together form a conventional table-handler API:

• INSERT_ROW — inserts a new thesis record into IGS_RE_THESIS_ALL with validation applied.
• UPDATE_ROW — updates an existing thesis row identified by its primary key.
• DELETE_ROW — removes a thesis record, subject to referential and status checks.
• LOCK_ROW — issues a row-level lock (SELECT FOR UPDATE) to serialize concurrent edits.
• ADD_ROW — a wrapper of the insert path that adds a row and returns the generated primary key.
• GET_PK_FOR_VALIDATION — resolves the primary key required to validate the current row state.
• GET_FK_IGS_RE_CANDIDATURE — derives the candidature foreign key so the thesis is correctly linked to its candidate.
• GET_FK_IGS_RE_THESIS_RESULT — derives the thesis result foreign key used when recording outcomes.
• CHECK_CONSTRAINTS — enforces the package-level business rules and referential integrity before DML.
• BEFORE_DML — a pre-DML hook that standardizes validation, WHO-column population, and message handling.

Tables Accessed

The only documented table referenced via APPS synonyms is IGS_RE_THESIS_ALL, the base entity table for thesis records. All insert, update, delete, and lock operations converge on this table. The package also references views and supporting objects including IGS_RE_THESIS, IGS_RE_THESIS_V, and IGS_RE_THESIS_ALL surrogates, and it depends on IGS_RE_CANDIDATURE_PKG, IGS_RE_THESIS_EXAM_PKG, IGS_RE_THESIS_RESULT_PKG, IGS_RE_VAL_THE, IGS_RE_GEN_002, IGS_RE_GEN_003, IGS_RE_WORKFLOW, and IGS_AS_VAL_SUAAP for validation, result handling, workflow, and message management. Utility dependencies include APP_EXCEPTION, FND_GLOBAL, FND_MESSAGE, IGS_GE_DATE, IGS_GE_MSG_STACK, IGS_GE_NUMBER, IGS_SC_GEN_001, and STANDARD.

Usage Notes

IGS_RE_THESIS_PKG is typically invoked from the Oracle Forms thesis maintenance screens, which call LOCK_ROW, INSERT_ROW, UPDATE_ROW, and DELETE_ROW through the standard table-handler pattern. It is also referenced by seven other database packages, notably the thesis examination, thesis result, and candidature packages, so custom code that manipulates thesis data should route through this API rather than writing to IGS_RE_THESIS_ALL directly. FND_GLOBAL supplies WHO columns; FND_MESSAGE and IGS_GE_MSG_STACK handle errors. The package is not referenced by any further database object, confirming it is an upper-layer API. No public synonym entries or grants beyond APPS are documented.