Search Results igs_ad_ter_ed_uni_at_pkg

Overview

IGS_AD_TER_ED_UNI_AT_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that belongs to the Student Systems (IGS) product family, specifically the Academic Data (AD) module dealing with term-level educational data. The object name decomposes into recognizable IGS conventions: "AD" for Academic Data, "TER" for term, "ED" for education, "UNI" for university, and "AT" indicating an attribute or association table. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package functions as the underlying programmatic handler for the IGS_AD_TER_ED_UNI_AT entity, which stores term-specific university education attributes associated with a student's prior or current academic record.

The package is classified as an OTHER API in the E-Business Suite Technical Reference Manual (ETRM). It is not a public, externally supported application programming interface; rather, it is an internal implementation package that encapsulates the data manipulation logic, validation, and referential integrity rules for its base table. It sits within the dependency chain of higher-level IGS academic packages and provides row-level operations that those packages invoke through standard Oracle Forms or PL/SQL processing.

Key Procedures and Functions

The ETRM documents ten callable units within this package. Their functions are as follows:

• INSERT_ROW — Inserts a new record into the IGS_AD_TER_ED_UNI_AT table, populating the entity's attributes.
• UPDATE_ROW — Modifies an existing record, applying the appropriate business validations before the change is persisted.
• DELETE_ROW — Removes a record from the base table, typically invoked after the owning record is deleted.
• LOCK_ROW — Acquires a row-level lock to support optimistic concurrency control during multi-user update transactions.
• ADD_ROW — Provides an alternate or composite add path, generally used by calling packages to append detail records against a parent education or term record.
• GET_PK_FOR_VALIDATION — Retrieves a primary key value so that dependent validation logic can confirm referential relationships before a DML operation proceeds.
• CHECK_CONSTRAINTS — Validates the record against the table's foreign-key and business constraints before committing changes.
• GET_FK_IGS_PS_DSCP — Returns the foreign-key reference to the IGS_PS_DSCP entity (program or discipline descriptor), supporting lookup and validation in both directions.
• GET_FK_IGS_AD_TER_EDU — Returns the foreign-key reference to the IGS_AD_TER_EDU entity (term-level education record), establishing the parent-child link for this attribute table.
• BEFORE_DML — A trigger-style pre-processing routine that executes standard housekeeping, such as stamping WHO audit columns, before the INSERT/UPDATE/DELETE operations run.

Parameter lists are not published in the ETRM excerpt and should be confirmed against the live package specification in the target environment.

Tables Accessed

The package operates exclusively on one documented base table, IGS_AD_TER_ED_UNI_AT, accessed through the APPS synonym in the APPS schema. This table holds the term education university attribute rows, with foreign keys to IGS_AD_TER_EDU (the parent term education record) and IGS_PS_DSCP (the discipline/program descriptor). All ten procedures and functions are oriented around maintaining records in this single table, with the GET_FK routines performing reads against the related parent and descriptor entities to enforce and expose referential values.

Usage Notes

IGS_AD_TER_ED_UNI_AT_PKG is referenced by two other packages in the environment:

• IGS_AD_TER_EDU_PKG — the parent term-education package, which calls the child attribute routines when managing a complete education record.
• IGS_PS_DSCP_PKG — the program/discipline descriptor package, which interacts with the descriptor foreign-key routines.

Typical invocation occurs through Oracle Forms-based maintenance of the term education setup data, where the form's block triggers delegate insert, update, delete, and lock operations to this package rather than touching the table directly. Because it is classified as an OTHER (internal) API, it should not be called from standalone custom code unless the IGS data model requires it, and any such usage should mirror the calling sequence followed by the two dependent packages. The BEFORE_DML logic ensures audit consistency, and CHECK_CONSTRAINTS should always be honored before committing, since bypassing validation could leave orphaned attribute rows. In 12.1.1 and 12.2.2 the object is reported VALID; however, standard EBS patching and product maintenance may regenerate the package body, so custom extensions should be applied as wrapper logic rather than direct modification.