Search Results igw_prop_narratives
Overview
The IGW_PROP_NARRATIVES table is a core data object within the Oracle E-Business Suite (EBS) Grants Proposal module (IGW). It functions as the primary repository for storing narrative text and associated metadata that forms a critical component of a formal grant proposal. Narratives are detailed, descriptive sections—such as the project description, methodology, or budget justification—required by funding agencies. The table's role is to maintain these textual components, linking them to specific proposals and organizing them by functional module, thereby enabling the assembly, versioning, and submission of complete proposal packages.
Key Information Stored
The table's structure centers on a composite primary key that uniquely identifies each narrative section. The most significant columns include PROPOSAL_ID, which is a foreign key linking the narrative to its parent proposal record in IGW_PROPOSALS_ALL. The MODULE_ID column categorizes the narrative by type or section (e.g., technical approach, facilities). While the specific metadata columns are not detailed in the provided excerpt, typical narrative tables in this context store columns for the narrative text itself (often a CLOB or LONG datatype), a version number, the creation and last update dates, and the status of the narrative section. The defined primary key constraint IGW_NARRATIVE_PK enforces uniqueness on the combination of PROPOSAL_ID and MODULE_ID.
Common Use Cases and Queries
This table is central to proposal development and reporting workflows. Common operational use cases include retrieving all narratives for a specific proposal for review, updating a particular narrative section, or checking the completeness of a proposal package before submission. For reporting, analysts often query this table to track narrative submissions or analyze proposal content. A fundamental query pattern involves joining to the parent proposals table:
- SELECT p.proposal_number, n.module_id, n.narrative_text FROM igw_prop_narratives n, igw_proposals_all p WHERE n.proposal_id = p.proposal_id AND p.proposal_id = :1;
Another common pattern is to verify the existence of required narratives for a set of proposals, which is crucial for compliance checks during internal proposal routing and before agency submission.
Related Objects
The table maintains a direct, documented relationship with the central proposals table, as defined by its foreign key. The key related objects are:
- IGW_PROPOSALS_ALL: This is the primary parent table. The relationship is defined by the foreign key from IGW_PROP_NARRATIVES.PROPOSAL_ID to IGW_PROPOSALS_ALL. This join is essential for connecting narrative text to the broader proposal header information, such as the proposal number, title, and principal investigator.
- IGW_NARRATIVE_PK: The primary key constraint on the table itself, ensuring data integrity for the combination of PROPOSAL_ID and MODULE_ID.
While not listed in the provided metadata, this table is also likely referenced by various Grants Proposal application forms, concurrent programs, and public APIs (e.g., IGW_PROPOSAL_PUB) that manage the lifecycle of proposal narratives.
-
Table: IGW_PROP_NARRATIVES
12.2.2
product: IGW - Grants Proposal (Obsolete) , description: Information about proposal narratives , implementation_dba_data: Not implemented in this database ,
-
View: IGWBV_GRANT_PROPOSAL_NARRATIVE
12.2.2
product: IGW - Grants Proposal (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
View: IGWFV_GRANT_PROPOSAL_NARRATIVE
12.2.2
product: IGW - Grants Proposal (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
Table: IGW_PROPOSALS_ALL
12.2.2
product: IGW - Grants Proposal (Obsolete) , description: Core information about proposals , implementation_dba_data: Not implemented in this database ,