Results for “igw_prop_rates”

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

Overview

IGW_PROP_RATES is a transactional table in the IGW (Grants Proposal) product module of Oracle E-Business Suite, owned by the IGW schema. It stores information about overriding rates applied to a specific budget version within a grants proposal. In the Oracle EBS Grants Management solution, proposals are developed and costed across multiple budget versions, and each version may require rates that deviate from the institution's standard or negotiated rate schedule. IGW_PROP_RATES captures those overrides, allowing proposal administrators to specify an exact applicable rate and institute rate for a given combination of rate class, rate type, fiscal year, location, and activity type.

From a dimensional modeling perspective, the ETRM metadata classifies this object heuristically as a link table. This classification is consistent with its structure: the table sits at the intersection of the IGW_BUDGETS proposal/version context and the IGW_RATE_TYPES rate definition, resolving a many-to-many-style association through a composite key. Rather than acting as a hub of independent business entities or a satellite of descriptive attributes, its principal role is to record the relationship between a budget version and the rate definitions that apply to it, enriched with the overriding rate amounts themselves.

Key Information Stored

The table contains 16 documented columns. Its primary key, IGW_PROP_RATES_PK, comprises PROPOSAL_ID, VERSION_ID, RATE_CLASS_ID, RATE_TYPE_ID, FISCAL_YEAR, LOCATION_CODE, and ACTIVITY_TYPE_CODE. A unique index, IGW_PROP_RATES_U1, is defined on precisely the same column set, confirming this combination as the business-key candidate that uniquely identifies a rate override row.

The most significant columns include:

• PROPOSAL_ID and VERSION_ID — together identify the proposal and its budget version to which the override applies; these form a foreign key to IGW_BUDGETS.
• RATE_CLASS_ID and RATE_TYPE_ID — reference the rate classification and specific rate type being overridden; these form a foreign key to IGW_RATE_TYPES.
• FISCAL_YEAR — the fiscal year for which the override rate is valid.
• LOCATION_CODE and ACTIVITY_TYPE_CODE — the location and activity context that qualify the rate.
• APPLICABLE_RATE and INSTITUTE_RATE — the overriding rate values stored for the budget version, distinguished by whether they represent the charged applicable rate or the institution's negotiated rate.
• START_DATE — the effective start date of the override.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and RECORD_VERSION_NUMBER.

Common Use Cases and Queries

Typical reporting scenarios include reconciling budget-version rates against the standard IGW_RATE_TYPES schedule, auditing overrides introduced during proposal preparation, and producing rate detail extracts for sponsor submissions. A representative query joining the two foreign-key targets is:

• SELECT r.PROPOSAL_ID, r.VERSION_ID, r.FISCAL_YEAR, r.APPLICABLE_RATE, r.INSTITUTE_RATE FROM IGW.IGW_PROP_RATES r WHERE r.PROPOSAL_ID = :p_proposal AND r.VERSION_ID = :p_version;
• SELECT r.*, rt.RATE_TYPE_NAME FROM IGW.IGW_PROP_RATES r, IGW.IGW_RATE_TYPES rt WHERE r.RATE_CLASS_ID = rt.RATE_CLASS_ID AND r.RATE_TYPE_ID = rt.RATE_TYPE_ID AND r.FISCAL_YEAR = :p_fy;

Because the unique index mirrors the primary key, lookups by the full business key return at most one row, making the table suitable for direct keyed access in concurrent program extracts.

Related Objects

• IGW_BUDGETS — referenced via PROPOSAL_ID and VERSION_ID; the parent budget-version context.
• IGW_RATE_TYPES — referenced via RATE_CLASS_ID and RATE_TYPE_ID; defines the rate being overridden.
• IGW_PROP_RATES_PK — the primary key constraint enforcing uniqueness.
• IGW_PROP_RATES_U1 — the unique index underpinning the business key.

These relationships establish IGW_PROP_RATES as a dependent link between budget versions and rate definitions, and queries against it should generally be driven from IGW_BUDGETS or joined to IGW_RATE_TYPES for descriptive rate information.