Results for “igwfv_grant_proposal”

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

Overview

The view IGWFV_GRANT_PROPOSAL belongs to the Oracle EBS product family IGW — Grants Proposal, which is documented as Obsolete in the ETRM reference metadata for releases 12.1.1 and 12.2.2. The view is classified as a descriptive or "flexfield" view (indicated by the naming convention ...FV...), intended to expose grants proposal header information in a denormalized, reporting-friendly layout. Its role in Oracle EBS is to present a consolidated projection of grants proposals, joining proposal base data to lookup meanings, organization names, and sponsor (customer) names so that the information can be consumed by Oracle Grants Proposal forms, Oracle Discoverer workbooks, and other reporting or integration layers without requiring the caller to reconstruct the joins manually.

The metadata explicitly records this object as "Not implemented in this database" and lists no documented base objects at the 12.2.2 release level, which is consistent with the Obsolete product designation. The view text is nevertheless preserved in the documentation, permitting reconstruction of its intended purpose even where the object is absent from a live instance.

Underlying Base Objects

Although the ETRM metadata records no referenced base objects, the documented view text reveals its true definition. The view is built from:

• IGW_PROPOSALS_ALL — the primary grants proposal table, aliased as PR.
• IGW_LOOKUPS_V — joined six times (LKUP2 through LKUP6) to resolve proposal type, activity type, notice of opportunity, sponsor action, and narrative submission codes into their display meanings.
• HR_ALL_ORGANIZATION_UNITS — aliased HR2 and HR3, providing organization unit names.
• RA_CUSTOMERS — aliased RA1 (sponsor name) and RA2 (secondary customer name), linking proposals to their funding sponsors through the Receivables customer model.

This relationship to RA_CUSTOMERS is significant for users searching on that term: the sponsor identity in Grants Proposal is resolved directly from the Receivables customer master, meaning sponsor data is shared with the AR module rather than maintained in a grants-specific table. Lookup joins for opportunity notice, sponsor action, and narrative submission types are outer joins ((+)), while proposal type and activity type are mandatory inner joins.

Key Columns

• PROPOSAL_NUMBER, PROPOSAL_TITLE, PROPOSAL_START_DATE, PROPOSAL_END_DATE — core proposal identification and period.
• PROPOSAL_TYPE / ACTIVITY_TYPE — lookup meanings derived from IGW_LOOKUPS_V.
• AWARD_NUMBER, AWARD_AMOUNT — award linkage and monetary value.
• SPONSOR_NAME (RA1.CUSTOMER_NAME), SPONSOR_ID, SPONSOR_PROPOSAL_NUMBER — the sponsoring party, sourced from RA_CUSTOMERS.
• NARRATIVE_STATUS — computed through the database function IGW_PROP.GET_NARRATIVE_STATUS(PR.PROPOSAL_ID).
• ORG_ID — the operating unit context for multi-org security.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY — standard audit columns.
• PROPOSAL_ID, LEAD_ORGANIZATION_ID, SUBMITTING_ORGANIZATION_ID — internal keys useful for joining to detail tables.

Common Use Cases and Queries

Typical usage centers on sponsor-facing reporting and proposal tracking. A user researching the relationship between grants proposals and Receivables customers would query:

• SELECT PROPOSAL_NUMBER, PROPOSAL_TITLE, SPONSOR_NAME, AWARD_AMOUNT FROM IGWFV_GRANT_PROPOSAL WHERE SPONSOR_NAME LIKE '%FOUNDATION%';
• SELECT PROPOSAL_NUMBER, PROPOSAL_TYPE, ACTIVITY_TYPE, NARRATIVE_STATUS FROM IGWFV_GRANT_PROPOSAL WHERE ORG_ID = :p_org_id;

Because the object is documented as not implemented and the product is obsolete, any query must first verify existence in ALL_VIEWS. If absent, successor objects in the later Oracle Grants Management schema should be substituted.