Results for “narrative_submission”

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

Overview

IGWBV_GRANT_PROPOSAL is a read-only database view associated with the Oracle E-Business Suite Grants Proposal module (product code IGW). In the ETRM metadata for releases 12.1.1 and 12.2.2, the module is explicitly flagged as Obsolete, and the object itself is documented with the note "Not implemented in this database." This means the view is legacy in nature: it survives as a cataloged definition for historical and upgrade reference, but it is not expected to exist in a current, freshly installed or fully migrated E-Business Suite environment.

The view presents a denormalized, reporting-oriented projection of grant proposal data. Rather than returning raw coded values, it resolves proposal descriptors such as proposal type, activity type, sponsor action, and narrative submission type into human-readable meanings by joining to the IGW lookup view. It also embeds descriptive flexfield and status value-set references through the "_DF:" and "_LA:" attribute conventions, which downstream reporting tools and the Oracle EBS framework interpret at runtime. Its role was to support proposal tracking, grant administration reporting, and integration extracts against the IGW schema.

Underlying Base Objects

The view is defined over IGW_PROPOSALS_ALL as its primary driving table (aliased PR), combined with IGW_LOOKUPS_V referenced six times (aliases LKUP2 through LKUP6) to decode lookup codes. The metadata section documents no referenced base objects in the 12.2.2 ETRM extract, reflecting the object's obsolete and unimplemented status, but the embedded view text confirms the dependencies above.

• IGW_PROPOSALS_ALL — the base proposal table supplying all proposal, award, sponsor, and program attributes.
• IGW_LOOKUPS_V — the lookup view, joined on LOOKUP_TYPE and LOOKUP_CODE to translate code columns into MEANING values for proposal types, activity types, opportunity notice types, sponsor action codes, and narrative submission types.
• IGW_PROP.GET_NARRATIVE_STATUS — a PL/SQL function invoked in the SELECT list to derive the narrative status for each proposal.

Joins to LKUP2 and LKUP3 are mandatory (inner), while LKUP4, LKUP5, and LKUP6 use outer joins, allowing proposals with null optional codes to be returned.

Key Columns

• PROPOSAL_NUMBER / PROPOSAL_TITLE — the identifying number and descriptive title of the grant proposal.
• "_LA:PROPOSAL_STATUS" — a special attribute column resolving proposal status through the IGW_LOOKUPS_V view using the IGW_PROPOSAL_STATUS lookup type.
• PROPOSAL_TYPE, ACTIVITY_TYPE, NARRATIVE_SUBMISSION — decoded MEANING values from the respective lookup joins.
• PROPOSAL_START_DATE / PROPOSAL_END_DATE — the proposal performance period.
• AWARD_NUMBER / AWARD_AMOUNT — award linkage and monetary value.
• SPONSOR_ID / SPONSOR_PROPOSAL_NUMBER / ORIGINAL_SPONSOR_ID — sponsor identification and their reference number.
• LEAD_ORGANIZATION_ID / SUBMITTING_ORGANIZATION_ID / ORG_ID — organization and operating unit context.
• DEADLINE_DATE / DEADLINE_TYPE / LETTER_OF_INTENT_DUE_DATE — submission deadline tracking.
• NARRATIVE_STATUS — computed via IGW_PROP.GET_NARRATIVE_STATUS.
• "_DF:IGW:IGW_PROPOSALS_DESC_FLEX:PR" — descriptive flexfield reference for proposal-level DFF segments.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical usage was to report on active proposals and their decoded attributes without writing repetitive lookup joins.

SELECT proposal_number, proposal_title, proposal_type,
       "PROPOSAL_STATUS", award_amount
FROM   igwbv_grant_proposal
WHERE  proposal_start_date >= :p_from_date
ORDER  BY proposal_number;

Additional scenarios included sponsor-facing extracts requiring SPONSOR_PROPOSAL_NUMBER and AWARD_NUMBER, deadline monitoring queries filtering on DEADLINE_DATE, and integration feeds that consumed NARRATIVE_STATUS. Because the object is documented as obsolete and not implemented in the database, any custom code referencing IGWBV_GRANT_PROPOSAL should be reviewed during 12.1.1 to 12.2.2 upgrades and redirected to surviving IGW or successor grant-management tables.