Search Results underrecovery_amount




Overview
Explore in AI Chat

Overview

IGW_BUDGET_DETAILS_V is a reporting view owned by the APPS schema within the IGW (Grants Proposal) product family of Oracle E-Business Suite. The ETRM metadata classifies it as "10SC Only," indicating that its availability and content are scoped to the Grants Proposal functionality associated with that designation rather than to the general Oracle EBS schema set. The view presents grant proposal budget detail lines together with their associated cost elements, including cost sharing, underrecovery, and inflation handling attributes.

Functionally, the view serves as a denormalized, read-only projection over the IGW_BUDGET_DETAILS base table. Its principal role is to expose budget detail rows for inquiry, reporting, and downstream integration without requiring consuming applications to address the base table directly. Because the view carries no filter predicates in its documented definition, the row set returned is identical in cardinality and composition to the underlying table. The column list mirrors the base table structure, including the standard EBS audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), which supports incremental extraction patterns and concurrency-safe integration.

Underlying Base Objects

The view is defined over a single documented base object, IGW_BUDGET_DETAILS. The view text performs a direct column projection with no joins, unions, aggregations, or filtering. The mapping is one-to-one: every column exposed by the view corresponds to a column of the same name in IGW_BUDGET_DETAILS.

Given the prefix conventions in the IGW schema, the base table is expected to reside in the APPS schema alongside the view. The documented metadata records no additional referenced objects; therefore, no implicit joins to related grants or budgeting tables should be assumed. Any enrichment with proposal, version, or award header information must be performed by the consuming query against the appropriate parent tables using the key columns the view exposes.

Key Columns

Common Use Cases and Queries

Typical scenarios include budget-line reporting for a proposal version, aggregation of cost and cost-sharing amounts by expenditure type, and extraction of underrecovery amounts for sponsored project reconciliation.

  • Retrieve all budget lines for a proposal version and period:

SELECT proposal_id, version_id, budget_period_id, line_item_id, expenditure_type, line_item_cost, cost_sharing_amount, underrecovery_amount FROM apps.igw_budget_details_v WHERE proposal_id = :p_proposal AND version_id = :p_version ORDER BY budget_period_id, line_item_id;

  • Aggregate cost, cost sharing, and underrecovery by expenditure type:

SELECT expenditure_type, SUM(line_item_cost) total_cost, SUM(cost_sharing_amount) total_cost_share, SUM(underrecovery_amount) total_underrecovery FROM apps.igw_budget_details_v WHERE proposal_id = :p_proposal GROUP BY expenditure_type;

  • Incremental extraction using the audit columns:

SELECT proposal_id, version_id, budget_period_id, line_item_id, underrecovery_amount, last_update_date FROM apps.igw_budget_details_v WHERE last_update_date >= :p_since;

Consumers should apply the same security and grants-specific access controls used for the IGW schema, since the view itself imposes no row-level filtering.