Search Results calculated_cost_sharing




Overview
Explore in AI Chat

Overview

IGW_BUDGET_DETAILS_AMTS_V is an Oracle EBS APPS-tier view used by the Grants Management (IGW) module to expose calculated budget amounts associated with proposal line items and rate schedules. It is a thin projection over the IGW_BUDGET_DETAILS_CAL_AMTS table, meaning the view does not perform joins or transformations — it simply selects a defined set of columns from the base table. This design indicates the view exists primarily to provide a stable, read-only interface for reporting, integration, and concurrent program consumption without exposing every column of the underlying table.

Budget amounts in IGW are the result of applying rate schedules (indirect cost rates, cost-sharing rules, and rate types) against a proposal's line items across budget periods. The columns exposed by this view capture those computed values, including the calculated cost and calculated cost sharing, which are the outputs of the rate application process. Because the view is defined over the CAL_AMTS (calculated amounts) table rather than a staging or input table, it represents post-calculation data — amounts that have already been derived by the budget generation logic.

Underlying Base Objects

Per the documented metadata, the view is defined solely over IGW_BUDGET_DETAILS_CAL_AMTS, with no additional base objects or joins documented. The view text is a direct column projection:

Because no joins are present, query performance is essentially equivalent to querying the base table directly. Any DML on the base table is immediately reflected in the view; there is no materialization. The view inherits the base table's partitioning, indexes, and constraints, so the primary key and supporting indexes on IGW_BUDGET_DETAILS_CAL_AMTS remain fully usable through the view.

Key Columns

The key columns center on the calculation output and its dimensional context:

  • CALCULATED_COST — The computed cost for the line item after applying the relevant rate schedule and rate type. This is the primary value users search for when reconciling budget totals.
  • CALCULATED_COST_SHARING — The portion of the calculated cost attributed to cost sharing, derived from the cost-sharing configuration on the proposal.
  • APPLY_RATE_FLAG — Indicates whether a rate was applied to the line item, allowing users to distinguish rated from non-rated lines.
  • RATE_CLASS_ID / RATE_TYPE_ID — Identify the rate class and rate type used in the calculation, enabling traceability back to the rate schedule.
  • PROPOSAL_ID / VERSION_ID — Locate the calculation within a specific proposal and version, since proposals may have multiple versions.
  • BUDGET_PERIOD_ID / LINE_ITEM_ID — Provide period-level and line-level granularity.
  • Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — Standard EBS who-columns for change tracking.

Common Use Cases and Queries

The view is typically consumed to reconcile calculated costs against budget totals, to validate rate application results, and to feed downstream reporting or integration extracts. A common pattern retrieves calculated cost and cost sharing for a given proposal and version:

SELECT proposal_id, version_id, budget_period_id, line_item_id,
rate_class_id, rate_type_id, calculated_cost, calculated_cost_sharing
FROM apps.igw_budget_details_amts_v
WHERE proposal_id = :p_proposal_id
AND version_id = :p_version_id
ORDER BY budget_period_id, line_item_id;

To isolate lines where a rate was actually applied:

SELECT proposal_id, version_id, line_item_id, calculated_cost
FROM apps.igw_budget_details_amts_v
WHERE apply_rate_flag = 'Y'
AND proposal_id = :p_proposal_id;

For reconciliation against totals, aggregate by proposal and version:

SELECT proposal_id, version_id,
SUM(calculated_cost) AS total_cost,
SUM(calculated_cost_sharing) AS total_cost_sharing
FROM apps.igw_budget_details_amts_v
GROUP BY proposal_id, version_id;

Given the direct projection and absence of joins, queries against this view are efficient provided the underlying table is indexed on PROPOSAL_ID and VERSION_ID. Users searching on calculated_cost should note the value represents the post-rate-application result and is only meaningful when APPLY_RATE_FLAG is set.