Search Results igw_budget_types

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

Overview

IGW_BUDGETS_V is a PL/SQL-based view owned by the APPS schema within the Oracle E-Business Suite Grants Management (IGW) module. It belongs to the FND Design Data object family IGW.IGW_BUDGETS_V and holds VALID status. The view exposes budget information tied to proposals and their versions, presenting data in a denormalized, user-friendly format that joins identifier values to their human-readable descriptions. It is a primary reporting and integration interface for proposal budgets, including total costs, direct and indirect cost breakdowns, cost-sharing amounts, and residual funds.

The view also exposes configuration flags that govern how budget figures are calculated, including APPLY_INFLATION_SETUP_RATES, APPLY_EB_SETUP_RATES, and APPLY_OH_SETUP_RATES. Because the user searched for "apply_eb_setup_rates," this view is a relevant object for locating the enablement flag that controls whether entity-budget (EB) setup rates are applied during budget generation. The column carries the value of the underlying flag and is presented directly in the view output.

Underlying Base Objects

The documented metadata does not list referenced base objects. In practice, IGW_BUDGETS_V is defined over the core Grants Management budget tables, principally IGW_BUDGETS, together with lookups and joined reference tables that supply descriptive text for coded values. The view resolves the OH_RATE_CLASS_ID into OH_RATE_CLASS, the BUDGET_TYPE_CODE into BUDGET_TYPE, and supplies PROPOSAL_FORM_NUMBER through a join to proposal header data. The ROW_ID column carries the ROWID of the underlying budget row.

The APPLY_EB_SETUP_RATES, APPLY_INFLATION_SETUP_RATES, APPLY_OH_SETUP_RATES, and ENTER_BUDGET_AT_PERIOD_LEVEL columns are exposed as VARCHAR2 flags. Each mirrors the corresponding setup-rate or period-level control on the budget record. The presence of these columns in the view, rather than requiring a direct query of the base table, makes IGW_BUDGETS_V a convenient access point for reporting and integration.

Key Columns

• PROPOSAL_ID / VERSION_ID — Identify the proposal and the specific version whose budget is presented.
• START_DATE / END_DATE — The budget period bounds.
• TOTAL_COST, TOTAL_DIRECT_COST, TOTAL_INDIRECT_COST — Aggregate budgeted amounts.
• COST_SHARING_AMOUNT, UNDERRECOVERY_AMOUNT, RESIDUAL_FUNDS, TOTAL_COST_LIMIT — Analysis amounts used in sponsor and internal cost review.
• OH_RATE_CLASS_ID / OH_RATE_CLASS — Identifier and description of the overhead rate class applied to the budget.
• BUDGET_TYPE_CODE / BUDGET_TYPE — Code and description of the budget type (for example proposed, awarded, or submitted).
• FINAL_VERSION_FLAG — Indicates whether this budget belongs to the final proposal version.
• ENTER_BUDGET_AT_PERIOD_LEVEL — Flag controlling whether the budget is entered and calculated at period level.
• APPLY_INFLATION_SETUP_RATES, APPLY_EB_SETUP_RATES, APPLY_OH_SETUP_RATES — Flags that determine which setup rate sources are applied when the budget is generated.
• DESCRIPTION, COMMENTS — Free-text annotations attached to the budget.
• ALLOW_CREATE, ALLOW_MODIFY — Descriptive access-control columns.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — The standard descriptive flexfield columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns.

Common Use Cases and Queries

A frequent requirement is to identify which budgets have entity-budget setup rates enabled:

• SELECT proposal_id, version_id, budget_type, apply_eb_setup_rates FROM apps.igw_budgets_v WHERE apply_eb_setup_rates = 'Y';

Reviewing the cost breakdown for a proposal version:

• SELECT proposal_form_number, total_cost, total_direct_cost, total_indirect_cost, cost_sharing_amount FROM apps.igw_budgets_v WHERE proposal_id = :p_proposal_id ORDER BY version_id;

Comparing rate-application configurations across budgets:

• SELECT budget_type, apply_inflation_setup_rates, apply_eb_setup_rates, apply_oh_setup_rates FROM apps.igw_budgets_v WHERE final_version_flag = 'Y';

Because the view exposes both identifiers and descriptive values, it supports reporting, integration extracts, and diagnostic queries without requiring the developer to join to lookup tables manually. Queries against it should be limited to the columns and rows needed, since the view does not apply additional filtering.