Search Results igw_installments_tbh




Overview

The APPS.IGW_INSTALLMENTS_TBH package body is a database-tier Table Handler (the "TBH" suffix denoting this role) that encapsulates the core Data Manipulation Language operations for the installment records used by Oracle E-Business Suite's Grants and proposals framework, delivered through the IGW module. In EBS 12.1.1 and 12.2.2, this package operates under the APPS schema and is classified as an "OTHER" API rather than a public, versioned interface. Its business purpose is to provide a controlled, centralized point for inserting, updating, and deleting rows in the underlying installment tables, isolating callers from direct table access and enforcing the module's validation and error-handling conventions.

The package is registered in ETRM with a status of VALID and exposes three documented procedures. It depends on standard EBS infrastructure packages, including FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and APP_EXCEPTION, which together indicate that the handler participates in the Oracle Application Object Library messaging and error-handling model — capturing messages through the FND message stack and raising standardized exceptions rather than returning raw Oracle errors to callers.

Key Procedures and Functions

The package body documents three procedures:

  • INSERT_ROW — Creates a new installment record. It is the entry point used when a new installment definition is introduced to the system, and it is expected to apply the table handler's validation rules before committing the row.
  • UPDATE_ROW — Modifies an existing installment record. This procedure supports maintenance of installment attributes over the life of the record, such as changes to amounts, dates, or descriptive details.
  • DELETE_ROW — Removes an installment record from the underlying tables. Consistent with EBS practice, deletion logic may be physical or may respect the module's data-retention rules depending on how the base tables are configured.

No function signatures, parameter lists, or return types are documented in the ETRM metadata; consumers must inspect the package specification directly before invoking these routines programmatically.

Tables Accessed

The package reads and writes two documented database objects, referenced through APPS synonyms:

  • IGW_INSTALLMENTS — The primary base table holding installment records. All three procedures (INSERT_ROW, UPDATE_ROW, DELETE_ROW) operate against this table, making it the central subject of the handler.
  • IGW_INSTALLMENTS_S — The companion sequence (or surrogate-key source) used to generate unique identifiers when new installment rows are inserted, ensuring primary key integrity.

The dependency list also confirms the package references its own specification, IGW_INSTALLMENTS_TBH, which is standard for packaged PL/SQL units.

Usage Notes

Because this is a table handler rather than a public API, it is normally invoked from within the IGW module's own code paths rather than directly by external developers. Typical invocation contexts include Oracle Forms-based maintenance screens and any internal module logic that must create, amend, or remove installment rows. ETRM records indicate that the package body is not referenced by any database object, meaning no other stored PL/SQL unit depends on it — it is a leaf-level handler, called from client-side or middle-tier code. Customizations that require installment maintenance should prefer the supported module interfaces; where direct calls are unavoidable, the caller must initialize the FND message and global context appropriately, since the package relies on FND_GLOBAL, FND_MSG_PUB, and APP_EXCEPTION for its runtime environment and error propagation. As with all APPS-owned objects, modifications should be avoided in favor of standard extension mechanisms.