Search Results proposal_funding_id

Overview

The IGW_PROJECT_FUNDINGS table is a core data object within the Oracle E-Business Suite Grants Proposal module (IGW), specifically designed to manage detailed funding information for awarded projects. Its primary role is to store granular financial data associated with the funding of a grant or sponsored project, acting as a child record to higher-level proposal and award entities. It is critical for tracking the financial commitments and disbursements tied to a specific project award. Notably, the ETRM metadata explicitly classifies the IGW - Grants Proposal module as "Obsolete," indicating this table and its associated functionality are part of a legacy system component that is no longer under active development or enhancement in the specified EBS releases (12.1.1 / 12.2.2). The documentation further states it is "Not implemented in this database," which may refer to a specific instance or a broader deprecation status.

Key Information Stored

The table's structure is centered on the unique funding identifier for a proposal. The documented primary key is PROPOSAL_FUNDING_ID, which serves as the unique identifier for each funding record. A critical foreign key column is PROPOSAL_INSTALLMENT_ID, which links the funding detail to a specific installment schedule defined in the IGW_INSTALLMENTS table. While the full column list is not provided in the excerpt, based on its description as "Information about awards project funding," typical data would include the funded amount, funding source, budget period, obligation dates, and status for a particular segment of the overall project award. This table enables the breakdown of a total award amount into manageable, schedulable financial components.

Common Use Cases and Queries

The primary use case is financial reporting and tracking for sponsored projects. Administrators would query this table to answer questions about the total funding committed, the timing of disbursements, and the linkage between funding amounts and project milestones or installments. A common reporting pattern would involve joining to the parent award and installment tables to generate funding schedules. A sample query to list all funding details for a specific proposal might follow this pattern:

• SELECT pf.* FROM IGW_PROJECT_FUNDINGS pf, IGW_INSTALLMENTS i WHERE pf.PROPOSAL_INSTALLMENT_ID = i.INSTALLMENT_ID AND i.PROPOSAL_ID = :p_proposal_id;

Given the module's obsolete status, direct operational use in newer implementations is unlikely; its primary relevance is for historical data migration, custom reporting on legacy data, or support for instances still running the obsolete functionality.

Related Objects

The table maintains a direct, documented foreign key relationship with the IGW_INSTALLMENTS table. This is the sole relationship explicitly provided in the metadata.

• IGW_INSTALLMENTS: The IGW_PROJECT_FUNDINGS table references this table via the column PROPOSAL_INSTALLMENT_ID. This relationship ties a specific funding amount to a scheduled installment or payment period within the broader project timeline. The join condition is IGW_PROJECT_FUNDINGS.PROPOSAL_INSTALLMENT_ID = IGW_INSTALLMENTS.<INSTALLMENT_ID_COLUMN>.

As a child table itself, IGW_PROJECT_FUNDINGS would typically be referenced by higher-level proposal or award summary tables (not listed in the provided excerpt), and it may feed into financial interfaces or general ledger posting entities within the Grants Accounting module.