Search Results igw_expenditure_type_sum_v




Overview
Explore in AI Chat

Overview

The IGW_EXPENDITURE_TYPE_SUM_V view is a reporting object owned by the APPS schema and delivered as part of the IGW – Grants Proposal module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented status is VALID. The ETRM metadata classifies the object as "10SC Only," indicating that the view is restricted to the 10SC (Grants) licensing context rather than being a general-purpose EBS object.

Functionally, the view presents budget line-item costs from the Grants budget detail table, pivoted across four consecutive budget periods. Instead of returning one row per period, it aggregates each expenditure type into a single row whose P1_AMT through P4_AMT columns correspond to the current period, the current period plus one, the current period plus two, and the current period plus three, respectively. This "sum across four periods" shape (reflected in the _SUM_V suffix) makes the view suitable for period-comparison reporting in proposal budgeting and for integration into custom forms, concurrent programs, or BI Publisher layouts that require a horizontally oriented budget view.

Underlying Base Objects

The view is defined over a single documented base object: IGW_BUDGET_DETAILS. The view text is a four-branch UNION, with each branch selecting the same set of columns from IGW_BUDGET_DETAILS filtered by proposal, version, and a specific budget period. The filtering relies on three packaged functions in IGW_BUDGET_OPERATIONS:

  • GET_PROPOSAL_ID — supplies the current proposal identifier.
  • GET_VERSION_ID — supplies the current budget version.
  • GET_PERIOD_ID — supplies the base budget period; the view extends it as +1, +2, and +3 in the subsequent UNION branches.

Because the period offset is expressed as an arithmetic increment on GET_PERIOD_ID rather than as a natural join to a period table, the view assumes contiguous, sequential budget periods. In each branch, the column LINE_ITEM_COST is projected into exactly one of P1_AMT through P4_AMT, while the other three columns are explicitly assigned NULL via nested TO_NUMBER(NULL) conversions. The RATE_CLASS_ID column is hard-coded as the literal 0 in every branch and does not derive from the base table. The ETRM metadata does not document any additional referenced base objects.

Key Columns

  • EXPENDITURE_TYPE — the expenditure type from the budget line, carried through every UNION branch and serving as the effective grouping key of the view.
  • P1_AMT — the LINE_ITEM_COST associated with budget period GET_PERIOD_ID (the current period).
  • P2_AMT — the LINE_ITEM_COST for budget period GET_PERIOD_ID + 1.
  • P3_AMT — the LINE_ITEM_COST for budget period GET_PERIOD_ID + 2.
  • P4_AMT — the LINE_ITEM_COST for budget period GET_PERIOD_ID + 3.
  • RATE_CLASS_ID — always 0; retained for interface conformity rather than conveying rate-class information.

Because each UNION branch produces separate rows, a given expenditure type can appear in up to four rows, with only the matching Pn_AMT column populated per row.

Common Use Cases and Queries

Typical uses include proposal budget reporting, four-period expenditure-type comparisons, and feeding custom Grants reporting extensions. A representative query selecting all rows is:

  • SELECT EXPENDITURE_TYPE, P1_AMT, P2_AMT, P3_AMT, P4_AMT, RATE_CLASS_ID FROM APPS.IGW_EXPENDITURE_TYPE_SUM_V;

To present one consolidated row per expenditure type, callers can wrap the view in an aggregate, for example:

  • SELECT EXPENDITURE_TYPE, 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 APPS.IGW_EXPENDITURE_TYPE_SUM_V GROUP BY EXPENDITURE_TYPE;

Queries against this view must run within the context expected by the IGW_BUDGET_OPERATIONS functions; the proposal, version, and period values are supplied through that package rather than through bind parameters, so results depend on the current Grants session state.