Search Results igs_ps_usec_occurs_pkg




Overview
Explore in AI Chat

Overview

IGS_PS_USEC_OCCURS_PKG is a table-handler package in the Oracle EBS Student Systems (IGS) product family. Its name derives from the IGS_PS_USEC_OCCURS entity, which stores the scheduled occurrences of unit section offerings — that is, the individual dated instances in which a section of a unit (course) is delivered during an academic period. The package body encapsulates the standard Oracle Forms server-side DML interface for that entity, exposing the conventional INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW, and ADD_ROW entry points together with supporting validation and defaulting routines. It also carries domain-specific logic: verifying that a mandatory reference code type is present on an occurrence record, and defaulting the occurrence's reference code. The header comment identifies the original author and a 2000 creation date, with change history extending through 2002 and a shipped revision dated 2005. In the ETRM 12.1.1 classification the package is registered as OTHER rather than as a public API, and it is cited as being referenced by thirteen other packages, indicating it sits within the internal call graph of the IGS scheduling modules rather than at the application boundary.

Key Procedures and Functions

The documented interface comprises twelve procedures and functions. The core DML set is INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW, which respectively create, modify, remove, and pessimistically lock the IGS_PS_USEC_OCCURS row identified by the caller's primary key. ADD_ROW performs the Forms-style row creation that precedes an insert. GET_PK_FOR_VALIDATION, GET_UK_FOR_VALIDATION, and GET_UFK_IGS_PS_UNIT_OFR_OPT retrieve the primary key, unique key, and user foreign key values used by the client to resolve and validate a record before submission. GET_FK_IGS_AD_BUILDING and GET_FK_IGS_AD_ROOM perform referential lookups against the address building and room entities that describe where an occurrence is held. CHECK_CONSTRAINTS centralises the entity's business and integrity checks, and BEFORE_DML is the pre-DML trigger entry point that dispatches to the appropriate insert, update, or delete logic. Beyond the documented set, the package body contains private helpers including BeforeRowInsertUpdatedelete1, which opens the cur_ref_cd cursor joining IGS_PS_USEC_OCUR_REF_V to IGS_PS_USEC_OCCURS_ALL by unit_section_occurrence_id, and calls igs_ps_val_atl.chk_mandatory_ref_cd to raise the IGS_PS_REF_CD_MANDATORY message. The procedure Dflt_usec_occur_ref_code supplies the default reference code, with enhanced cursor filtering on restricted_flag and closed_id.

Tables Accessed

The package performs its primary insert, update, delete, and lock operations against IGS_PS_USEC_OCCURS_ALL, the base table for unit section occurrences. IGS_PS_USEC_OCCURS_S is the corresponding sequence source used to populate the primary key on insert. IGS_GE_REF_CD is the general reference code table, consulted to validate and default the reference code type associated with an occurrence. DUAL is used for key and validation lookups that require no table access. The reference-code cursor additionally reads the IGS_PS_USEC_OCUR_REF_V view alongside the base table.

Usage Notes

Because this is a Forms-oriented table handler, it is invoked through Oracle Forms triggers and server-side PL/SQL blocks that maintain unit section occurrence data, typically the occurrence scheduling forms within the IGS institution and scheduling responsibility. The BEFORE_DML and CHECK_CONSTRAINTS entry points should be called in sequence by any custom code that manipulates the table directly, so that mandatory reference-code validation and the standard audit column maintenance are applied. Direct inserts or updates that bypass the package risk producing occurrence records without a valid reference code type. The package is not intended for external integration; callers needing an open interface should use the published IGS public APIs instead. Developers extending the package should note the 2005 baseline revision and the Enh#2613933 and Enh#2858431 change references, which document the mandatory reference-code enforcement and the restricted_flag/closed_id filtering added to the defaulting cursor.