Results for “igf_ap_td_item_mst_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGF_AP_TD_ITEM_MST_PKG is an Oracle Application Object Library style PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle iGrants / Grants Accounting (IGF) product family, which manages award, proposal, and grant-related expenditure processing. The package serves as the master maintenance API for the IGF_AP_TD_ITEM_MST entity, controlling the creation, modification, deletion, locking, and validation of third-party or award-related item master records that are consumed by downstream iGrants and payables integration logic.

Functionally, the package acts as a thin business-logic layer above the underlying base table and its translated and sequence support objects. It centralizes row-level data manipulation so that higher-level forms, concurrent programs, and dependent packages do not write directly to the base table. In the Oracle Forms framework terminology, the procedure set follows the classical Table Handler pattern, exposing generic handlers such as INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW alongside wrapper and validation routines. The body is marked VALID in the ETRM metadata, indicating that it compiles cleanly against its declared dependencies.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. None are described with explicit signatures in the metadata, so parameter lists are not asserted here; only their documented purposes are summarized.

• INSERT_ROW — Performs the physical insert of a new item master row into the base table, typically populating mandatory columns and audit attributes.
• UPDATE_ROW — Applies changes to an existing item master row, including the update of the "who" and "when" audit columns.
• DELETE_ROW — Removes an existing item master row from the base table.
• LOCK_ROW — Acquires a row-level lock (SELECT ... FOR UPDATE) so that a caller can safely read, modify, and re-save a record within a single transaction.
• ADD_ROW — Wrapper routine that drives insertion logic, including primary key generation and validation, before delegating to INSERT_ROW.
• GET_PK_FOR_VALIDATION — Returns the primary key value for a candidate record so that uniqueness and referential checks can be performed against the base table.
• GET_FK_IGF_AP_APPL_SETUP — Retrieves the foreign key value linking the item master row to the application setup entity, supporting parent-child validation.
• GET_UK_FOR_VALIDATION — Returns the unique key value used to enforce uniqueness constraints on the item master record.
• BEFORE_DML — Central pre-DML hook that executes shared validation, defaulting, and audit-stamping logic prior to any insert, update, or delete operation.

Tables Accessed

The package reads and writes the following database objects through APPS synonyms:

• IGF_AP_TD_ITEM_MST_ALL — The primary multi-organization base table holding item master records; targeted by INSERT_ROW, UPDATE_ROW, DELETE_ROW, and LOCK_ROW.
• IGF_AP_TD_ITEM_MST_ALL_S — The corresponding sequence object used to generate surrogate primary key values for new rows.
• DUAL — Utilized for single-row selection expressions, typically for sequence nextval retrieval or constant value resolution.

The table handler is accompanied by additional referenced objects, notably IGF_AP_TD_ITEM_MST and IGF_AP_TD_ITEM_MST_ALL_S, which the metadata lists among dependencies of the package body.

Usage Notes

IGF_AP_TD_ITEM_MST_PKG is not referenced by any database object per the documented dependency graph, and it is explicitly listed as being referenced by three other packages, indicating that it functions as a shared utility API rather than the entry point of a transaction. Typical invocations occur from Oracle Forms-based maintenance screens for iGrants item master setup, from concurrent programs that batch-load or validate item master data, and from custom PL/SQL extensions that must respect the same validation and audit rules. Because the procedures rely on FND_GLOBAL for session context and on FND_MESSAGE and APP_EXCEPTION for error signaling, callers should set up the FND session environment before invocation. The package also calls IGS_GE_MSG_STACK and IGS_GE_GEN_003, so error handling propagates through the standard iGrants message stack.