Search Results igs_en_unit_set_cat_pkg

Overview

The APPS.IGS_EN_UNIT_SET_CAT_PKG package is a core PL/SQL construct within the Oracle E-Business Suite student systems infrastructure, specifically belonging to the Student Records and Enrollment Management product family (the IGS_EN module prefix denotes Enrollment). The package is registered in the APPS schema with a status of VALID, and is classified as an "OTHER" API — meaning it is not a formally published public API but rather an internal procedural wrapper whose primary purpose is to manage data integrity and transactional logic for the IGS_EN_UNIT_SET_CAT table.

The name itself is instructive: "UNIT_SET_CAT" refers to the unit set catalogue (the taxonomy of academic unit set categories) that underpins enrollment configuration. Unit sets define the rules by which academic units (credit, weighting, and related enrollment attributes) are grouped and applied during a student's enrolment record. This package provides the table-level DML abstraction that forms, concurrent programs, and other packages use instead of issuing direct SQL against the base table.

Key Procedures and Functions

The ETRM metadata documents eight procedures/functions. Their purposes are as follows:

• INSERT_ROW — Inserts a new category record into the unit set catalogue, orchestrating the full insert workflow including validation and constraint checks before the physical row is written.
• UPDATE_ROW — Applies changes to an existing category row, ensuring that pre-update validations are performed and row-level integrity is preserved.
• DELETE_ROW — Removes an existing category row, typically accompanied by referential and constraint verification before physical deletion.
• LOCK_ROW — Acquires a row-level lock on the target record, providing concurrency control so that competing sessions cannot modify the same row simultaneously.
• ADD_ROW — Provides a higher-level entry point for adding catalogue rows, characteristically dispatching to the lower-level insert path after performing setup or defaulting logic.
• GET_PK_FOR_VALIDATION — Retrieves the primary key values needed to validate the existence or uniqueness of a category record before further processing.
• CHECK_CONSTRAINTS — Performs the business-rule validation that mirrors the database constraints, allowing callers to detect invalid data before attempting DML.
• BEFORE_DML — A standard Oracle Forms-style preprocessing hook that executes logic (such as populating WHO columns or auditing attributes) immediately prior to insert, update, or delete operations.

The method naming (INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW, BEFORE_DML) follows the conventional Oracle EBS "Table Handler" pattern, indicating that this package is the sanctioned gateway for DML on the underlying table.

Tables Accessed

The package directly references a single documented table through APPS synonyms:

• IGS_EN_UNIT_SET_CAT — the unit set category table that stores the catalogue of unit set categories. This package reads from it during validation and primary-key lookup (GET_PK_FOR_VALIDATION, CHECK_CONSTRAINTS), and writes to it via the insert, update, and delete operations.

The package also declares a dependency on SYS.STANDARD, the built-in PL/SQL package that supplies standard language elements. No other base tables are documented as directly referenced, though WHO-column maintenance within BEFORE_DML is implicit to the EBS table handler convention.

Usage Notes

Within Oracle EBS 12.1.1 and 12.2.2, this package is invoked primarily rather than called directly by end users. ETRM shows it is referenced by two other packages: IGS_DA_SETUP_PKG (the setup-support package for the DA module) and IGS_EN_UNIT_SET_PKG (the parent unit set package), and it references itself. These inbound references indicate that the package functions as a subordinate utility within the broader enrollment setup processing chain.

Typical invocation paths include:

• Oracle Forms performing enrollment setup maintenance, which call the row-handler procedures for insert, update, delete, and lock operations.
• Other IGS packages, notably IGS_EN_UNIT_SET_PKG and IGS_DA_SETUP_PKG, which delegate catalogue maintenance to this package to avoid duplicating DML logic.
• Custom code or concurrent programs that require validated, constraint-checked manipulation of the unit set category catalogue rather than direct SQL.

Because the package is validated and classified as OTHER, implementers should treat it as an internal component: extension is best achieved through the calling packages rather than by modifying or wrapping the package directly, and any custom callers should invoke the documented procedures in the order the table-handler pattern prescribes (lock, validate, then DML) to preserve concurrency and integrity guarantees.