Search Results igf_ap_isir_matched_pkg




Overview
Explore in AI Chat

Overview

IGF_AP_ISIR_MATCHED_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Student Financial Aid processing flow for ISIR (Institutional Student Information Record) data, part of the Financial Aid module (IGF). ISIR records originate from the U.S. Department of Education and must be matched against existing person and organization records before they can be used in awards, disbursements, and verification processing. This package encapsulates the data-access and DML logic for the IGF_AP_ISIR_MATCHED entity, which stores the outcome of matching an incoming ISIR against a student or related party identity. In ETRM terms it is classified as an OTHER API, meaning it exposes low-level row operations rather than a single high-level business transaction. It is a base-level utility package called across the ISIR lifecycle: import, generation, correction, matching, verification, and NSLDS data handling.

Key Procedures and Functions

The documented API surface contains eight procedures/functions:

  • INSERT_ROW — inserts a new ISIR matched record into the entity table.
  • ADD_ROW — companion insert routine, typically used to add a row with caller-supplied primary key values.
  • UPDATE_ROW — updates an existing matched record, generally keyed on the row's primary or unique identifier.
  • UPDATE_ROW_RECTYPE — a specialized update limited to record-type attributes of the matched row, allowing the record type to be changed without rewriting the entire entity.
  • DELETE_ROW — removes an existing matched record.
  • LOCK_ROW — issues a SELECT FOR UPDATE to serialize concurrent modification of a matched record.
  • BEFORE_DML — a pre-DML hook that populates standard WHO columns such as creation/update date and user, executed by the API routines.
  • GET_PK_FOR_VALIDATION — retrieves the primary key of the matched record for validation before performing DML, returning a Boolean or success indicator depending on the internal convention.

No public parameter lists are documented in the ETRM metadata, so signatures should be obtained from the deployed package specification.

Tables Accessed

The package reads and writes the base and synonym tables that underpin ISIR matching:

  • IGF_AP_ISIR_MATCHED_ALL — the multi-org base table holding matched ISIR records; the primary write target for INSERT, UPDATE, and DELETE.
  • IGF_AP_ISIR_MATCHED_S — the corresponding security/sequence table used to generate identifiers for new rows.
  • IGF_AP_FA_BASE_REC_ALL — the financial aid base record, used to associate a matched ISIR with its originating student record.
  • HZ_PARTIES and HZ_RELATIONSHIPS — TCA party and relationship tables, used to resolve the student and related parties during identity matching.
  • IGS_OR_ORG_ALT_IDS and IGS_OR_ORG_ALT_IDTYP — alternative organization identifiers and their types, used to match institution or entity references carried on the ISIR.
  • DUAL — used for sequence/next-value and single-row utility operations.

Usage Notes

IGF_AP_ISIR_MATCHED_PKG is not invoked directly by end users. It is a dependency of nine higher-level packages, including IGF_AP_BATCH_VER_PRC_PKG, IGF_AP_ISIR_CORR_PKG, IGF_AP_ISIR_GEN_PKG, IGF_AP_ISIR_IMPORT_PKG, IGF_AP_LI_ISIR_IMP_PROC, IGF_AP_MATCHING_PROCESS_PKG, IGF_AP_MK_ISIR_ACT_PKG, IGF_AP_NSLDS_DATA_PKG, and IGF_AP_SS_PKG. These callers drive the ISIR import and matching concurrent processes; this package performs the underlying CRUD work and row locking. Any customization or data fix touching ISIR matched rows should route through this API so that BEFORE_DML maintains WHO columns and LOCK_ROW ensures concurrency safety. Because it also references itself, recursion or nested calls are possible within the matching process. All operations run at the APPS schema level and are subject to the caller's Mo/VPD security context.