Search Results find_services




Overview
Explore in AI Chat

Overview

The APPS.IGI_ITR_TIMEOUT_PKG package is a component of the Oracle E-Business Suite financials module, specifically associated with the IGI (Oracle Internal Controls Manager / iExpenses-related) schema and the ITR (Internal Transaction Reconciliation or related timeout/charge) processing framework. Its principal business function is to identify and process services associated with timeout and charge handling across one or more ledgers. The package is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than its owner, which has implications for security and access control at runtime. The package header, as documented in ETRM, exposes two public procedures and serves as the entry point for ledger-scoped service identification logic.

A significant design note embedded in the source is that the original code within find_services was relocated to find_ledger_services, indicating an evolution of the package to support both single-ledger and multi-ledger (Data Access Set) processing. The header comment explicitly states that p_access_set_id was added so that service lines across all ledgers within a Data Access Set could be processed in a single invocation — a critical feature for organizations operating with multiple ledgers and shared service responsibilities.

Key Procedures and Functions

  • FIND_SERVICES — The primary procedure for discovering and processing services. It returns standard concurrent program out parameters (errbuf and retcode) and accepts a set of books identifier along with a Data Access Set identifier. The inclusion of p_access_set_id enables the procedure to traverse service lines belonging to all ledgers encompassed by the specified Data Access Set, rather than restricting processing to a single ledger. This makes it suitable for centralized or cross-ledger timeout processing.
  • FIND_LEDGER_SERVICES — This procedure represents the relocated core logic originally housed within find_services. It accepts the standard concurrent out parameters and a single set of books identifier. By isolating ledger-specific processing into its own procedure, the package supports modular invocation: find_services can iterate across multiple ledgers and delegate per-ledger work to find_ledger_services.

Tables Accessed

According to the documented metadata, the package references five tables via APPS synonyms, all belonging to the IGI_ITR family:

  • IGI_ITR_ACTION_HISTORY — Records the history of actions taken during timeout processing, providing an audit trail of service identification and handling.
  • IGI_ITR_CHARGE_HEADERS — Stores header-level charge information related to ITR timeout processing.
  • IGI_ITR_CHARGE_LINES — Contains line-level charge details that the package evaluates when identifying chargeable or timeout-eligible services.
  • IGI_ITR_CHARGE_RANGES — Defines the ranges (thresholds or bands) used to categorize or calculate charges during processing.
  • IGI_ITR_CHARGE_SETUP — Holds configuration data governing how charges and timeouts are set up and applied within the ITR framework.

Together, these tables form the configuration and transactional backbone that the package reads and potentially updates as it identifies services requiring attention.

Usage Notes

The package is typically invoked from a concurrent program within Oracle EBS, evidenced by the errbuf and retcode OUT parameters that conform to the standard concurrent processing interface. It may also be called from custom PL/SQL code or forms that require on-demand service identification. When invoked with a valid p_access_set_id, find_services processes service lines across all ledgers in the Data Access Set; when only a p_set_of_books_id is relevant, find_ledger_services can be called directly. Because the package is declared AUTHID CURRENT_USER, callers must possess the necessary privileges on the underlying IGI_ITR tables. The package is not referenced by any other documented packages, indicating it is a terminal integration point rather than a shared library.