Results for “igw_budget_category_v”

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

Overview

The IGW_BUDGET_CATEGORY_V view is a reporting object delivered within the Oracle E-Business Suite Grants Proposal module (product code IGW), which is documented as obsolete in the ETRM reference for releases 12.1.1 and 12.2.2. Its purpose is to present, for each budget line, the expenditure type together with its associated budget category and the direct costs accumulated against that line. The view consolidates line-item cost and employee benefit cost into a single base amount, and exposes overhead cost alongside an indicator of whether overhead has been applied. In this capacity it functions as a summarized, presentation-layer view rather than a transactional entity, and would typically be consumed by budget inquiry screens, grants reporting, or downstream integration extracts that need budget category level cost rollups without navigating the underlying proposal, version, and period structures directly. Because IGW is flagged obsolete, the view is retained only for backward compatibility and is not implemented in the current database release.

Underlying Base Objects

The view is defined over two documented source objects. The first is IGW_BUDGET_COMPLETE_V, aliased PBCV, which supplies the proposal, version, budget period, line item, expenditure type, budget category code, and the cost components (line item cost, employee benefit cost, and overhead cost). The second is IGW_LOOKUPS_V, aliased FL, which resolves the budget category code into a user-facing meaning by matching on lookup code where the lookup type is 'IGW_BUDGET_CATEGORY'. The join between the two is an equality between the budget category code on the budget view and the lookup code on the lookup view. No base tables are documented directly for this view; all access is mediated through the intermediate IGW_BUDGET_COMPLETE_V and IGW_LOOKUPS_V objects, making the view a second-tier aggregation layer over the Grants Proposal budget data model.

Key Columns

• PROPOSAL_ID, VERSION_ID, BUDGET_PERIOD_ID — identify the proposal, its version, and the budget period to which the summarized line belongs.
• LINE_ITEM_ID — the specific budget line item being reported.
• EXPENDITURE_TYPE — the expenditure type assigned to the line, used to classify the nature of the cost.
• EXPENDITURE_CATEGORY_FLAG — a flag carried from the budget source indicating the expenditure category classification.
• BUDGET_CATEGORY_CODE — the internal code representing the budget category.
• BUDGET_CATEGORY — the descriptive meaning of the code, obtained from the lookup view.
• BASE_AMT — the sum of line item cost and employee benefit cost, representing the direct cost base for the line.
• OH_APPLIED_FLAG — 'Y' or 'N' depending on whether overhead cost is non-zero.
• OH_COST — the overhead amount associated with the line.
• EB_COST — the employee benefit cost component.

Common Use Cases and Queries

Typical use cases include budget category cost rollups, verification of overhead application, and grants proposal reporting by period. Because the view aggregates on proposal, version, period, line item, expenditure type, and category, it is well suited to summary inquiries that do not require line-level detail.

SELECT proposal_id,
       version_id,
       budget_period_id,
       budget_category,
       SUM(base_amt) total_direct,
       SUM(oh_cost)  total_overhead
FROM   igw_budget_category_v
WHERE  proposal_id = :proposal_id
GROUP BY proposal_id, version_id, budget_period_id, budget_category;

A second common pattern isolates lines where overhead has been applied:

SELECT line_item_id, expenditure_type, budget_category, base_amt, oh_cost
FROM   igw_budget_category_v
WHERE  oh_applied_flag = 'Y'
ORDER BY proposal_id, budget_period_id, line_item_id;

Given the obsolete status of the IGW module, any query relying on this view should be reviewed against current Grants Management functionality before being carried forward into new development.