Results for “igs_ps_awd_pkg”

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

Overview

The PL/SQL package body APPS.IGS_PS_AWD_PKG is a core table-handler (or "TAPI" — Table API) in the Oracle E-Business Suite Student Information / Student Records model, belonging to the IGS (Institution of Higher Education / Student Systems) product family. It provides the programmatic interface to the IGS_PS_AWD base table, which stores award definitions — the qualifications, degrees, diplomas, and certificates that an institution offers and that a student can be enrolled toward. The package centralizes the insert, update, locking, and validation logic for award records so that every consumer of the underlying table observes consistent business rules, rather than bypassing them through direct DML.

In Oracle EBS release 12.1.1 (and equivalently 12.2.2), the object carries a status of VALID in the APPS schema and is classified under ETRM as an API of type OTHER. It conforms to the standard Oracle "C" (Table Handler) API pattern, exposing row-level operations together with constraint and foreign-key validation routines used by the surrounding forms and packages.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions within this package body:

• INSERT_ROW — Performs the physical insert of a new award record into IGS_PS_AWD. This is the low-level DML routine invoked after validation has succeeded.
• UPDATE_ROW — Applies changes to an existing award record, updating the columns of the affected row.
• LOCK_ROW — Acquires a row-level lock on the target award record, guarding against concurrent modification during an edit transaction.
• ADD_ROW — The primary create entry point. It orchestrates validation (including the constraint checks below) before delegating to INSERT_ROW, and is the procedure most commonly called by external code and forms.
• GET_PK_FOR_VALIDATION — Returns the primary key of the award row so that dependent validation and constraint routines can operate against a specific record.
• GET_FK_IGS_GR_TESTAMUR_TYPE — Resolves the foreign-key relationship to the test-amendment/duration type entity, used to validate that the referenced type value is legitimate before persistence.
• GET_FK_IGS_AS_GRD_SCHEMA — Resolves the foreign-key relationship to the grading schema, ensuring that an award is tied to a valid grade scheme.
• CHECK_CONSTRAINTS — Central routine that validates all required columns and business constraints on an award record prior to insert or update.
• BEFORE_DML — A pre-DML hook that executes standard housekeeping, such as populating WHO columns (created/updated by, dates) via FND_GLOBAL, issuing error messages through FND_MESSAGE and IGS_GE_MSG_STACK, and preparing the record for the subsequent DML operation.

Tables Accessed

The package operates on IGS_PS_AWD, accessed through its APPS synonym. This is the award master table and is the sole documented table read from or written to by the package. Inserts and updates are directed here by INSERT_ROW and UPDATE_ROW; primary-key and foreign-key lookups (GET_PK_FOR_VALIDATION, GET_FK_IGS_GR_TESTAMUR_TYPE, GET_FK_IGS_AS_GRD_SCHEMA) read from the table and its related reference entities to confirm referential integrity before the award record is committed.

Usage Notes

IGS_PS_AWD_PKG is an internal, application-owned package rather than a published public API, and is not referenced by any other database object at the schema level; instead, it is invoked from the Oracle Forms front end and from sibling IGS packages that manage award-related setup. Its declared dependencies include APP_EXCEPTION for standardized error raising, FND_GLOBAL for environment context, FND_MESSAGE and IGS_GE_MSG_STACK for message handling, IGS_GE_NUMBER for numeric conversion, and the validation helpers IGS_PS_VAL_AW, IGS_AS_GRD_SCHEMA_PKG, and IGS_GR_TESTAMUR_TYPE_PKG. The ETRM record notes that the package is referenced by 18 other packages within the application, confirming its role as a shared award-maintenance utility. Because it performs direct DML against a base table, customizations should call ADD_ROW (and, where applicable, UPDATE_ROW) rather than issuing SQL against IGS_PS_AWD directly, so that constraint checking, WHO-column maintenance, and message-stack error reporting remain intact across both 12.1.1 and 12.2.2 environments.