Results for “igs_as_std_exm_instn_pkg”

21 results




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

Overview

The PL/SQL package body APPS.IGS_AS_STD_EXM_INSTN_PKG is a core component of the Oracle E-Business Suite (EBS) Student System (IGS) product family, specifically within the Assessment (AS) module. Its primary business function is to manage the association between a student and an examination instance — that is, the record of an individual student's sitting of a particular examination. This entity is stored in the underlying table IGS_AS_STD_EXM_INSTN_ALL, and the package encapsulates the DML logic required to insert, update, lock, and delete these records. The package also enforces referential integrity and validation rules that link students' examination instances to examination instances, examination sessions, and student attempt items. As a validated object in the APPS schema, it serves as a governed data-access layer that shields callers from direct manipulation of the base tables.

Key Procedures and Functions

The ETRM metadata documents twelve procedures and functions in this package body, each fulfilling a specific role in the lifecycle of a student examination instance record:

  • INSERT_ROW — Performs the physical insert of a new student examination instance record into the base table.
  • LOCK_ROW — Acquires a row-level lock on an existing record to prevent concurrent modification during a transaction.
  • UPDATE_ROW — Applies changes to an existing student examination instance record.
  • ADD_ROW — Or higher-level entry point that orchestrates validation and insertion logic for a new record.
  • DELETE_ROW — Removes an existing student examination instance record.
  • GET_PK_FOR_VALIDATION — Retrieves the primary key value used to validate against the underlying table.
  • GET_UK_FOR_VALIDATION — Retrieves the unique key value used for uniqueness validation.
  • GET_FK_IGS_AS_EXAM_INSTANCE — Resolves the foreign key relationship to the examination instance entity.
  • GET_UFK_IGS_AS_EXAM_SESSION — Resolves the alternative unique foreign key relating to the examination session.
  • GET_FK_IGS_AS_SU_ATMPT_ITM — Resolves the foreign key linking to the student attempt item.
  • CHECK_CONSTRAINTS — Validates business and schema constraints before committing DML operations.
  • BEFORE_DML — A trigger-style routine invoked prior to insert, update, or delete to enforce pre-DML validation and auditing.

Tables Accessed

The package operates against two documented base tables accessed through APPS synonyms, along with the DUAL utility table:

  • IGS_AS_STD_EXM_INSTN_ALL — The primary base table holding student examination instance records. The package inserts, updates, locks, and deletes rows here via its DML procedures.
  • IGS_AS_STD_EXM_INSTN_ALL_S — The sequence table associated with the base table, used to generate primary key values via IGS_GE_NUMBER and the sequence access routine.
  • DUAL — Used for single-row evaluations during validation and key retrieval logic.

Additional dependency objects include IGS_AS_EXAM_INSTANCE_PKG, IGS_AS_EXAM_SESSION_PKG, and IGS_AS_SU_ATMPT_ITM_PKG, which supply validated foreign key information, together with utility packages such as IGS_AS_VAL_SEI, IGS_GE_MSG_STACK, FND_MESSAGE, and APP_EXCEPTION for error handling and messaging.

Usage Notes

This package is not referenced by any other database object at the schema level, meaning it is invoked explicitly rather than through automatic dependency chains. It is typically called from the Assessment module's Oracle Forms interfaces, from concurrent programs that seed or maintain student examination instance data, or from custom PL/SQL code performing bulk operations. The presence of CHECK_CONSTRAINTS and BEFORE_DML indicates that callers should always route DML through the package rather than writing directly to IGS_AS_STD_EXM_INSTN_ALL, since the package enforces foreign key validation against examination instances, sessions, and attempt items as well as the standard WHO-column and messaging conventions. In EBS 12.1.1 and 12.2.2, the package remains valid and can be safely referenced from customizations by calling the documented public procedures.