Search Results igw_prop_rates

Overview

The IGW_PROP_RATES table is a core data object within the Oracle E-Business Suite (EBS) Grants Proposal (IGW) module. It serves as the primary repository for storing manually defined or overridden indirect cost rates for a specific budget version within a grant or contract proposal. This table enables proposal managers and financial administrators to apply custom rate calculations that deviate from the standard rates defined in the system, providing the flexibility required for complex grant budgeting and compliance with specific sponsor guidelines. Its existence is critical for maintaining detailed audit trails of budget calculations and ensuring that proposal budgets accurately reflect negotiated or mandated indirect cost structures.

Key Information Stored

The table's structure is designed to uniquely identify a specific rate override within the context of a proposal budget. Its composite primary key highlights the essential dimensions of the data: the proposal itself (PROPOSAL_ID), the specific budget version (VERSION_ID), the category of rate (RATE_CLASS_ID), the precise rate type (RATE_TYPE_ID), and the applicable fiscal period (FISCAL_YEAR). Additional columns like LOCATION_CODE and ACTIVITY_TYPE_CODE allow for further granularity, enabling rate overrides to be applied based on organizational unit or the nature of the work performed. The table's foreign key relationships to IGW_BUDGETS and IGW_RATE_TYPES enforce referential integrity, ensuring that all overrides are linked to a valid budget version and a defined rate structure within the system.

Common Use Cases and Queries

A primary use case is the review and audit of all custom rates applied to a proposal budget, often for internal compliance checks or sponsor submissions. A financial analyst might run a query to list all overridden rates for a specific proposal version. Another common scenario involves troubleshooting budget totals; if calculated indirect costs seem incorrect, a query against this table can confirm whether any manual overrides are in effect and what their values are. Sample SQL to retrieve this information would typically join IGW_PROP_RATES with IGW_BUDGETS and descriptive tables like IGW_RATE_TYPES_TL for translated names.

• Sample Query Pattern: SELECT prop.proposal_number, b.version_name, rt.rate_class_code, rt.rate_type_code, pr.fiscal_year, pr.location_code, pr.activity_type_code FROM igw_prop_rates pr, igw_budgets b, igw_proposals_all prop, igw_rate_types rt WHERE pr.proposal_id = b.proposal_id AND pr.version_id = b.version_id AND b.proposal_id = prop.proposal_id AND pr.rate_class_id = rt.rate_class_id AND pr.rate_type_id = rt.rate_type_id AND prop.proposal_id = :p_proposal_id;

Related Objects

IGW_PROP_RATES is centrally connected to other key tables in the Grants Proposal schema. Its defining relationship is with the IGW_BUDGETS table, as every rate override must be scoped to a specific budget version (PROPOSAL_ID, VERSION_ID). It also depends on the IGW_RATE_TYPES table to validate the RATE_CLASS_ID and RATE_TYPE_ID combinations. While not listed in the provided metadata, this table is likely referenced by various budget calculation engines and reporting views within the IGW module. Data from IGW_PROP_RATES may flow into formal budget reports and interfaces with other EBS financial modules, such as Projects (PA), during award setup and post-award financial management.