Results for “proposal_award_title”

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

Overview

IGWBV_GRNT_PRPSL_PERS_OTHR_SUP is a read-only Oracle EBS view owned by the APPS schema in the IGW (Grants Proposal) product family. Its status is VALID in both release 12.1.1 and 12.2.2. The view presents person-level "other support" information associated with grant proposals — that is, details of sponsored or externally funded support that a proposal person (Principal Investigator, co-investigator, or key personnel) receives, allowing grant administrators to assess overlap, effort, and cost commitments across funding sources.

The naming convention follows Oracle's Grants suite: the "BV" segment denotes a business view, "IGW" the Grants Proposals module, and the suffix "OTH_SUP" the "other support" business subject area. The view is designed for reporting and integration rather than transaction processing; it carries the WITH READ ONLY clause, so it cannot be used for DML.

The view exposes proposal header attributes joined with person-support detail rows, including labor distribution dates across calendar, academic, and summer periods, percent effort, direct and total costs, major goals, and overlap indicators.

Underlying Base Objects

The view is defined over exactly two base tables in the APPS schema:

• IGW_PROP_PERSON_SUPPORT (PPS) — the driving detail table holding person-support records tied to a proposal, including effort, cost, period dates, and overlap information.
• IGW_PROPOSALS_ALL (PR) — the proposal header table supplying the proposal number and linking via PROPOSAL_ID.

The join condition is PR.PROPOSAL_ID = PPS.PROPOSAL_ID, an inner join, so only person-support rows with a matching proposal header are returned. No additional documented base objects exist in the ETRM metadata; the view is a straightforward two-table join with no documented aggregation.

Key Columns

• PROPOSAL_NUMBER — the user-facing identifier of the grant proposal from IGW_PROPOSALS_ALL.
• "_LA:SUPPORT_TYPE" — a descriptive flexfield/lookup marker resolving to IGW_SUPPORT_TYPES meanings; the literal prefix signals a lookup substitution in the reporting layer.
• PROPOSAL_AWARD_NUMBER, PROPOSAL_AWARD_TITLE — sponsor award reference and title carried on the support record.
• START_DATE, END_DATE — overall support period; PERCENT_EFFORT reflects committed effort.
• ANNUAL_DIRECT_COST, TOTAL_COST — financial magnitude of the support.
• CALENDAR_START_DATE / CALENDAR_END_DATE, ACADEMIC_*, SUMMER_* — period boundaries by appointment basis.
• MAJOR_GOALS, OVERLAP — narrative and flag for overlap determination.
• "_DF" — a descriptive flexfield marker tied to IGW_PERSON_SUPPORT_DESC_FLEX.
• PROP_PERSON_SUPPORT_ID, PROPOSAL_ID, PERSON_ID, PI_PERSON_ID, SPONSOR_ID — primary keys and foreign keys for drill-through and joins.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Typical scenarios include other-support disclosure review, effort certification, and overlap analysis before award acceptance. A basic query by proposal:

SELECT proposal_number, percent_effort, total_cost,
       calendar_start_date, calendar_end_date, overlap
  FROM apps.igwbv_grnt_prpsl_pers_othr_sup
 WHERE proposal_number = :p_proposal_number;

To examine all other-support records for a specific person across proposals:

SELECT person_id, proposal_number, proposal_award_title,
       start_date, end_date, percent_effort, total_cost
  FROM apps.igwbv_grnt_prpsl_pers_othr_sup
 WHERE person_id = :p_person_id
 ORDER BY start_date;

The view is commonly consumed by OBIEE/BI Publisher extracts and by custom Grants dashboards. Because flexfield markers appear as column aliases, reports typically resolve them through the lookup and flexfield machinery rather than expecting literal stored values.