Search Results igs_re_cdt_att_hist_pkg




Overview
Explore in AI Chat

Overview

The APPS.IGS_RE_CDT_ATT_HIST_PKG package body is a procedural component of the Oracle E-Business Suite (EBS) Student System (IGS) product family, specifically within the Recruitment and Admissions (IGS_RE) module. It manages the persistent representation of candidate attendance history records — the historical trail of attendance-related events attached to an applicant or candidate record before that candidate becomes a registered student.

The package follows the standard Oracle Forms-generated table handler (TAPI) pattern, providing a controlled, validated interface for insert, update, delete, and locking operations against the underlying attendance history table. Rather than permitting direct DML against the base table, the Student System routes changes through this package so that foreign key relationships, validation routines, and message-stack conventions are consistently applied. The package is declared with a classification of OTHER in the ETRM register and is currently VALID in the APPS schema.

Key Procedures and Functions

The package exposes ten documented procedures and functions, forming the canonical table-handler API:

  • INSERT_ROW — Performs a validated insert of a new candidate attendance history row, populating mandatory columns and invoking before-DML logic.
  • LOCK_ROW — Acquires a row-level lock on the specified attendance history record to support concurrent edit sessions, typically returning the locked row for display.
  • UPDATE_ROW — Applies changes to an existing attendance history row after re-validation.
  • ADD_ROW — Provides the higher-level, Forms-facing entry point that orchestrates a new record creation, delegating to the insert logic.
  • DELETE_ROW — Removes an attendance history row, subject to referential and validation checks.
  • GET_PK_FOR_VALIDATION — Resolves or exposes the primary key of the record under validation, enabling downstream validation routines to confirm identity.
  • GET_FK_IGS_EN_ATD_TYPE — Retrieves and validates the foreign key reference to the attendance type definition, linking the history row to a valid attendance type.
  • GET_FK_IGS_RE_CANDIDATURE — Retrieves and validates the foreign key reference to the candidate candidature, establishing the owning applicant context.
  • CHECK_CONSTRAINTS — Enforces business and referential constraints before committing a DML operation.
  • BEFORE_DML — The pre-DML hook that standardizes WHO-column stamping, defaulting, and cross-field validation for all row operations.

Tables Accessed

The package reads from and writes to IGS_RE_CDT_ATT_HIST_ALL, the multi-org (_ALL) table that stores candidate attendance history records. This is the sole base table documented against the package body. The _ALL suffix indicates the table is partitioned by operating unit and is accessed via the APPS synonym layer, reinforcing that all manipulation must occur within the APPS schema context.

Supporting data used during validation is obtained through dependencies rather than direct table joins. The package depends on IGS_EN_ATD_TYPE_PKG and IGS_RE_CANDIDATURE_PKG to resolve and validate the two foreign keys described above, and on IGS_EN_STDNT_PS_ATT as a related entity. Validation helpers such as IGS_AS_VAL_SUAAP, IGS_RE_VAL_CAH, and IGS_SC_GEN_001 supply institutional validation rules, while IGS_GE_MSG_STACK, IGS_GE_NUMBER, and IGS_GE_GEN_003 provide the messaging, numbering, and generic utilities standard across the Student System.

Error handling is routed through APP_EXCEPTION and FND_MESSAGE, with FND_GLOBAL supplying the application and session context. The package references no database object that in turn references it, but it is itself referenced by five other packages, confirming its role as a shared, low-level table handler.

Usage Notes

IGS_RE_CDT_ATT_HIST_PKG is invoked in the same manner as other Oracle Forms table handlers. In the standard EBS 12.1.1 / 12.2.2 runtime it is called from the Recruitment and Admissions forms that maintain candidate attendance history, where the form triggers (pre-insert, pre-update, on-lock, on-delete) delegate to ADD_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW respectively. Because it is referenced by five additional packages, it may equally be called from custom PL/SQL that needs to create or amend attendance history records without opening a form.

Best practice is to invoke these procedures only through the documented entry points rather than issuing direct DML against IGS_RE_CDT_ATT_HIST_ALL, since BEFORE_DML and CHECK_CONSTRAINTS enforce WHO-column stamping, operating-unit context, and cross-field consistency. Any custom code must run in the APPS schema, supply a valid FND_GLOBAL session, and inspect the IGS_GE_MSG_STACK or handle APP_EXCEPTION for error reporting. Given the package is marked VALID and its dependents are stable, it should be treated as a supported extension point within the IGS_RE integration surface.