Results for “igw_prop_locations_s”

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

Overview

The PL/SQL package body APPS.IGW_PROP_LOCATIONS_TBH is a table handler (TWH) unit delivered as part of the Oracle Grants Management (formerly Oracle Grants Proposal / IGW) application family within Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix _TBH follows the Oracle Applications coding convention for a "table handler," signifying that the package encapsulates the core data manipulation logic associated with a specific base table. In this case, that base table is IGW_PROP_LOCATIONS and its companion foreign key / lookup table IGW_PROP_LOCATIONS_S.

The business function of this package is to provide a controlled, centralized interface for inserting, updating, and deleting records that describe the physical locations associated with a proposal. Proposal locations capture where research activity is conducted — for example, a PI's laboratory, a partner institution, a field site, or a sub-awardee facility. These records feed downstream reporting, effort certification, and institutional compliance. By isolating the DML behind named procedures, the package enables validation, message handling, and exception propagation consistent with the Oracle Applications framework rather than allowing ad hoc SQL against the underlying tables.

Key Procedures and Functions

The ETRM metadata documents three procedures on this package body. Parameter lists are not part of the published metadata and are therefore not reproduced here.

• INSERT_ROW — Creates a new proposal-location record in the base table. The procedure is responsible for populating standard WHO columns (creation date, created-by, last update date, last-updated-by, last update login) and for enforcing any mandatory attribute checks before the row is committed.
• UPDATE_ROW — Modifies an existing proposal-location record. It handles the bookkeeping of WHO audit columns and ensures that changes flow through the same validation path as an insert, protecting data integrity where the location is referenced by other proposal constructs.
• DELETE_ROW — Removes a proposal-location record. Consistent with Oracle Grants practices, the delete may be logical in nature depending on the entity, or it may physically remove the row while applying referential safeguards.

These three procedures form a cohesive CRUD trio, one of the most common shapes for Oracle Applications table handlers.

Tables Accessed

• IGW_PROP_LOCATIONS — the primary base table holding proposal location records. This is the principal target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW.
• IGW_PROP_LOCATIONS_S — the sequence (or companion) object referenced by the package. The presence of a _S object indicates that primary keys for the base table are sourced from a database sequence, which the INSERT_ROW logic draws upon to generate unique identifiers.

Access to these objects is via APPS synonyms, so the package operates in the APPS schema and relies on standard synonym resolution rather than fully qualified schema names.

Usage Notes

Dependencies recorded in the metadata confirm that the package builds on the standard Oracle Application Object Library stack: FND_API for message and API conventions, FND_GLOBAL for session context (user id, login id, responsibility), FND_MESSAGE and FND_MSG_PUB for the message dictionary and stacked error handling, and APP_EXCEPTION for raising and managing application-level exceptions. This pattern is characteristic of a server-side API designed to be called from Oracle Forms or other PL/SQL clients rather than executed directly at the SQL*Plus prompt.

Typical invocation is from the Oracle Grants proposal-entry forms, where the locations block issues calls to INSERT_ROW, UPDATE_ROW, and DELETE_ROW as the user manipulates proposal location lines. Because the package is not referenced by any other database object per the ETRM report, it is a leaf-level API — it may be invoked by form triggers, by concurrent-program logic, or by custom PL/SQL extensions that follow the documented procedure names, but no shipped package depends on it. Customers extending proposal location behavior should call these procedures rather than performing direct DML, ensuring that validation logic, auditing columns, and error messages remain consistent with the Oracle E-Business Suite standard.