Results for “igw_budgets”

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

Overview

IGW_BUDGETS is a core transactional table in the Oracle EBS IGW – Grants Proposal module. It stores information about budget versions associated with grant proposals, capturing each versioned financial summary of a proposal's cost structure, rate application, and indirect cost characteristics. In the grants management workflow, this table acts as the parent record for the detailed budget lines distributed across periods, persons, and proposal rates, making it the anchor for budget creation, versioning, and finalization activities.

The table resides in the IGW schema and is documented as VALID in both 12.1.1 and 12.2.2. Its primary key, IGW_BUDGETS_PK, is composed of PROPOSAL_ID and VERSION_ID. From a Data Vault modeling perspective, the metadata's heuristic classification suggests this object is hub-leaning: it carries the natural business key of a proposal-version combination and serves as the reference point for dependent satellites and links. This classification is a modeling suggestion derived from the foreign key structure, not an enforced EBS construct.

Key Information Stored

The table exposes 42 documented columns. The most operationally significant are:

• PROPOSAL_ID and VERSION_ID — the composite primary key identifying a specific budget version of a proposal.
• START_DATE and END_DATE — the effective period covered by the budget version.
• TOTAL_COST, TOTAL_DIRECT_COST, and TOTAL_INDIRECT_COST — the aggregate financial rollups for the version.
• COST_SHARING_AMOUNT, UNDERRECOVERY_AMOUNT, and RESIDUAL_FUNDS — supporting cost-allocation figures.
• TOTAL_COST_LIMIT — the ceiling applied to the budget.
• OH_RATE_CLASS_ID — foreign key to IGW_RATE_CLASSES, defining the overhead rate class.
• FINAL_VERSION_FLAG — indicates whether the version is the finalized budget.
• BUDGET_TYPE_CODE — categorizes the budget.
• PROPOSAL_FORM_NUMBER — links the budget to its proposal form.
• APPLY_INFLATION_SETUP_RATES, APPLY_EB_SETUP_RATES, and APPLY_OH_SETUP_RATES — flags controlling rate application behavior.
• ENTER_BUDGET_AT_PERIOD_LEVEL — controls the granularity of budget entry.

The unique index IGW_BUDGETS_U1 on (PROPOSAL_ID, VERSION_ID) confirms the composite business key, which coincides with the primary key columns. Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, RECORD_VERSION_NUMBER, and the ATTRIBUTE1–15 flex columns) are also present.

Common Use Cases and Queries

Typical uses include budget version comparison, cost rollup reporting, and identifying the finalized budget for a proposal. A common query pattern retrieves all versions for a proposal:

• SELECT VERSION_ID, TOTAL_COST, TOTAL_DIRECT_COST, TOTAL_INDIRECT_COST, FINAL_VERSION_FLAG FROM IGW_BUDGETS WHERE PROPOSAL_ID = :proposal_id;
• To find the active finalized version: filter on FINAL_VERSION_FLAG = 'Y'.
• Cost-sharing analysis joins the budget header to IGW_BUDGET_PERIODS on PROPOSAL_ID and VERSION_ID to reconcile period detail against header totals.

Reporting scenarios include grants dashboarding, indirect cost recovery analysis, and audit trails of budget revisions across versions.

Related Objects

• IGW_PROPOSALS_ALL — parent proposal; join on PROPOSAL_ID.
• IGW_RATE_CLASSES — referenced by OH_RATE_CLASS_ID.
• IGW_BUDGET_PERIODS — period-level detail; joins on PROPOSAL_ID and VERSION_ID.
• IGW_BUDGET_PERSONS — personnel budget lines; joins on PROPOSAL_ID and VERSION_ID.
• IGW_PROP_RATES — proposal rate records; joins on PROPOSAL_ID and VERSION_ID.