Results for “funding_amount”

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

Overview

IGW_PROJECT_FUNDINGS is a table within the Oracle E-Business Suite Grants Proposal (IGW) module, which is documented as obsolete in Release 12.1.1 and 12.2.2. The table stores information about awards project funding, specifically the allocation of proposal funding amounts to projects and tasks associated with sponsored award activity. It functions as a child or detail table within the grants proposal data model, capturing the financial distribution of approved funding across project and task structures.

From a Data Vault modeling perspective, the metadata indicates a satellite-leaning classification. This heuristic suggests the table primarily records descriptive and context-dependent attributes surrounding a funding event — such as amounts, allocation dates, and audit columns — rather than acting as a pure hub (unique business entity registry) or a pure link (many-to-many relationship resolver). The presence of a surrogate primary key and a foreign key to a parent installment table reinforces this satellite interpretation: the table enriches a parent event with measurable funding detail.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• PROPOSAL_FUNDING_ID — Surrogate primary key of the table, enforced by the IGW_PROJECT_FUNDINGS_PK constraint and also defined as the unique business-key candidate through the IGW_PROJECT_FUNDINGS_U1 index. It uniquely identifies each funding record.
• PROPOSAL_INSTALLMENT_ID — Foreign key column referencing IGW_INSTALLMENTS. It links the funding record to the installment (disbursement schedule) from which the funding originates.
• PROJECT_ID — Identifies the project to which funding is allocated.
• TASK_ID — Identifies the specific task within the project receiving the allocation.
• FUNDING_AMOUNT — The monetary value of funding allocated to the referenced project and task.
• RECORD_VERSION_NUMBER — Supports optimistic locking and concurrency control during updates.
• DATE_ALLOCATED — The date on which the funding allocation was recorded.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns tracking who created and last modified each row, and when.

The distinction between the surrogate key (PROPOSAL_FUNDING_ID) and any natural business key is important: the unique index mirrors the primary key, so PROPOSAL_FUNDING_ID serves both roles in the documented schema.

Common Use Cases and Queries

Because the table is marked obsolete and "not implemented in this database" in the ETRM documentation, its practical use is largely historical or migration-oriented. Typical scenarios include:

• Reconstructing award funding distributions across projects and tasks for legacy grants reporting.
• Reconciling proposal installments against the amounts funded to individual projects.
• Auditing when funding allocations were recorded and by whom.

A representative query joining the installment parent might read:

SELECT pf.proposal_funding_id, pf.project_id, pf.task_id, pf.funding_amount, pf.date_allocated FROM igw_project_fundings pf, igw_installments i WHERE pf.proposal_installment_id = i.proposal_installment_id;

Aggregations such as SUM(funding_amount) grouped by project_id or task_id support funding-by-project reporting.

Related Objects

The documented foreign key relationship anchors this table to its parent and related grant objects:

• IGW_INSTALLMENTS — Parent table through the PROPOSAL_INSTALLMENT_ID foreign key.
• IGW_PROJECT_FUNDINGS_PK — Primary key constraint defined on PROPOSAL_FUNDING_ID.
• IGW_PROJECT_FUNDINGS_U1 — Unique index candidate on PROPOSAL_FUNDING_ID.
• Projects (PA) entities — Referenced logically via PROJECT_ID and TASK_ID, linking funding detail to project and task definitions.

Given the obsolete status, integration with other IGW tables and external grants interfaces should be verified against the legacy database before reliance.