Results for “calculated_cost”

48 results




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

Overview

IGWBV_GRANT_PRPSL_BDGT_LIN_AMT is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGW - Grants Proposal product family. The view exposes calculated budget line amounts for grant proposals, joining proposal header information to pre-computed cost and cost-sharing figures held at the budget detail level. Its definition is explicitly declared WITH READ ONLY, which confirms that the object is intended purely for query, reporting, and integration consumption rather than for transactional data maintenance.

The view carries a VALID status in the ETRM metadata for both 12.1.1 and 12.2.2, indicating that the definition is stable across these release lines. Because it consolidates proposal identification with versioned, period-level, and line-level calculated amounts, it is typically consumed by inquiry forms, concurrent reporting programs, and external interfaces that need to present budget cost rollups without navigating the full normalized budgeting model.

Underlying Base Objects

The view text identifies two base objects:

The join predicate is a single equi-join: PR.PROPOSAL_ID = CAL_AMTS.PROPOSAL_ID. No outer join is present, so rows in the calculated-amounts table without a matching proposal record are excluded. The view is therefore a denormalized projection of the calculated-amounts entity enriched only with the proposal number.

Key Columns

  • PROPOSAL_NUMBER — business-facing identifier of the grant proposal, sourced from IGW_PROPOSALS_ALL.
  • VERSION_ID — the budget version to which the calculated amount belongs; exposed in the column list as BUDGET_VERSION_ID.
  • PROPOSAL_ID — internal surrogate key of the proposal, the primary join attribute.
  • BUDGET_PERIOD_ID — identifies the budget period within the version, enabling period-by-period reporting.
  • LINE_ITEM_ID — the budget line item against which costs are calculated.
  • RATE_CLASS_ID and RATE_TYPE_ID — the rate classification and rate type used to derive the calculated amounts.
  • APPLY_RATE_FLAG — indicates whether rate application was performed for the row.
  • CALCULATED_COST — the computed cost amount for the line/period combination.
  • CALCULATED_COST_SHARING — the computed cost-sharing amount, reported separately from the base cost.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE are carried through from the calculated-amounts table.

Note that the documented column listing labels the second column BUDGET_VERSION_ID while the select list names it VERSION_ID; consumers should reference the exposed column name when querying.

Common Use Cases and Queries

The most frequent scenario is retrieving calculated cost and cost-sharing totals for a proposal at line and period granularity, typically filtered by proposal number or by version. Because the view is read-only, it is safe to embed in custom reports and OBIEE or BI Publisher data models without transactional risk.

A representative filtered query:

  • SELECT proposal_number, budget_version_id, budget_period_id, line_item_id, calculated_cost, calculated_cost_sharing FROM igwbv_grant_prpsl_bdgt_lin_amt WHERE proposal_number = :p_proposal_number ORDER BY budget_period_id, line_item_id;

Aggregated cost rollup by version and period:

  • SELECT proposal_number, budget_version_id, budget_period_id, SUM(calculated_cost) tot_cost, SUM(calculated_cost_sharing) tot_sharing FROM igwbv_grant_prpsl_bdgt_lin_amt WHERE proposal_id = :p_proposal_id GROUP BY proposal_number, budget_version_id, budget_period_id;

Rate-driven analysis, isolating rows where rates were applied:

  • SELECT proposal_number, rate_class_id, rate_type_id, calculated_cost FROM igwbv_grant_prpsl_bdgt_lin_amt WHERE apply_rate_flag = 'Y' AND proposal_id = :p_proposal_id;

These patterns support proposal budget review, indirect cost verification, and downstream integration extracts into costing or reporting repositories.