Search Results eb_total

Overview

APPS.IGW_PRPO_CATEGORY_AMTS_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It falls within the IGW (Grants/Proposal) product family and presents summarized budget information organized by sponsor budget hierarchy. Its stated purpose is to support the generation of flat files for Electronic Data Interchange (EDI), making it a downstream integration object rather than a transactional data-entry object. The view carries FND Design Data identifier IGW.IGW_PRPO_CATEGORY_AMTS_V and holds a VALID status in ETRM. Because it consolidates period-level budget amounts across proposal budget categories, it is particularly relevant to reporting and extract routines concerned with period-based direct cost figures. The user search term "period_total_direct_cost" maps directly to one of the view's exposed columns, confirming that this object is the intended source for that measure.

Underlying Base Objects

The view is defined over the following documented base objects within APPS:

• IGW_BUDGETS — header-level budget records for proposals.
• IGW_BUDGET_DETAILS — line-level budget detail underpinning category amounts.
• IGW_BUDGET_PERIODS — budget period definitions, including start and end dates and period types.
• IGW_REPORT_BUDGET and IGW_REPORT_BUDGET_SEED — reporting-oriented budget structures used to shape the summarized output.
• FND_LOOKUPS — used to resolve lookup-coded values into descriptive text.
• FND_GLOBAL — supplies session context such as the current user and responsibility.

The view is not referenced by any other database object, so it functions as a reporting endpoint. In 12.2.2 ETRM documentation no base objects are separately recorded, but the dependency list above reflects the 12.1.1 metadata and remains applicable as the semantic definition has not materially changed.

Key Columns

• PROPOSAL_ID (NUMBER) — identifies the proposal to which the summarized budget belongs.
• BUDGET_PERIOD_ID (NUMBER) — the budget period identifier.
• PERIOD_TYPE (CHAR) — classification of the budget period.
• START_DATE (DATE) — start date of the budget period.
• PROPOSAL_BUDGET_CATEGORY_CODE (VARCHAR2 30) — coded budget category.
• PROPOSAL_BUDGET_CATEGORY (VARCHAR2 80) — descriptive category name.
• DESCRIPTION (VARCHAR2 250) — additional narrative for the category or line.
• PERIOD_TOTAL_DIRECT_COST (NUMBER) — the summarized direct cost for the period, and the measure most commonly queried by users.
• PERIOD_MONTHS (NUMBER) — number of months spanned by the period.
• PERCENT_DOLLAR_FLAG (VARCHAR2) — indicates whether the amount is expressed as a percentage or a dollar value.
• EB_TOTAL (VARCHAR2 17) — a formatted total value, character-typed for extract output.

Common Use Cases and Queries

Typical uses include EDI flat-file generation for sponsor reporting, period-level direct cost analysis, and reconciliation of summarized category amounts against budget detail. A straightforward query to retrieve period totals by proposal is:

SELECT PROPOSAL_ID,
       BUDGET_PERIOD_ID,
       PERIOD_TYPE,
       START_DATE,
       PROPOSAL_BUDGET_CATEGORY,
       PERIOD_TOTAL_DIRECT_COST,
       PERIOD_MONTHS
FROM   APPS.IGW_PRPO_CATEGORY_AMTS_V
WHERE  PROPOSAL_ID = :proposal_id
ORDER  BY START_DATE, PROPOSAL_BUDGET_CATEGORY;

To aggregate direct cost by category across all periods of a proposal:

SELECT PROPOSAL_ID,
       PROPOSAL_BUDGET_CATEGORY_CODE,
       SUM(PERIOD_TOTAL_DIRECT_COST) AS total_direct_cost
FROM   APPS.IGW_PRPO_CATEGORY_AMTS_V
GROUP  BY PROPOSAL_ID, PROPOSAL_BUDGET_CATEGORY_CODE;

Because the view joins lookup and global context objects, queries should generally be executed under an APPS-enabled responsibility so that FND_GLOBAL session values are populated correctly. Direct SQL against the view is read-only and does not affect transactional data.