Search Results budget_category




Overview
Explore in AI Chat

Overview

IGW_BUDGET_LINE_CATEGORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGW – Grants Proposal product. Its documented purpose is to display the expenditure type, the associated budget category, and the line item cost for budget lines. In practice, the view flattens budget line detail into a denormalized, human-readable form by resolving the raw budget category code into its display meaning and by reconciling the expenditure type recorded on the budget line against the expenditure type defined for the budget period.

Because Grants Proposal budgeting is organized hierarchically — proposal, version, budget period, and line item — the view exposes all four levels of that hierarchy alongside the financial and descriptive attributes of each line. This makes it a convenient source for reporting on how proposed costs are distributed across budget categories such as personnel, supplies, travel, or indirect costs. The view is read-only and is intended for query and reporting rather than transaction processing; concurrent programs, BI Publisher reports, OBIEE/OTBI extracts, and custom SQL frequently reference it when budget category breakdowns are required. It is valid in Oracle EBS 12.1.1 and 12.2.2, and since it resides in APPS, callers should reference it as APPS.IGW_BUDGET_LINE_CATEGORY_V or, when grants are used, as IGW.IGW_BUDGET_LINE_CATEGORY_V, respecting the standard grants synonym and security model.

Underlying Base Objects

The documented view text identifies three referenced objects:

The joins are inner joins, meaning budget lines whose budget category code has no matching IGW_BUDGET_CATEGORY lookup, or whose category flag/expenditure combination cannot be resolved, are excluded from the result set. This behavior is important when diagnosing apparent row loss in reports.

Key Columns

  • PROPOSAL_ID — identifies the grant proposal to which the budget line belongs.
  • VERSION_ID — the proposal version, allowing comparison across revisions.
  • BUDGET_PERIOD_ID — the budget period within the proposal version.
  • LINE_ITEM_ID — unique identifier of the budget line item.
  • LINE_ITEM_COST — the monetary cost recorded for the line item; the primary budgeting measure.
  • EXPENDITURE_TYPE — the expenditure type associated with the budget line, used to classify the nature of the cost.
  • LINE_ITEM_DESCRIPTION — free-text description of the line.
  • BUDGET_CATEGORY_CODE — the stored lookup code (for example, the raw category value).
  • BUDGET_CATEGORY — the translated meaning of the code from IGW_LOOKUPS_V, suitable for display.
  • BUDGET_JUSTIFICATION — narrative justification entered for the budget line.

Common Use Cases and Queries

Typical uses include budget category roll-up reports, proposal budget worksheets, expenditure type analysis, and data extracts feeding downstream reporting tools. A common query totals proposed cost by category for a given proposal and version:

  • SELECT budget_category, SUM(line_item_cost) total_cost FROM igw_budget_line_category_v WHERE proposal_id = :p_proposal AND version_id = :p_version GROUP BY budget_category ORDER BY budget_category;
  • SELECT budget_period_id, expenditure_type, line_item_description, line_item_cost FROM igw_budget_line_category_v WHERE proposal_id = :p_proposal ORDER BY budget_period_id, budget_category;
  • SELECT budget_category, COUNT(*) line_count, SUM(line_item_cost) cost FROM igw_budget_line_category_v WHERE proposal_id = :p_proposal GROUP BY budget_category HAVING SUM(line_item_cost) > 0;

Where documentation is limited, developers should validate behavior by tracing against IGW_BUDGET_DETAILS directly, since the view is a straightforward projection over that table plus two lookup joins. Remember that rows failing the lookup or expenditure-type join are silently dropped, so reconciliation totals may differ from the base detail table.