Search Results p3_amt




Overview
Explore in AI Chat

Overview

IGW_DETAIL_AMTS_SUM_V is a reporting view historically shipped with the Oracle Grants Proposal (IGW) module, a component of Oracle E-Business Suite releases 12.1.1 and 12.2.2. The Grants Proposal product has since been classified as obsolete, and the ETRM metadata explicitly records this view as "Not implemented in this database," meaning it is not deployed in current installations. Its purpose, as reflected in both its name and its SQL definition, is to present overhead or indirect cost detail amounts pivoted across four consecutive budget periods for a given proposal, version, and period of interest.

The view does not store data; it is a pure derivation layer. It reshapes the output of IGW_OH_TEMP_V, a temporary overhead calculation view, into a fixed-column format (P1_AMT through P4_AMT) that report and page layouts in the Grants Proposal HTML interface could consume. Because the view references IGW_BUDGET_OPERATIONS and IGW_OH_TEMP_V rather than documented base tables, it sits at the tail end of the Grants Proposal calculation chain, closest to the user interface.

Underlying Base Objects

Per the ETRM metadata, no base tables are documented as referenced objects; the view is instead defined over the temporary view IGW_OH_TEMP_V, which supplies four attributes: DESCRIPTION (aliased as EXPENDITURE_TYPE), CALCULATED_COST, RATE_CLASS_ID, and the keying columns PROPOSAL_ID, VERSION_ID, and BUDGET_PERIOD_ID. The view also calls the package functions IGW_BUDGET_OPERATIONS.GET_PROPOSAL_ID, GET_VERSION_ID, and GET_PERIOD_ID, which supply the current session context — the proposal, version, and starting period the user is working with.

The SQL is a four-way UNION ALL of IGW_OH_TEMP_V against itself, filtering on the session context and on BUDGET_PERIOD_ID at the base period (P1), +1 (P2), +2 (P3), and +3 (P4). Because the base view is temporary by name and by design, no persistent data dictionary dependency exists for this object.

Key Columns

  • EXPENDITURE_TYPE — Carried from IGW_OH_TEMP_V.DESCRIPTION; identifies the overhead or expenditure category to which the amounts apply.
  • P1_AMT — CALCULATED_COST for the budget period returned by IGW_BUDGET_OPERATIONS.GET_PERIOD_ID. Null in the other three UNION branches.
  • P2_AMT — CALCULATED_COST for the next period (base + 1). This is the column most commonly referenced in searches for "p2_amt," since it is the second period amount in the detail summary grid and is frequently cited in customizations and report queries.
  • P3_AMT — CALCULATED_COST for base + 2; null in other branches.
  • P4_AMT — CALCULATED_COST for base + 3; null in other branches.
  • RATE_CLASS_ID — Identifier of the overhead rate class applied, allowing the amounts to be grouped by rate type.

Each row is therefore horizontally sparse: exactly one of the four period columns is populated, with the remaining three returned as TO_NUMBER(NULL). The rows are not consolidated, so consumers must aggregate if a single row per expenditure type and rate class is required.

Common Use Cases and Queries

The canonical access pattern selects the pivot columns for the currently active proposal and budget periods. A representative query is:

SELECT expenditure_type, p1_amt, p2_amt, p3_amt, p4_amt, rate_class_id
FROM igw_detail_amts_sum_v
ORDER BY expenditure_type, rate_class_id;

Where a single consolidated line per expenditure type is required, the sparse layout is collapsed with aggregation:

SELECT expenditure_type, rate_class_id,
  SUM(NVL(p1_amt,0)) p1, SUM(NVL(p2_amt,0)) p2,
  SUM(NVL(p3_amt,0)) p3, SUM(NVL(p4_amt,0)) p4
FROM igw_detail_amts_sum_v
GROUP BY expenditure_type, rate_class_id;

In practice, this view was used to populate multi-period overhead detail grid regions in the Grants Proposal budget pages, and by extension in any custom concurrent program or XML Publisher report that needed a fixed four-period overhead summary for the active proposal context. Because the view depends on session context set through IGW_BUDGET_OPERATIONS, attempts to query it outside a Grants Proposal session return no rows. Given its obsolete status and the "not implemented" designation, references to igw_detail_amts_sum_v should be treated as legacy and replaced with current indirect cost reporting sources on supported releases.