Results for “igs_pe_persenc_effct_pkg”

48 results




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

Overview

IGS_PE_PERSENC_EFFCT_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Student System (IGS) product family. The name resolves to "Person Encumbrance Effect," and the package encapsulates the data-access and validation logic for the IGS_PE_PERSENC_EFFCT entity, which records the effect of an encumbrance held against a person or student record. Encumbrances in the Student System represent restrictions such as financial holds, registration blocks, or eligibility overrides that must be evaluated before certain transactions are permitted. This package provides a generated, table-handler style API that centralizes insert, update, delete, lock, and constraint-validation operations against the base table so that other IGS modules do not embed direct DML. It is a dependent object only on SYS.STANDARD, confirming that it relies on no other application package for its core behavior, while twelve other packages — including IGS_EN_ATD_TYPE_PKG, IGS_PE_PERS_ENCUMB_PKG, and several generated IGS_EN and IGS_AZ objects — call into it. The object is documented as VALID in ETRM for release 12.1.1 and remains present in 12.2.x.

Key Procedures and Functions

Ten documented subprograms form the public surface of the package. They follow the standard Oracle Forms-generated table handler pattern:

  • INSERT_ROW — inserts a new row into the person encumbrance effect table, populating surrogate and foreign key columns from the supplied record.
  • UPDATE_ROW — applies changes to an existing row identified by its primary key.
  • DELETE_ROW — removes the identified row from the table.
  • LOCK_ROW — acquires a row-level lock to serialize concurrent modification, typically invoked before an update or delete in a multi-user form session.
  • ADD_ROW — convenience wrapper that combines validation and insertion for a new record.
  • GET_PK_FOR_VALIDATION — resolves or confirms the primary key value used for validation checks on the target row.
  • GET_FK_IGS_EN_ATD_TYPE — retrieves the foreign key value referencing the attendance type entity, supporting referential integrity during DML.
  • GET_FK_IGS_PE_PERS_ENCUMB — retrieves the foreign key value referencing the parent person encumbrance record.
  • CHECK_CONSTRAINTS — evaluates mandatory columns, lookup validity, and relational constraints before a row is committed.
  • BEFORE_DML — pre-DML trigger logic that standardizes auditing columns and derived attributes across insert, update, and delete paths.

Tables Accessed

The package operates on three tables exposed through APPS synonyms. IGS_PE_PERSENC_EFFCT is the primary table holding the encumbrance-effect records that the DML procedures manipulate. IGS_EN_ELGB_OVR_ALL stores eligibility override data, which the effect rows reference when an encumbrance modifies a student's eligibility outcome. IGS_PE_HOLD_REL_OVR holds hold-release override information, linking encumbrance effects to the release of a hold. Reads against these tables support the check-constraint and foreign-key resolution routines, while writes are confined to the primary table.

Usage Notes

This package is normally invoked indirectly. Oracle Forms-based Student System windows that maintain person encumbrances and their effects call the table handler on save, lock, and clear events, giving the end user transparent validation. Concurrent programs and batch processes such as the generated IGS_EN and IGS_AZ concurrent program objects listed among the referencing packages also call these routines when evaluating eligibility and attendance during enrollment. Custom extensions should call the documented procedures rather than issuing direct INSERT, UPDATE, or DELETE statements against IGS_PE_PERSENC_EFFCT, because BEFORE_DML and CHECK_CONSTRAINTS enforce auditing and integrity rules that direct DML would bypass. Because the package has no application-level dependencies, it can be safely reused by custom code provided the caller supplies the required key values and honors the row-locking discipline.