Search Results get_fk_igs_fi_govt_fund_src




Overview
Explore in AI Chat

Overview

IGS_FI_FUND_SRC_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the Student Systems (IGS) financials product family. Its name indicates responsibility for the funding source entity used within Oracle Student Financial Aid processing — specifically, the foundation records that associate a student or sponsor with a fund source and government funding classifications. The package implements the standard EBS table-handling interface for the IGS_FI_FUND_SRC_ALL table, exposing a consistent CRUD-plus-validation surface that other IGS modules can invoke instead of issuing direct DML.

The package status is VALID in the documented environment (ETRM 12.1.1, applicable to 12.1.1 / 12.2.2). It has a limited external footprint in the dependency graph: it depends only on the SYS.STANDARD package, but it is referenced by thirteen other APPS packages, making it a low-level, widely shared component rather than an application-facing entry point.

Key Procedures and Functions

The documented API surface consists of nine procedures and functions:

  • INSERT_ROW — Inserts a new record into the funding source table, applying the package's standard attribute derivation and defaulting rules.
  • LOCK_ROW — Acquires a row-level lock on an existing record, typically through a SELECT ... FOR UPDATE, to serialize concurrent modification.
  • UPDATE_ROW — Applies changes to an existing record after locking and validation.
  • ADD_ROW — Handles first-time insertion logic, providing the wrapper used when a row does not yet exist.
  • DELETE_ROW — Removes a record from the funding source table, subject to the package's referential checks.
  • GET_PK_FOR_VALIDATION — Returns the primary key for a supplied record so that callers, forms triggers, and constraint routines can validate uniqueness and existence before DML.
  • GET_FK_IGS_FI_GOVT_FUND_SRC — Derives or returns the foreign key to the government fund source entity, ensuring funding source rows are correctly linked to their government classification.
  • CHECK_CONSTRAINTS — Performs package-level validation of business and referential rules before the DML is committed.
  • BEFORE_DML — The mandatory pre-DML hook that populates the WHO columns (created/updated by, dates, login) and executes standard validation on each insert, update, or delete.

Tables Accessed

The package references two documented tables through APPS synonyms:

  • IGS_FI_FUND_SRC_ALL — The multi-org funding source table that is the primary target of all insert, update, delete, lock, and validation operations performed by this package.
  • DUAL — Used for scalar lookups and PL/SQL expression evaluation.

In addition, the package derives the government fund source foreign key (via GET_FK_IGS_FI_GOVT_FUND_SRC), which links records to related government funding source data used within the same IGS financials schema.

Usage Notes

IGS_FI_FUND_SRC_PKG is not intended for direct invocation by end users. It is consumed programmatically by other IGS packages: thirteen packages reference it, including IGS_FI_FND_SRC_RSTN_PKG, IGS_FI_FD_SRC_RSTN_H_PKG, IGS_FI_GOVT_FUND_SRC_PKG, IGS_EN_STDNT_PS_ATT_PKG, IGS_EN_SPA_LGCY_PUB, IGS_AD_PS_APPL_INST_PKG, IGS_AD_PS_APLINSTHST_PKG, the IGS_AD_SBMAO_* family, and IGS_HE_POOUS_ALL_PKG. This dependency pattern indicates the package sits beneath admission, enrolment, financial aid, and higher-education processing layers.

Typical call paths are form handlers and concurrent programs within the Student Systems modules, plus custom extensions that manage funding source records. The dominant pattern is a BEFORE_DML-then-INSERT_ROW/UPDATE_ROW sequence, with LOCK_ROW and CHECK_CONSTRAINTS used to enforce concurrency and validation. Because the package depends only on SYS.STANDARD, it is effectively self-contained at the PL/SQL level, but callers must still supply correctly structured record types and observe the WHO column population performed by BEFORE_DML. In 12.1.1 and 12.2.2 the object resides in the APPS schema and is compiled as a standard database package; no Java or OAF deployment artifacts are associated with it.