Search Results program_income_source




Overview
Explore in AI Chat

Overview

The IGW_BUDGET_PERIODS_V view is a reporting and integration object within the Oracle E-Business Suite IGW – Grants Proposal module. The IGW product family supports the management of sponsored research proposals, grant applications, and related budgeting activities, primarily in the North American higher-education and research-institute verticals. Note that the ETRM documentation classifies this object with the description "10SC Only," indicating it is a release-specific artifact tied to the 10SC (industry-specific) designation rather than a general-purpose global object available across every installation configuration.

Functionally, the view presents a denormalized, read-friendly projection of budget period information for proposals. Each row represents a single budget period defined against a specific proposal and version, and exposes the aggregated financial totals associated with that period. Because a proposal often spans multiple budget periods (for example, annual periods across a multi-year award), consumers of this view can retrieve period-by-period cost breakdowns without having to navigate the more granular underlying budgeting tables. It is commonly consumed by custom reports, concurrent programs, and integration interfaces that populate downstream financial or analytical systems. Direct DML against the view is not supported; it is intended strictly for query and extraction.

Underlying Base Objects

The view is defined over a single base table, IGW_BUDGET_PERIODS, owned by the APPS schema. The column list in the view is a one-to-one projection of the columns in that base table, with no joins, aggregations, or computed expressions present in the documented view text. This design means the view acts as a controlled, stable read interface over the underlying table, insulating downstream consumers from any physical reorganization of the base object while still reflecting its current state.

The absence of documented joins is significant: all descriptive attributes of a budget period — including its start and end dates, its cost components, and its audit columns — reside directly in IGW_BUDGET_PERIODS. Contextual information such as the proposal name, sponsor, or organization must be obtained by joining this view to other proposal- and version-level objects using PROPOSAL_ID and VERSION_ID. Because the view does not resolve those foreign keys itself, any join work is the responsibility of the consumer query.

Key Columns

  • PROPOSAL_ID – Identifier of the parent proposal to which the budget period belongs.
  • VERSION_ID – Identifier of the specific proposal version. Together with PROPOSAL_ID, this forms the natural key context for a budget period.
  • BUDGET_PERIOD_ID – Unique identifier of the budget period record.
  • START_DATE / END_DATE – The begin and end dates that bound the budget period.
  • TOTAL_DIRECT_COST – The sum of direct costs attributable to the period; this is the column most frequently referenced by users searching for total_direct_cost.
  • TOTAL_INDIRECT_COST – Indirect (facilities and administrative) costs loaded against the period.
  • TOTAL_COST – Combined total cost, generally the sum of direct and indirect costs for the period.
  • COST_SHARING_AMOUNT – The portion of period cost borne by the institution rather than the sponsor.
  • UNDERRECOVERY_AMOUNT – Costs not recovered, typically where negotiated rates exceed applied rates.
  • TOTAL_COST_LIMIT – Any ceiling imposed on allowable cost for the period.
  • PROGRAM_INCOME / PROGRAM_INCOME_SOURCE – Income and its source that offsets period cost.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – Standard EBS audit columns for change tracking and interface reconciliation.

Common Use Cases and Queries

A typical requirement is to extract the direct cost totals for every budget period of a given proposal and version, often for sponsor reporting or for load into a data warehouse. The following query illustrates the pattern:

SELECT PROPOSAL_ID, VERSION_ID, BUDGET_PERIOD_ID,
START_DATE, END_DATE,
TOTAL_DIRECT_COST, TOTAL_INDIRECT_COST, TOTAL_COST
FROM APPS.IGW_BUDGET_PERIODS_V
WHERE PROPOSAL_ID = :p_proposal_id
AND VERSION_ID = :p_version_id
ORDER BY START_DATE;

Because audit columns are exposed, the view is also useful for incremental extraction: filtering on LAST_UPDATE_DATE allows an interface to pull only changed periods. Similarly, comparing TOTAL_DIRECT_COST plus TOTAL_INDIRECT_COST against TOTAL_COST provides a quick data-integrity check, and contrasting TOTAL_COST against TOTAL_COST_LIMIT supports cost-ceiling monitoring. Any consumer requiring sponsor or organization detail should join back to the appropriate proposal-level objects on PROPOSAL_ID and VERSION_ID. Given the "10SC Only" designation, implementations should confirm the object's applicability to their specific configuration and release level before relying on it in a production interface.