Search Results igf_ap_ver_grps_prc_pkg




Overview
Explore in AI Chat

Overview

IGF_AP_VER_GRPS_PRC_PKG is an Oracle EBS PL/SQL package owned by the APPS schema that supports the processing of verification groups within the Oracle iGrants (IGF) module, specifically the grantee and applicant verification functionality integrated with Oracle Payables. The package operates in the intersection between student financial aid processing and supplier/institution verification, coordinating the maintenance of verification items associated with applicants, institutions, and third-party entities tracked in the iGrants and student systems data model.

In the context of Oracle EBS 12.1.1 and 12.2.2, this package forms part of the internal server-side logic that manages the lifecycle of verification items — records that capture whether an applicant, institution, or related party has satisfied a particular verification requirement. The package is classified as an OTHER API type within the ETRM metadata, meaning it is not exposed as a formally published public API but rather serves as an internal processing engine invoked by higher-level routines, concurrent processes, or form-based transactions. It carries a VALID status in the documented environment and is self-referenced (recursive dependency), indicating that one or more of its internal procedures calls back into the package itself or into a sibling routine within the same package body.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions within this package:

  • DUP_VER_ITEM — Handles duplication of a verification item. This routine supports the creation of a new verification item record based on an existing one, typically when a verification requirement must be replicated across terms, applicants, or processing cycles without re-entering source data.
  • ADD_VER_ITEM — Inserts a new verification item into the master verification item store. This procedure is the primary creation path for verification item records, populating the master table with the incoming requirement details.
  • MAIN — Serves as the coordinating or driver routine of the package. It orchestrates the verification group processing logic, calling the supporting procedures as required to complete the verification item workflow.

Parameter lists are not disclosed in the ETRM excerpt, and they should not be assumed. Consumers must inspect the package specification directly in the target instance to determine call signatures.

Tables Accessed

The package references several base tables through APPS synonyms, reflecting the cross-module nature of verification group processing:

  • IGF_AP_FA_BASE_REC_ALL — Stores base financial aid record data for applicants; used to link verification items to the underlying aid record.
  • IGF_AP_TD_ITEM_MST_ALL — The master table of verification items (tracking data items), which is the primary target for the DUP_VER_ITEM and ADD_VER_ITEM procedures.
  • IGF_FC_SAR_CD_MST — Holds SAR (Student Aid Report) code master data, used to validate or resolve codes associated with verification items.
  • IGS_PE_PERSID_GROUP_ALL — Stores person identification group assignments from the Oracle Student System, used to resolve applicant identity and group membership during verification processing.
  • IGS_CA_INST and IGS_PE_PRSID_GRP_MEM — Institution and person SID group membership tables referenced by the package body for institutional and personal identification context.
  • IGF_AP_INST_VER_ITEM — Institutional verification item data, supporting the institutional side of the verification workflow.

Usage Notes

This package is typically invoked indirectly rather than called directly by end users. Its most common invocation paths are internal calls from higher-level iGrants processing routines, concurrent programs that batch-process verification groups, and form-based logic within the Oracle iGrants responsibility. Because the ETRM metadata shows the package is referenced by zero other packages (other than itself), custom code calling this package directly should treat it as an internal implementation detail subject to change across patch levels.

Developers and administrators diagnosing verification item issues in 12.1.1 or 12.2.2 should inspect the package body for the exact logic in MAIN and its subordinate procedures. Any custom invocation should be wrapped in defensive error handling, since the package is not a published API and its behavior may vary between releases.