Results for “proposal_end_date”

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

Overview

The IGW_PROP_V view belongs to the IGW – Grants Proposal module, which is designated as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, denormalized snapshot of grant proposal header information by joining proposal master data with principal investigator details, sponsor information, location attributes, cost aggregates, and proposal narrative fields. Its primary role is to expose proposal-level data through a single queryable object so that reporting tools, concurrent programs, and integration touchpoints can retrieve grant proposal information without manually replicating the multi-table join logic.

Because the view bundles computed attributes in addition to stored columns, it functions as a reporting convenience layer rather than a transactional interface. The ETRM metadata notes "Not implemented in this database," indicating that in the documented environment the view is not physically deployed. Nevertheless, the definition remains useful for understanding historical data models and for interpreting legacy Grants Proposal implementations.

Underlying Base Objects

The view is defined over four base objects joined through standard foreign key relationships:

• IGW_PROPOSALS IPA — the proposal master table, supplying proposal identifiers, type codes, sponsor, title, dates, and audit columns.
• IGW_PROP_PERSONS IPP — the association table linking persons to proposals; the join is restricted to rows where PI_FLAG = 'Y', ensuring the principal investigator is selected.
• PER_PEOPLE_X PPX — the person view supplying the full name of the principal investigator.
• RA_CUSTOMERS RC — the customer table supplying the sponsor name, joined on CUSTOMER_ID = SPONSOR_ID.

In addition, several display attributes are produced through functions in a helper package, IGW_VIEW_PARAMETERS, and a cost package, IGW_PROP_COSTS. These functions resolve project location identifiers and names, the major goals narrative, and annual direct and total cost figures at query time. No referenced base objects are separately documented in the ETRM 12.2.2 metadata, so the join logic embedded in the view text serves as the authoritative specification of its dependencies.

Key Columns

• PROPOSAL_ID / PROPOSAL_NUMBER / PROPOSAL_TITLE — core identifiers and descriptive text for the proposal.
• PROPOSAL_TYPE_CODE / SPONSOR_ACTION_CODE — classification and sponsor action status codes used for filtering and categorization.
• PI_ID / PI_NAME — the person identifier and full name of the principal investigator.
• SPONSOR_ID / SPONSOR_NAME — the customer identifier and name of the funding sponsor.
• PROJECT_LOCATION_ID / PROJECT_LOCATION_NAME — resolved project location attributes returned by IGW_VIEW_PARAMETERS functions.
• MAJOR_GOALS — the proposal's major goals text, retrieved via IGW_VIEW_PARAMETERS.GET_MAJOR_GOALS.
• PROPOSAL_START_DATE / PROPOSAL_END_DATE — the performance period boundaries of the proposal.
• ANNUAL_DIRECT_COST / TOTAL_COST — calculated cost metrics obtained through IGW_PROP_COSTS functions.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, inherited from IGW_PROPOSALS.

Common Use Cases and Queries

Typical scenarios include proposal status reports, sponsor funding summaries, and extract loads to downstream reporting systems. Because major_goals is exposed as a first-class column, inquiries focused on that attribute can be satisfied directly:

• Proposal summary by sponsor: select proposal number, title, PI name, and total cost, ordered by sponsor.
• Goals review: retrieve PROPOSAL_NUMBER, PI_NAME, and MAJOR_GOALS for proposals within a date range.
• Cost analysis: aggregate ANNUAL_DIRECT_COST and TOTAL_COST by proposal type or sponsor.

A representative query is:

SELECT proposal_number, proposal_title, pi_name, sponsor_name, major_goals, total_cost FROM igw_prop_v WHERE proposal_start_date >= :start_date AND proposal_end_date <= :end_date ORDER BY sponsor_name, proposal_number;

Because the view relies on stored functions for several columns, performance may be affected when large result sets are requested; filtering on indexed base columns from IGW_PROPOSALS is advisable. Implementations migrating away from the obsolete IGW module should treat this view as a legacy artifact and validate equivalent data sources in the replacement Grants solution.