Search Results igs_ge_unhandled_exception




Overview

IGS_FI_INVOICE_PROCESS is a PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite. Its source header identifies it under the IGS (Student Systems) product family, with the source file revision IGSFI49B.pls 120.1. In EBS 12.1.1 and 12.2.2, this package belongs to the Financials interface layer of the Student Systems (formerly Oracle Student System / OSS) module, serving as the integration driver between student fee assessments and the Oracle Receivables and invoice/payment processing subsystems.

The package is classified as API classification OTHER, meaning it is not formally registered as a public open interface API but rather as an internal processing package invoked through concurrent programs. Its central responsibility is orchestrating the movement of fee and invoice data across the interfaces: from fee assessment to OAR (Oracle Accounts Receivable), from the interface staging tables into OAR, and from OAR onward into invoice and payment processing.

Key Procedures and Functions

The documented package exposes four procedures. Each is designed with the standard concurrent program signature — errbuf OUT NOCOPY VARCHAR2 and retcode OUT NOCOPY NUMBER — confirming that they are intended to be executed as concurrent program entry points rather than called interactively.

  • IGS_FI_FEE_ASTO_INT — Handles fee assessment to interface processing. The version shown in the source is explicitly obsoleted per SFCR005: when invoked, it writes the IGS_GE_OBSOLETE_JOB message to the log file, sets retcode to 0, and exits normally. Its WHEN OTHERS handler sets retcode := 2, raises the IGS_GE_UNHANDLED_EXCEPTION message, assigns it to errbuf, and delegates to IGS_GE_MSG_STACK.Conc_Exception_Hndl for stack logging.
  • IGS_FI_INTTO_OAR — Handles movement of interface records into Oracle Accounts Receivable. Like the preceding procedure, this routine is also obsoleted under SFCR005 and follows the identical obsolete-job logging pattern and exception handling logic.
  • IGS_FI_OARTO_INVPAY — Drives the transfer of OAR data into invoice and payment processing. It accepts an organization identifier parameter in addition to the standard concurrent program signature, indicating organization-level filtering of the records processed.
  • IGS_FI_PER_PAY_SCHED — Manages payment schedule processing for persons, operating over payment schedule data generated during the fee-to-invoice lifecycle.

Tables Accessed

The ETRM metadata does not enumerate specific base tables referenced through APPS synonyms for this package body, and no direct table list is published in the documented excerpt. Based on the package's stated purpose, its operations logically target the Student Systems fee and interface staging tables (fee assessment and interface entities) alongside the Oracle Receivables interface and invoice/payment tables that receive the transferred records. All such access occurs through APPS synonyms under the standard EBS multi-org security model.

Usage Notes

This package is invoked exclusively through Oracle EBS concurrent programs, as evidenced by the standard errbuf/retcode parameter convention on every documented procedure. Two of the four procedures (IGS_FI_FEE_ASTO_INT and IGS_FI_INTTO_OAR) have been obsoleted by SFCR005; when an administrator submits the corresponding concurrent programs, the job completes successfully (retcode 0) but logs an explicit obsolete-job message rather than performing any data transfer. This behavior is significant when troubleshooting: the appearance of the IGS_GE_UNHANDLED_EXCEPTION message, which the user searched against, originates from the WHEN OTHERS exception handlers in this package. It signals an unexpected runtime error, and the accompanying IGS_GE_MSG_STACK.Conc_Exception_Hndl call writes the full PL/SQL error stack to the concurrent request log. The package is not referenced by other packages, reinforcing its role as a terminal concurrent program entry point rather than a shared library. Customizations should not extend the obsoleted procedures; new development should target the replacement interface utilities identified by SFCR005.