Results for “igw_budget_complete_v”

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

Overview

IGW_BUDGET_COMPLETE_V is a database view owned by the APPS schema within the Oracle E-Business Suite Grants Proposal (IGW) module. It is documented as VALID in the ETRM reference for releases 12.1.1 and 12.2.2. The view is described as a mechanism "to display overhead amounts and employee benefit amounts for budget lines." Its principal role is to expose, for each proposal budget line, the base line item cost together with the associated overhead (indirect cost) and employee benefit amounts, which are not stored as simple columns but are derived at query time.

Because the view returns these computed figures alongside the identifying keys of the proposal, version, budget period, and budget line, it serves as a convenient reporting and integration surface. Rather than requiring downstream reports, forms, or interfaces to invoke the underlying integration APIs individually, the view consolidates them into a single, denormalized read-only result set. This makes it suitable for Grants proposal budget reporting, validation, and extraction into external systems.

Underlying Base Objects

The view is defined over a single documented base object: IGW_BUDGET_DETAILS, which holds the proposal budget detail lines and supplies the identifying and descriptive columns. Three of the output columns are not physical columns of the base table; they are produced by calls into the IGW_BUDGET_INTEGRATION package:

• IGW_BUDGET_INTEGRATION.GET_LINE_ITEM_COST(LINE_ITEM_ID) supplies LINE_ITEM_COST.
• IGW_BUDGET_INTEGRATION.GET_OH_COST(LINE_ITEM_ID) supplies OH_COST (overhead).
• IGW_BUDGET_INTEGRATION.GET_EB_COST(LINE_ITEM_ID) supplies EB_COST (employee benefit).

Consequently, the view is not a simple projection of a base table but a computed join between stored budget detail rows and the PL/SQL cost-derivation logic in IGW_BUDGET_INTEGRATION. Query performance therefore depends on the efficiency of those function calls, and each invocation carries the behavioral attributes and error-handling of the package.

Key Columns

The view exposes the following columns:

• PROPOSAL_ID, VERSION_ID — Identify the Grants proposal and the specific proposal version.
• BUDGET_PERIOD_ID — Identifies the budget period to which the line belongs.
• LINE_ITEM_ID — The primary identifier of the budget detail line; also the argument passed to the integration functions.
• LINE_ITEM_COST — The derived cost of the line item.
• EXPENDITURE_TYPE — The expenditure type classification for the line.
• BUDGET_CATEGORY_CODE — The budget category assigned to the line.
• EXPENDITURE_CATEGORY_FLAG — Flag indicating the expenditure category characteristic.
• BASED_ON_LINE_ITEM — Reference to a line item on which this line is based.
• PROJECT_ID, AWARD_ID, TASK_ID — Project, award, and task associations carried from the budget detail.
• OH_COST — The derived overhead amount for the line item.
• EB_COST — The derived employee benefit amount for the line item.

Common Use Cases and Queries

Typical uses include budget review reports that must present the fully loaded cost of each line (base plus overhead plus benefits), reconciliation of indirect cost calculations, and extraction of budget data for integration with other Grants or financial modules. The following example lists all completed budget figures for a given proposal version:

• SELECT proposal_id, version_id, budget_period_id, line_item_id, line_item_cost, oh_cost, eb_cost FROM apps.igw_budget_complete_v WHERE proposal_id = :p_proposal_id AND version_id = :p_version_id ORDER BY budget_period_id, line_item_id;

A second common pattern aggregates total direct, overhead, and benefit amounts by budget period to produce summary budget rollups. Because OH_COST and EB_COST are computed per row, aggregation over large proposals should be evaluated for performance, and results should be validated against the IGW_BUDGET_INTEGRATION package logic. The view is read-only and should not be used for data maintenance; inserts and updates must be directed to the underlying budget detail tables through supported Grants functionality.