Results for “rate_applied”

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

Overview

IGW_REPORT_BUDGET_BASE_RATE is a table in the IGW schema within Oracle E-Business Suite, belonging to the Grants Proposal (IGW) product module. It stores information about base amounts or direct costs associated with proposal budget periods, forming part of the reporting infrastructure that supports sponsored-project budgeting in Oracle Grants Management. The table captures the values against which indirect cost rates are applied, enabling accurate computation and reporting of budget-period costs for a given proposal and version.

From a Data Vault modeling perspective, the heuristic classification of this table is satellite-leaning. This suggests the table behaves primarily as an attribute-bearing structure that records descriptive and numeric measures (such as base amounts and rates) attached to a parent business key, rather than acting as a hub of unique business entities or a link resolving many-to-many relationships. In practical EBS terms, it functions as a detail table whose rows are meaningfully dependent on the proposal, version, and budget period context.

Key Information Stored

The table contains ten documented columns in the 12.1.1 physical schema. The most significant columns and their roles are as follows:

• BUDGET_PERIOD_ID — Identifier of the budget period to which the base amount and rate data apply. This is a key component of the primary key and participates in the unique index.
• PROPOSAL_ID — Identifier of the proposal to which the budget period belongs. This is a foreign key to IGW_BUDGET_PERIODS and is part of the composite business key.
• VERSION_ID — Identifier of the proposal version, allowing multiple versions of a proposal to carry distinct base-rate figures.
• BASE_AMOUNT — The base amount or direct cost value against which the indirect rate is applied for the budget period.
• RATE_APPLIED — The indirect cost rate applied to the base amount for the period.
• TOTAL_INDIRECT_COST — The resulting indirect cost computed from the base amount and applied rate.
• START_DATE and END_DATE — The date range defining the budget period.
• FISCAL_YEAR — The fiscal year associated with the budget period, useful for period-based reporting.
• PROPOSAL_FORM_NUMBER — The proposal form number under which the budget data is organized.

The primary key is defined by IGW_REPORT_BUDG_BASE_RATE_PK over (BUDGET_PERIOD_ID, PROPOSAL_ID, VERSION_ID). A unique index, IGW_REPORT_BUDG_BASE_RATE_U1 over (PROPOSAL_ID, VERSION_ID, BUDGET_PERIOD_ID), serves as the business-key candidate, enforcing that no two rows duplicate the same proposal/version/period combination.

Common Use Cases and Queries

This table is typically used in budget reporting and indirect-cost reconciliation. A common reporting query joins proposal budget periods to base-rate rows to produce per-period direct and indirect cost breakdowns:

• Auditing indirect cost calculations by comparing BASE_AMOUNT multiplied by RATE_APPLIED against TOTAL_INDIRECT_COST.
• Producing fiscal-year summaries of direct costs across all budget periods for a proposal version.
• Validating that every budget period for a proposal has an associated base-rate row.
• Extracting period start and end dates for time-phased budget schedules.

A representative SQL pattern is:

SELECT PROPOSAL_ID, VERSION_ID, BUDGET_PERIOD_ID, BASE_AMOUNT, RATE_APPLIED, TOTAL_INDIRECT_COST FROM IGW.IGW_REPORT_BUDGET_BASE_RATE WHERE PROPOSAL_ID = :proposal_id AND VERSION_ID = :version_id ORDER BY START_DATE;

Related Objects

The table's relationships center on the proposal budgeting hierarchy. The most significant related objects are:

• IGW_BUDGET_PERIODS — The parent table referenced through the foreign key columns PROPOSAL_ID, VERSION_ID, and BUDGET_PERIOD_ID. This is the primary relationship underpinning the base-rate rows.
• The unique index IGW_REPORT_BUDG_BASE_RATE_U1 and primary key constraint IGW_REPORT_BUDG_BASE_RATE_PK, which enforce business-key uniqueness.
• Proposal and version entities in the IGW schema, indirectly related through the budget-period linkage.

Because the documented FK data identifies IGW_BUDGET_PERIODS as the sole referenced parent, joins to that table form the core of most reporting and validation queries against this object.