Search Results igf_ap_lg_td_imp




Overview

The APPS.IGF_AP_LG_TD_IMP package is a PL/SQL implementation component within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environment, owned by the APPS schema and carrying a status of VALID. Its naming convention situates it clearly within the Oracle Student Financial Aid / Financial Aid (IGF) product family, specifically the AP (Accounts Payable) and LG (Loans/Grant) processing areas, with the "TD" component signifying a relationship to term or translator data processing. The package functions as a backend import and processing driver that updates the financial aid base records and logs results of that processing.

The package combines several responsibilities. It executes a main processing routine, manipulates the financial aid base record staging structures, and writes diagnostic output to a log table. Because it references STANDARD without any other Oracle-supplied PL/SQL built-ins, the package relies primarily on direct SQL data manipulation against the underlying financial aid and student system tables.

Key Procedures and Functions

  • MAIN — The primary driver entry point. It coordinates the overall execution flow of the package, orchestrating calls to the logging, base record update, and processing helpers.
  • PRINT_LOG_PROCESS — A logging utility that outputs processing results and status messages, allowing batch or interactive invocations to surface a readable trace of the import operation.
  • UPDATE_FABASE_PROCESS — Controls the process-level update of the financial aid base records, governing the wider update cycle across the selected record set.
  • UPDATE_FABASE_REC — Performs the granular, record-level update against the base record staging table, applying the data changes required to reconcile imported financial aid information with the existing base records.
  • ADD_LOG_TABLE — Manages the creation and insertion of log rows so that processing activity and error information are persisted for later review.

Tables Accessed

The package operates against a broad set of documented tables accessed through APPS synonyms. The primary financial aid targets are IGF_AP_FA_BASE_REC_ALL, the base record repository updated by the FABASE procedures; IGF_AP_TD_ITEM_INST_ALL and IGF_AP_TD_ITEM_MST_ALL, which hold term item instance and master data; and IGF_AP_LI_BAT_INTS and IGF_AP_LI_TODO_INTS, which relate to loan/batch and outstanding item interface records. Student system dependencies include IGS_CA_INST_ALL, IGS_PE_HZ_PARTIES, and IGS_CO_INTERAC_HIST, providing calendar instance, person-party, and interaction history context. Party and lender data are drawn from HZ_PARTIES, IGF_SL_CL_PREF_LENDERS, and IGF_SL_CL_RECIPIENT. The PLITBLM table is referenced as a PL/SQL table or utility structure. These tables collectively support the identification of parties, resolution of loan recipients and preferred lenders, and reconciliation of term/item balances during base record maintenance.

Usage Notes

The package is typically invoked indirectly rather than from an end-user form. Its status as an import/processing component indicates that it is triggered by a concurrent program, a scheduled financial aid batch run, or by another IGF package during term-based loan or grant processing. The ETRM metadata records zero packages referencing IGF_AP_LG_TD_IMP, which suggests it sits at a leaf of the dependency graph and is called from concurrent program definitions or custom code rather than from sibling PL/SQL APIs. The presence of PRINT_LOG_PROCESS and ADD_LOG_TABLE confirms reliance on a log table for operational visibility. Because the package name matches its own reference list and no downstream subobjects are documented, administrators should treat it as a self-contained processing unit whose diagnostics are reviewed through the log table after batch execution. Customizations must avoid altering the package in place, as the APPS schema object may be reapplied during patching.