Results for “igs_ad_appl_stat_pkg”

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

Overview

The IGS_AD_APPL_STAT_PKG package body in the APPS schema supports the Oracle E-Business Suite Student Systems (Oracle Student System / OSS) admissions module. Its business function is to manage the persistence and validation of admission application status records held in the IGS_AD_APPL_STAT table. In the admissions lifecycle, application status codes track an applicant's progression through stages such as enquiry, application received, under review, offer made, accepted, rejected, and enrolled. This package provides the controlled DML layer that forms and concurrent processes use to insert, update, and delete these status records while enforcing referential integrity, row locking, and validation against lookup values. The API classification in ETRM is documented as OTHER, indicating it is an internal, generated-style package rather than a public business API, and it is typically invoked indirectly through higher-level admissions APIs and the associated maintenance forms rather than being called directly by end users.

Key Procedures and Functions

The ETRM metadata documents nine procedures and functions, all addressing the standard table-handler pattern used extensively across Oracle Student System entities:

• INSERT_ROW — Inserts a new application status row into IGS_AD_APPL_STAT, populating mandatory columns and standard WHO audit columns.
• UPDATE_ROW — Updates an existing application status row, typically after a lock has been obtained.
• DELETE_ROW — Removes an application status row from the table.
• LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) to serialize concurrent modification of a status record.
• ADD_ROW — A convenience wrapper that performs locking and insertion logic for a new record.
• GET_PK_FOR_VALIDATION — Retrieves the primary key of an application status row so that downstream validation logic can operate against the correct record.
• CHECK_CONSTRAINTS — Validates foreign key and lookup constraints before DML is committed, raising errors via the message stack when validation fails.
• BEFORE_DML — A pre-DML hook that applies defaulting, WHO column population, and other preparatory logic before insert, update, or delete operations.
• GET_FK_IGS_LOOKUPS_VIEW — Resolves the foreign key relationship to the lookups view, ensuring the status code corresponds to a valid lookup value.

Tables Accessed

The only table directly documented as referenced (via APPS synonyms) is IGS_AD_APPL_STAT, the base table that stores application status records. All insert, update, delete, lock, and validation operations described above target this table. Supporting dependencies used by the package body include APP_EXCEPTION for error handling, FND_GLOBAL for session context (user and login information for WHO columns), FND_MESSAGE and IGS_GE_MSG_STACK for message construction and error propagation, IGS_AD_APPL_PKG and IGS_AD_VAL_AAS for related admissions validation, and IGS_LOOKUPS_VIEW_PKG for lookup-code verification through GET_FK_IGS_LOOKUPS_VIEW.

Usage Notes

IGS_AD_APPL_STAT_PKG is not intended for direct invocation by custom code. It is referenced by five other database objects within the Oracle Student System, meaning it is called from higher-level packages — most notably the admission application package IGS_AD_APPL_PKG — which in turn are invoked by the admissions maintenance forms, self-service application pages, and concurrent programs that process application status transitions. In Oracle EBS 12.1.1 and 12.2.2, the package remains VALID and follows the standard single-table handler architecture: callers should route status changes through the parent admissions API rather than issuing direct DML against IGS_AD_APPL_STAT, so that BEFORE_DML, CHECK_CONSTRAINTS, and the locking procedures execute in the correct order. Custom integrations needing only to read application status may query the table directly, but any modification should respect the validation and locking behavior provided by this package. The Oracle Proprietary, Confidential Information designation and the legal notices accompanying the ETRM documentation reinforce that any extension or diagnosis of this package should be performed within Oracle support guidelines.