Search Results delete_temp_award




Overview
Explore in AI Chat

Overview

IGW_AWARDS_PVT is a private PL/SQL package body in the APPS schema that serves as the core data-manipulation layer for award records within the Oracle Grants Management (IGW/GMS) module. The package encapsulates the business logic required to create, modify, delete, and persist grant award headers and their associated award installments. It is classified as a PVT (private) API, meaning it is intended to be invoked by the corresponding public package, IGW_AWARDS_PUB, or by other internal GMS components rather than being called directly by external applications or custom code. The "PVT" designation typically signals that the procedures here implement the actual DML against the underlying award tables, while the public wrapper enforces validation rules, security, and message handling.

The package carries the header identifier igwvawib.pls 120.12, dated 2005/09/12, indicating it is a long-standing component of the E-Business Suite Grants schema that has remained stable across releases including 12.1.1 and 12.2.2. The body declares a package-level constant G_PKG_NAME for error logging and uses the standard API error-handling conventions (return status, message count, and message data out parameters).

Key Procedures and Functions

The ETRM documentation lists eight documented procedures and functions within this package. Their purposes are as follows:

  • CREATE_AWARD — Inserts a new award header record, establishing the primary award entity that grant administrators manage.
  • CREATE_AWARD_INSTALLMENT — Creates an installment line associated with an award, supporting the scheduling of funded amounts over time.
  • UPDATE_AWARD — Modifies an existing award record. This is the procedure most commonly surfaced when users search for "update_award," as it is the internal implementation behind award maintenance operations in the Grants forms and public APIs.
  • DELETE_AWARD — Removes an award record, including the appropriate integrity handling for dependents.
  • TRANSFER_AWARD_INSTALLMENT — Moves or reallocates an installment from one award or funding context to another.
  • GET_AWARD_NUMBERING_METHOD — Retrieves the configured numbering method used when generating award numbers; the source excerpt shows this as a stub returning a null implementation, with the numbering method returned as an out parameter.
  • DELETE_TEMP_AWARD — Cleans up temporary award records, typically created during pre-award or draft processing.
  • MAKE_PERMANENT — Converts a temporary award into a permanent award, a standard pattern for two-phase award creation.

Additional helper functions appear in the source excerpt—Check_Lock, Get_Gms_Lookup_Code, Get_Funding_Source_Id, and Get_Award_Manager_Id—though several are stubbed with null bodies, indicating they are either placeholders or superseded by logic elsewhere.

Tables Accessed

The documented ETRM metadata does not enumerate the specific tables referenced by this package. Based on the GMS schema and the award/installment operations described, the package writes to and reads from the core award tables (such as GMS_AWARDS and its installment counterpart) via APPS synonyms. The metadata confirms only that no additional packages reference this one directly (referenced by 0 other packages), reflecting its position as a leaf-level implementation package.

Usage Notes

Because IGW_AWARDS_PVT is a private package, it should not be called directly from custom code. Oracle recommends invoking the public API, IGW_AWARDS_PUB, which delegates to these private procedures. In practice, the procedures are triggered from the Grants Management award entry forms, from concurrent programs that process award imports or mass updates, and from GMS pre-award workflows where DELETE_TEMP_AWARD and MAKE_PERMANENT convert drafts into final awards. Customizations requiring award updates should always go through the public API to ensure validation, locking (via Check_Lock logic), and error-message propagation occur. Note that direct DML against the underlying tables bypasses this package and risks violating the integrity checks it enforces.