Results for “abstract_type_code”

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

Overview

IGW_PROP_NARRATIVES is a table within the Oracle E-Business Suite Grants Proposal module (IGW), a product line documented as obsolete in current EBS releases. In Oracle EBS 12.1.1 and 12.2.2, this object historically supported the capture and storage of narrative content associated with grant proposals, including proposal module structure, contact details, and free-text abstract and comment information. Its role in the IGW data model is that of an attribute-bearing child entity, storing descriptive information that enriches the parent proposal record held in IGW_PROPOSALS_ALL.

Based on a heuristic Data Vault classification mined from the foreign key structure, this table exhibits a satellite-leaning profile. As a modeling suggestion, this implies that IGW_PROP_NARRATIVES behaves primarily as a descriptive satellite, holding time-variant, non-key attributes attached to a parent hub or link. The composite primary key IGW_NARRATIVE_PK (PROPOSAL_ID, MODULE_ID) acts as the unique identifier for each narrative record, while foreign key traversal back to the parent proposal is achieved through PROPOSAL_ID.

Key Information Stored

Among the eighteen documented columns, the most significant can be grouped by function. The primary key and relationship columns form the structural spine of the table:

• PROPOSAL_ID — part of the composite primary key and a foreign key to IGW_PROPOSALS_ALL; identifies the parent grant proposal.
• MODULE_ID — part of the composite primary key; segments the proposal narrative into distinct modules.

Descriptive and business-content columns carry the substantive narrative data:

• MODULE_TITLE — the human-readable title of the narrative module.
• MODULE_STATUS — the current status of the module within the proposal workflow.
• CONTACT_NAME, PHONE_NUMBER, and EMAIL_ADDRESS — contact details associated with the narrative module.
• COMMENTS and COMMENTS_CLOB — free-text commentary, with the CLOB variant accommodating lengthy narrative content.
• ABSTRACT_TYPE and ABSTRACT_TYPE_CODE — classification of the abstract content, with code providing the lookup value.
• CONTACT_ID — a reference to the contact entity associated with the module.

Standard audit columns complete the table: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and RECORD_VERSION_NUMBER. The unique index IGW_NARRATIVE_U1 (PROPOSAL_ID, MODULE_ID) reinforces the business-key candidate, ensuring one narrative module per proposal per module identifier. A system-generated index, SYS_IL0000099447C00018$$, supports the LOB column.

Common Use Cases and Queries

Reporting on proposal narratives typically joins back to the parent proposal table. A representative query retrieves narrative modules for a given proposal:

• SELECT n.MODULE_ID, n.MODULE_TITLE, n.MODULE_STATUS, n.CONTACT_NAME FROM IGW_PROP_NARRATIVES n WHERE n.PROPOSAL_ID = :proposal_id;
• Aggregation across proposals for a summary of module counts and statuses: SELECT PROPOSAL_ID, COUNT(*) FROM IGW_PROP_NARRATIVES GROUP BY PROPOSAL_ID;
• Extraction of abstract and comment content using the CLOB column: SELECT PROPOSAL_ID, MODULE_ID, COMMENTS_CLOB FROM IGW_PROP_NARRATIVES WHERE ABSTRACT_TYPE_CODE = :type;

Because the product is obsolete, these patterns are most relevant to legacy data migration, archival reporting, and historical research efforts rather than active transactional processing.

Related Objects

The most significant related objects are bound by the documented foreign key and key relationships:

• IGW_PROPOSALS_ALL — the parent table referenced via IGW_PROP_NARRATIVES.PROPOSAL_ID; the primary join target for any narrative query.
• IGW_NARRATIVE_PK — the primary key constraint comprising PROPOSAL_ID and MODULE_ID.
• IGW_NARRATIVE_U1 — the unique index enforcing the business-key candidate on PROPOSAL_ID and MODULE_ID.
• SYS_IL0000099447C00018$$ — the system index supporting the LOB segment associated with COMMENTS_CLOB.

Because the documented metadata lists no additional foreign or referencing objects, downstream dependencies should be validated directly against the database dictionary in any deployment where the IGW schema remains available. In most EBS 12.1.1 and 12.2.2 environments, the table is marked as not implemented in the database, so its relevance is principally historical and documentary.