Search Results val_int




Overview
Explore in AI Chat

Overview

IGF_AP_LI_ISIR_IMP_PROC is an APPS-owned PL/SQL package within the Oracle E-Business Suite Financial Aid (IGF) module. Its role is to support the import and validation of ISIR (Institutional Student Information Record) data originating from the U.S. federal student aid process, which is delivered in bulk files and loaded into the institution's staging and interface tables. The suffix "LI" denotes the Loan Interface area of Financial Aid, and "ISIR_IMP" identifies the package as an ISIR import processor. The package therefore provides the procedural logic that parses incoming ISIR records, validates individual data elements (codes, dates, numeric ranges, e-mail formats, and record types), constructs base records for downstream processing, and writes validated data into the ISIR interface and internal staging structures used by the Financial Aid award and loan cycles.

The package is classified as OTHER in the ETRM API registry, meaning it is an internal utility package rather than a published public API. It is documented in both 12.1.1 and 12.2.2, where the module remains essentially unchanged in this area.

Key Procedures and Functions

The ETRM metadata documents 29 procedures and functions. The prominent ones are:

  • MAIN — the primary driver procedure that orchestrates the ISIR import flow, invoking validation and record-creation steps in sequence.
  • CPS_IMPORT — handles import of CPS (Central Processing System) supplied ISIR data into the staging/interface tables.
  • CREATE_BASE_REC — constructs the base ISIR record used as the anchor for subsequent validation and persistence.
  • PUT_MEANING and PUT_HASH_VALUES — populate decoded meanings and hash/lookup values associated with imported fields.
  • IS_LOOKUP_CODE_EXIST — a validation helper that checks whether a supplied lookup code is valid in the relevant lookup type.
  • VAL_NAME, VAL_CHAR, VAL_ALPHA, VAL_INPUT_REC_TYPE — validators for person names, character fields, alphabetic-only fields, and the input record type indicator.
  • VAL_DATE and VAL_DATE_2 — validate and normalize date values, with the second variant accommodating an alternative date format or optional date.
  • VAL_EMAIL — validates e-mail address format.
  • VAL_INT, VAL_NUM, VAL_NUM_1, VAL_NUM_2, VAL_NUM_12, VAL_NUM_NONZERO — numeric validators enforcing integer, general numeric, single-digit, two-digit, twelve-digit, and non-zero numeric constraints respectively.
  • VAL_ADD — validates address-type data elements.

Only names and purposes are documented; no parameter signatures are published in the metadata.

Tables Accessed

The package reads from and writes to the following objects, mostly via APPS synonyms:

  • IGF_AP_ISIR_INTS_ALL and IGF_AP_LI_ISIR_INTS — the ISIR interface tables that hold imported ISIR records pending validation and processing.
  • IGF_AP_LI_BAT_INTS — the batch interface table that groups ISIR imports into processing batches.
  • IGF_AW_LI_COA_INTS — the Cost of Attendance interface table, which the ISIR import process populates with derived COA-related values.
  • IGS_PE_ALT_PERS_ID and IGS_PE_PERSON_ID_TYP — person identification tables used to resolve or create the student's alternate person identifiers during import.
  • FND_NEW_MESSAGES — the Oracle Application Object Library message table used to surface validation and error messages.
  • DBMS_UTILITY, STANDARD, PLITBLM, and DUAL — supporting PL/SQL infrastructure and utility objects rather than business tables.

Usage Notes

IGF_AP_LI_ISIR_IMP_PROC is an internal package invoked from within the Financial Aid ISIR import concurrent program flow and from other Financial Aid packages such as IGF_AP_LI_PROF_IMP_PROC and IGS_FI_1098T_EXTRACT_DATA. It is not intended to be called directly from custom code. Oracle EBS 12.1.1 and 12.2.2 do not alter the behavior of this package; the same VAL_* validation routines and MAIN driver apply. Institutions running custom ISIR loads should call the supported concurrent programs rather than this package, since its procedures are undocumented at the parameter level and may change between patch levels. The package body depends on DBMS_UTILITY and STANDARD, confirming it uses standard Oracle-supplied PL/SQL utilities for error formatting and dynamic operations.