Search Results igs_fi_elm_range_rt_pkg




Overview

IGS_FI_ELM_RANGE_RT_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified as a component of the Oracle Student Financial Aid (IGS) application family. Its object name and dependencies identify it as the row-handler layer for the IGS_FI_ELM_RANGE_RT entity, which stores element range rate definitions used in financial aid fee and rate calculations. The package encapsulates the standard Oracle Forms row-level DML behavior — insert, lock, update, delete, constraint checking, and primary/unique key validation — for that entity, and it also exposes foreign-key lookup functions used when other rate-related entities are validated or displayed.

The body status is VALID under both Oracle EBS 12.1.1 and 12.2.2. The ETRM metadata documents the object as an OTHER-classification API rather than a public business API, which reflects its role as an internal table-handler package rather than a user-facing interface. It is not referenced by any database object (no other package, view, or trigger calls it), but it is reported as referenced by four other packages and depends in turn on the IGS_FI_EL_RNG_PKG and IGS_FI_FEE_AS_RATE_PKG packages, indicating a tightly coupled rate-calculation subsystem.

Key Procedures and Functions

The body documents twelve procedures and functions, grouped as follows.

  • INSERT_ROW — Performs the base row insertion into IGS_FI_ELM_RANGE_RT, populating the standard WHO columns.
  • LOCK_ROW — Acquires a row-level lock on an existing record, typically used when a form enters update or delete mode.
  • UPDATE_ROW — Applies modifications to an existing element range rate row.
  • ADD_ROW — Higher-level handler that orchestrates insertion, sequence assignment, and key derivation for a new record.
  • DELETE_ROW — Removes a row from the entity.
  • GET_PK_FOR_VALIDATION — Returns the primary key values for a candidate record so that uniqueness can be validated.
  • CHECK_CONSTRAINTS — Validates referential and business constraints before or during DML.
  • GET_UK1_FOR_VALIDATION and GET_UK2_FOR_VALIDATION — Return the values for the first and second unique keys so that duplicate detection can be performed.
  • BEFORE_DML — Central pre-DML routine that runs validation logic and WHO column defaults before any insert, update, or delete is committed.
  • GET_UFK_IGS_FI_ELM_RANGE — Foreign-key lookup that retrieves the parent element range description for display or validation.
  • GET_UFK_IGS_FI_FEE_AS_RATE — Foreign-key lookup that retrieves the associated fee/rate record.

Tables Accessed

The package operates against three documented database objects. IGS_FI_ELM_RANGE_RT is the base table holding element range rate records; it is the target of all insert, update, and delete operations and the source for all lookup queries. IGS_FI_ELM_RANGE_RT_ERR_ID_S is the associated sequence, used to generate the error-identifier value for new rows during ADD_ROW and INSERT_ROW processing. DUAL is referenced for scalar evaluations such as retrieving sequence next values and performing single-row validation checks.

Usage Notes

This package is invoked indirectly rather than by end users. It is called by the Oracle Forms module that maintains element range rates, by concurrent programs that load or validate rate data in bulk, and by the four other packages that reference it. It also participates in the standard IGS message stack (IGS_GE_MSG_STACK, FND_MESSAGE) and error handling framework (APP_EXCEPTION, IGS_FI_VAL_ERR), raising user-facing messages when constraint or uniqueness validation fails.

Because the package body is not referenced by any database object, it should always be invoked through the public specification IGS_FI_ELM_RANGE_RT_PKG rather than called directly. Customizations should avoid modifying the seeded body; extend behavior by wrapping the declared procedures. The dependency on IGS_FI_EL_RNG_PKG and IGS_FI_FEE_AS_RATE_PKG means that any change to those packages must be regression-tested against this row handler. In 12.2.2 the object is compiled online, so recompilation of dependent packages is not required, but AD_ZD or adpatch validation should be run after any upgrade to confirm VALID status.