Search Results igw_rate_types




Overview
Explore in AI Chat

Overview

The IGW_RATE_TYPES table is a core reference table within the Oracle E-Business Suite Grants Proposal (IGW) module. It functions as a master data repository for defining and storing the specific rate types that are associated with a broader rate class. In the context of grant and proposal management, rate classes categorize costs (e.g., Fringe Benefits, Overhead), while rate types represent the specific calculation methods or tiers within those classes (e.g., a "Graduate" fringe rate versus an "Undergraduate" fringe rate). This table is essential for the accurate configuration and application of indirect cost rates, facilities and administrative (F&A) rates, and other calculated costs on sponsored project proposals, ensuring compliance with institutional and sponsor billing policies.

Key Information Stored

The table's structure is defined by a composite primary key, enforcing uniqueness through the combination of RATE_CLASS_ID and RATE_TYPE_ID. While the provided ETRM metadata does not list all columns, the core data stored includes the identifiers that link a rate type to its parent rate class in the IGW_RATE_CLASSES table. Typical columns in such a reference table would include, but are not limited to, the RATE_TYPE_CODE and a descriptive NAME or DESCRIPTION field for the rate type. The table likely also contains standard Oracle EBS audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY to track data history. The integrity of the data is maintained through the primary key constraint (IGW_RATE_TYPES_PK) and a foreign key relationship to the IGW_RATE_CLASSES table.

Common Use Cases and Queries

This table is primarily accessed during the setup and maintenance of rate structures, and during the runtime calculation of proposal costs. Common operational and reporting scenarios include validating rate configurations, listing all available rate types for a given class, and troubleshooting rate application issues. A typical query would join IGW_RATE_TYPES to IGW_RATE_CLASSES to produce a human-readable list. For example:

  • SELECT rcl.rate_class_code, rtp.rate_type_code, rtp.name
  • FROM igw_rate_types rtp, igw_rate_classes rcl
  • WHERE rtp.rate_class_id = rcl.rate_class_id
  • ORDER BY rcl.rate_class_code, rtp.rate_type_code;

This data is also critical for downstream processes when specific rates (stored in IGW_PROP_RATES or IGW_INSTITUTE_RATES) are applied to expenditure types or proposal line items, ensuring the correct rate type identifier is propagated through the costing engine.

Related Objects

The IGW_RATE_TYPES table sits at the center of a key data model for rates in Grants Proposal. As documented in the foreign key metadata, it has direct relationships with several important transactional and setup tables:

  • IGW_RATE_CLASSES: The parent table, defining the overarching class to which a rate type belongs.
  • IGW_EXP_TYPE_RATE_TYPES: Links expenditure types to valid rate types, controlling which rates can be applied to specific costs.
  • IGW_INSTITUTE_RATES: Stores the institution's standard or baseline rates for each rate class and type combination.
  • IGW_PROP_RATES: Stores proposal-specific rates, which may override institute rates, for a given rate class and type.

These relationships illustrate that IGW_RATE_TYPES is a fundamental reference point for the entire rate assignment and application workflow within the module.