Results for “igw_report_itemized_budget”

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

Overview

The IGW_REPORT_ITEMIZED_BUDGET table resides in the IGW schema, which supports the Oracle E-Business Suite Grants Proposal (IGW) module. Its documented purpose is to store information about combined expenditure category or expenditure type descriptions that map to a sponsor budget category. In practical terms, this table acts as a reporting-oriented bridge between a proposal's budget structure and the descriptive expenditure breakdowns required when presenting itemized budgets to sponsors. It is most commonly consumed by Grants Proposal reporting logic that renders budget detail at the expenditure level rather than at the aggregate budget category level.

Only six columns are documented for the 12.1.1 physical schema, indicating a narrow, purpose-built structure. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it is not treated as a strict hub, link, or satellite. A reasonable modeling suggestion is to view it as a report/aggregation satellite keyed to version and budget context, since its dominant foreign key relationship points to VEA_VERSIONS rather than to a full normalized hub structure.

Key Information Stored

• PROPOSAL_ID — Identifies the grant proposal to which the itemized budget reporting line belongs; a primary business-key candidate for scoping.
• VERSION_ID — The version of the proposal/budget; this is the documented foreign key referencing VEA_VERSIONS.
• BUDGET_PERIOD_ID — Segments the itemized budget by budget period, enabling period-by-period reporting.
• PROPOSAL_BUDGET_CATEGORY — The sponsor budget category that the underlying expenditure description rolls up into.
• PROPOSAL_FORM_NUMBER — Identifies the proposal form associated with the reported budget line.
• EXPENDITURE_DESCRIPTION — The textual expenditure category or expenditure type description presented against the sponsor budget category.

The documented schema does not enumerate a surrogate primary key column; the effective row identity is expected to be the combination of proposal, version, period, budget category, and form context. Where a unique index is defined, the composite of these business columns functions as the natural key.

Common Use Cases and Queries

Typical use cases include generating sponsor-facing itemized budget reports, reconciling expenditure descriptions against sponsor categories, and producing version-aware budget comparisons. A representative query joining to the version master is:

• SELECT r.PROPOSAL_ID, r.BUDGET_PERIOD_ID, r.PROPOSAL_BUDGET_CATEGORY, r.EXPENDITURE_DESCRIPTION FROM IGW.IGW_REPORT_ITEMIZED_BUDGET r WHERE r.VERSION_ID = :version_id;
• Period roll-ups: SELECT BUDGET_PERIOD_ID, PROPOSAL_BUDGET_CATEGORY, COUNT(*) FROM IGW.IGW_REPORT_ITEMIZED_BUDGET WHERE PROPOSAL_ID = :proposal_id GROUP BY BUDGET_PERIOD_ID, PROPOSAL_BUDGET_CATEGORY;
• Version comparison: join VEA_VERSIONS on VERSION_ID to resolve version labels for reporting.

Because the object is report-oriented, avoid treating it as the authoritative transaction source; use it for presentation and descriptor resolution, and reconcile against core budget tables where applicable.

Related Objects

• VEA_VERSIONS — Referenced via IGW_REPORT_ITEMIZED_BUDGET.VERSION_ID = VEA_VERSIONS.VERSION_ID; the sole documented FK and the primary version master.
• IGW proposal and budget tables — Parent proposal and budget header/detail objects keyed by PROPOSAL_ID and BUDGET_PERIOD_ID that supply the underlying budget amounts.
• Sponsor budget category setup objects — Source definitions for PROPOSAL_BUDGET_CATEGORY.
• Expenditure type/category reference objects — Source of EXPENDITURE_DESCRIPTION values.
• Proposal form definitions — Associated with PROPOSAL_FORM_NUMBER and the reporting layout.

These relationships support report generation and reconciliation while confirming the object's role as a lightweight, report-facing summary within the Grants Proposal module.