Search Results ap_holds_s




Overview
Explore in AI Chat

Overview

IGI_SIA is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Financials for Public Sector (IGI) product family. Its documented API classification is OTHER, indicating it is not a formally published public API but rather an internal utility package used for processing supplier invoice holds. The package provides the procedural logic required to identify, apply, process, and release holds against Oracle Payables invoices within the ETRM (Enterprise Tax, Treasury, and Revenue Management) and Public Sector invoice workflows.

The package body resides at status VALID and depends on the APPS schema for all of its subordinate objects, including the AP_HOLDS family of tables, invoice and distribution tables, FND_PROFILE, and the IGI_GEN package. It is not referenced by any other database object directly, although its procedures are exposed within the APPS schema and invoked through application logic.

Key Procedures and Functions

The package body documents five procedures and functions, all related to invoice hold management:

  • SET_INVOICE_ID — Establishes the current invoice identifier within the package session, providing the context against which subsequent hold operations are executed.
  • PROCESS_INVOICE_HOLDS — Drives the end-to-end hold processing logic for a supplier invoice, evaluating applicable holds and applying or clearing them as appropriate within the Public Sector invoice lifecycle.
  • REVERSE_HOLDS — Reverses holds that were previously applied to an invoice, typically in response to a transaction correction, cancellation, or workflow reversal.
  • PROCESS_HOLDS — Provides the core hold-processing routine that operates on the set of holds identified for an invoice or distribution, coordinating validation and application logic.
  • RELEASE_HOLDS — Releases invoices or distributions from applied holds once the underlying condition has been satisfied, restoring the document to a releasable state.

These procedures are documented in the ETRM metadata without exposed parameter lists; they are described here by purpose only.

Tables Accessed

IGI_SIA references the following tables via APPS synonyms:

  • AP_HOLDS — The base hold definition and application table; the package reads and writes hold records for invoices.
  • AP_HOLDS_ALL — The multi-organization view of hold data, enabling held invoice processing across operating units.
  • AP_HOLDS_S — The hold definition/setup table, notably the object the user searched for ("ap_holds_s"), used to resolve which holds are active and their release rules.
  • AP_INVOICES — The invoice header table, providing the invoice context and status used as input to hold processing.
  • AP_INVOICE_DISTRIBUTIONS_ALL — The invoice distribution table, allowing holds to be applied or released at the distribution line level.

Profile access is handled through FND_PROFILE, and utility routines are drawn from IGI_GEN.

Usage Notes

IGI_SIA is an internal package that supports the Public Sector invoice hold workflow. It is typically invoked from Oracle Payables forms (particularly the Invoice Workbench and Invoice Holds windows), from concurrent programs that process or release holds in batch, and from custom extensions that need to programmatically apply or release holds against supplier invoices. Because the package references AP_HOLDS, AP_HOLDS_ALL, and AP_HOLDS_S, any caller must operate within an initialization context that sets the correct org and session profile values.

The package body is referenced by five other database objects, confirming it is embedded in broader APPS processing chains rather than being called in isolation. Custom code should not depend on this package as a stable API, since it is classified OTHER and is not documented as a public interface; direct use risks incompatibility across ETRM and EBS point releases such as 12.1.1 and 12.2.2. Where hold manipulation is required, Oracle recommends using the documented Oracle Payables invoice APIs instead.