Results for “igw_exp_type_rate_types”

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

Overview

The IGW_EXP_TYPE_RATE_TYPES table is a core configuration object within the Oracle E-Business Suite Grants Proposal (IGW) module. It stores the mapping between expenditure categories, rate classes, and rate types, defining which expenditure categories are associated with a particular rate class and rate type combination. This mapping is fundamental to indirect cost rate calculation in the grants proposal and award lifecycle, where sponsored project budgets must apply the correct facilities and administrative (F&A), fringe, or other negotiated rates to the appropriate categories of spend.

In the 12.1.1 and 12.2.2 releases, the object resides in the IGW schema and is classified as VALID in the ETRM repository. Applying Data Vault modeling heuristics, the FK structure is satellite-leaning: the primary key is a composite of business columns rather than a generated surrogate, and the table primarily carries descriptive relationship attributes and audit columns rather than serving as a pure hub or link. Modeling it as a satellite around rate and expenditure category concepts is therefore a reasonable design suggestion.

Key Information Stored

The table comprises eight documented columns. The most significant are the three business-key columns forming the primary key and its supporting unique index.

• EXPENDITURE_CATEGORY — Identifies the expenditure category (for example, a spend classification such as supplies or travel) to which a rate definition applies. It is the first component of the composite key.
• RATE_CLASS_ID — Foreign key to IGW_RATE_TYPES, identifying the rate class (such as a specific F&A or fringe class). Also a key component.
• RATE_TYPE_ID — Foreign key within the same IGW_RATE_TYPES relationship, identifying the rate type (such as on-campus or off-campus) that qualifies the rate class.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO-column audit attributes recording insertion and modification context.

The surrogate-style primary key is documented as IGW_EXP_RATE_TYPES_PK over (EXPENDITURE_CATEGORY, RATE_CLASS_ID, RATE_TYPE_ID), with the unique index IGW_EXP_RATE_TYPES_U1 defined over the identical column set. Both the primary key and the unique index are therefore business-key candidates; no separate generated surrogate identifier exists in the documented metadata.

Common Use Cases and Queries

The primary use case is resolving, for a given rate class and rate type, the set of expenditure categories eligible for that rate. Typical reporting and validation queries join to IGW_RATE_TYPES on both RATE_CLASS_ID and RATE_TYPE_ID to retrieve rate descriptions alongside category assignments.

• Verifying that every required expenditure category has at least one rate class/type assignment before rate calculation runs.
• Producing configuration reports that list rate class and type assignments by expenditure category for grants administrators.
• Detecting duplicate or orphaned category assignments by comparing the business key against IGW_RATE_TYPES.
• Auditing configuration changes using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

A representative pattern selects the three key columns plus audit columns, filtered by RATE_CLASS_ID and RATE_TYPE_ID, and joins to IGW_RATE_TYPES on the matching foreign key columns.

Related Objects

The most significant related object is IGW_RATE_TYPES, the parent of the foreign key relationship. IGW_EXP_TYPE_RATE_TYPES joins to IGW_RATE_TYPES through RATE_CLASS_ID and RATE_TYPE_ID. These rate definitions drive downstream indirect cost calculation logic and proposal budget generation within the Grants Proposal module. Because the metadata documents only this single foreign key relationship, additional dependencies on expenditure category or proposal budget components should be validated against the IGW schema directly in the target environment.