Results for “get_uk_for_validation”

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

Overview

IGR_INQUIRY_LINES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API. It belongs to the Oracle Grants / iGrants (IGR) product family, which provides the inquiry and proposal tracking components used in the grants management lifecycle. The package encapsulates core data manipulation logic for the inquiry lines entity — the individual line items that constitute a customer or sponsor inquiry record. In the iGrants inquiry model, an inquiry represents an early-stage funding opportunity or sponsor contact, and its lines capture the specific items of interest, amounts, or proposed activity detail associated with that inquiry.

The package is a valid, compiled object in the APPS schema and its scope is deliberately narrow: it exposes row-level DML operations and a single validation helper rather than a full business-event API. This design indicates it is an internal service package invoked by other iGrants components rather than a public interface intended for external integration.

Key Procedures and Functions

ETRM documents three callable units within IGR_INQUIRY_LINES_PKG:

• INSERT_ROW — Creates a new inquiry line record. It handles the initial population of the line entity, including standard WHO columns and any derived or defaulted attributes required for a new line row. This is the entry point used when a user or process adds a line to an existing inquiry.
• UPDATE_ROW — Modifies an existing inquiry line. It supports changes to the mutable attributes of a line after creation, preserving the associated audit columns (last updated by, last update date, last update login).
• GET_UK_FOR_VALIDATION — Returns the unique key (UK) value or set required to validate a row against the inquiry line entity. This helper is used to enforce uniqueness or referential consistency before insert or update operations, ensuring the surrogate or natural key supplied by the caller maps to a valid record.

No parameter lists are published in the ETRM metadata, and parameter signatures should be confirmed against the deployed package specification in the target environment before any direct invocation.

Tables Accessed

The package operates against three documented tables via APPS synonyms:

• IGR_I_A_LINES — The primary base table for inquiry lines. INSERT_ROW and UPDATE_ROW perform DML against this table; it is the principal persistence target for the entity managed by the package.
• IGR_I_APPL_ALL — The inquiry application/allocation table. Read access supports validation and key resolution, linking line records to their parent inquiry application context.
• AS_SALES_LEAD_LINES — The CRM sales lead line table. Its presence reflects the integration between iGrants inquiry data and the Oracle Sales/CRM lead model, where an inquiry may originate from or relate to sales lead information.

Usage Notes

IGR_INQUIRY_LINES_PKG is referenced by IGR_IMP_003, an iGrants import/concurrent program, which indicates the package is invoked during batch inquiry import processing. It is also self-referenced, meaning some internal routines call one another for shared validation and DML logic.

Typical invocation scenarios include the iGrants inquiry maintenance forms (when a user adds or modifies inquiry lines), the IGR_IMP_003 import concurrent program, and any custom code that must manipulate inquiry lines while respecting the package's validation conventions. Because the API is classified as OTHER and is primarily an internal row-handling package, direct calls from custom code should be made cautiously, with the current package specification reviewed first. Where possible, callers should prefer higher-level iGrants APIs or the standard inquiry forms so that business validation, key derivation, and audit columns remain consistent with the application's intended processing model.