Search Results igi_itr_approval_pkg




Overview
Explore in AI Chat

Overview

IGI_ITR_APPROVAL_PKG is an APPS-owned PL/SQL package within the Oracle E-Business Suite that supports the approval processing engine for intercompany charge transactions managed by the Intercompany Transaction Reconciliation (ITR) module. In both EBS 12.1.1 and 12.2.2, the package orchestrates the routing, authorization, and disposition of charge lines as they move through a multi-tier approval hierarchy. Its documented scope covers workflow initiation, approver identity resolution, authority verification, and the recording of approval history. The package is classified as API type OTHER and is marked VALID in the ETRM repository. It is referenced by no other packages, indicating that it functions as a top-level controller invoked directly by the forms and workflow infrastructure of the ITR application rather than being a shared utility library. The package exposes twenty-nine documented procedures and functions, all of which relate to the lifecycle of an intercompany charge approval — from the moment a preparer submits a charge line to the point at which a receiver or final approver acts upon it.

Key Procedures and Functions

The documented entry points fall into several functional groups:

Tables Accessed

Through APPS synonyms, the package reads and writes the following documented tables:

Usage Notes

IGI_ITR_APPROVAL_PKG is normally invoked indirectly through the ITR charge approval forms and the Oracle Workflow processes bound to them; end users trigger its logic by submitting, approving, or rejecting charge lines rather than calling the package directly. Because it is the sole documented reference point for its own functionality and is not referenced by other packages, customizations should treat it as the authoritative integration surface for ITR approval behavior. Custom code that needs to inject approval actions or query approval state should call the documented procedures by name, observing the authority checks they enforce. Any modification to approval routing rules is best implemented within the package body, as its procedures are not designed to be overridden externally.