Search Results igs_ps_us_prenr_cfg_pkg

Overview

The APPS.IGS_PS_US_PRENR_CFG_PKG package belongs to the Oracle E-Business Suite Student Systems (IGS) product family, which supports higher-education institutions in managing the student lifecycle. Specifically, the package supports configuration of United States pre-enrollment (pre-registration) data. Pre-enrollment configuration controls how prospective or continuing students register intent to enroll in a program or unit set before formal enrollment occurs, and the US-specific variant addresses localization requirements applicable to United States institutions.

The package is classified as an "OTHER" API within the ETRM registry. This means it is not a public, supported business API in the same sense as the IGS Enrollment APIs, but rather an internal or generated helper package used to maintain the underlying configuration entity. Its structure, particularly the presence of generated row-handling procedures such as LOCK_ROW, INSERT_ROW, UPDATE_ROW, DELETE_ROW, and CHECK_CONSTRAINTS, is characteristic of Oracle Forms-generated or table-handler packages that enforce primary key, unique key, and foreign key integrity for the associated base table. In Oracle EBS 12.1.1 and 12.2.2, such packages sit behind the corresponding maintenance form and provide a controlled, single point of DML access to the configuration table.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

• INSERT_ROW — Inserts a new configuration row into the base table, populating the primary key and all mandatory columns.
• LOCK_ROW — Issues a row-level lock on a specified configuration record, typically in support of an editing session to prevent concurrent modification.
• UPDATE_ROW — Applies changes to an existing configuration row while preserving key integrity.
• ADD_ROW — Adds a row through the table-handler interface, commonly used by the form to stage and commit new records.
• DELETE_ROW — Removes a configuration row, subject to constraint validation.
• GET_PK_FOR_VALIDATION — Returns the primary key of the record under validation, used by the Form to confirm the correct row identity.
• GET_UK_FOR_VALIDATION — Returns the unique key value used to detect duplicate configuration records.
• CHECK_CONSTRAINTS — Validates primary, unique, and foreign key constraints before DML proceeds.
• BEFORE_DML — Pre-DML hook that runs validation and population logic prior to insert, update, or delete operations.
• GET_FK_IGS_EN_UNIT_SET — Retrieves the foreign key reference linking the configuration record to the enrollment unit set.

No parameter lists are documented in the ETRM metadata; the descriptions above reflect documented purpose only.

Tables Accessed

The package operates against the following tables through APPS synonyms:

• IGS_PS_US_PRENR_CFG — The primary base table storing US pre-enrollment configuration records.
• IGS_EN_UNIT_SET_ALL — The enrollment unit set definition table, referenced to establish and validate the unit set foreign key.
• IGS_EN_UNIT_SET_STAT — The enrollment unit set status table, used to resolve or validate the current status of the associated unit set.

These accesses confirm that US pre-enrollment configuration is scoped to particular enrollment unit sets, and that configuration validity depends on the status of the referenced unit set.

Usage Notes

The package is invoked indirectly by student systems maintenance forms that manage US pre-enrollment configuration. It is referenced by APPS.IGS_EN_UNIT_SET_MAP_PKG, indicating that unit set mapping logic also depends on this configuration package. Because it is an internal table-handler style package rather than a supported public API, customers and integrators should not call it directly from custom code; configuration changes should be made through the supported forms or concurrent processes. When troubleshooting, note that constraint failures raised by CHECK_CONSTRAINTS or BEFORE_DML typically surface as form-level errors rather than database exceptions. The package status is VALID in the documented 12.1.1 environment and behaves consistently in 12.2.2. Its dependencies are limited to SYS.STANDARD and the APPS synonyms above.