Results for “igw_prop_abstracts”

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

Overview

IGW_PROP_ABSTRACTS is a transactional table within the IGW (Grants Proposal) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2 releases. It stores paragraph-level and resource-level narrative content associated with grant proposals, including abstracts, titles, and descriptive text used throughout the proposal lifecycle. The table functions as a child of IGW_PROPOSALS_ALL, the central proposal header entity, and captures the multi-row textual detail that cannot be accommodated on the proposal record itself.

Because a single proposal may carry multiple abstracts distinguished by type (for example, technical, executive, or lay summaries), the table exhibits a one-to-many relationship with its parent. From a Data Vault modeling perspective, this object is best characterized as satellite-leaning: it holds descriptive, time-stamped attributes dependent on the proposal hub, with the proposal identifier as the connecting key. It is not a hub, since it does not independently define the proposal; nor is it a pure link, since it stores substantive descriptive payload rather than merely resolving many-to-many associations.

Key Information Stored

The primary key is defined by the constraint IGW_PROP_ABSTRACTS_PK, composed of PROPOSAL_ID and ABSTRACT_TYPE_CODE. A separate unique index, IGW_PROP_ABSTRACTS_U1, covers the same two columns, confirming that the combination of proposal and abstract type is the business-key candidate. PROPOSAL_ID is the foreign key to IGW_PROPOSALS_ALL and identifies the owning proposal.

The most significant columns include:

• PROPOSAL_ID – foreign key to the parent proposal record; part of the composite primary key.
• ABSTRACT_TYPE_CODE – lookup code classifying the abstract; part of the composite primary key.
• ABSTRACT_TYPE – descriptive form of the abstract type.
• ABSTRACT – the abstract text body (short or legacy format).
• ABSTRACT_CLOB – large-object column holding extended abstract content beyond the short field limit.
• PARAGRAPH_TITLE – heading applied to the paragraph or abstract section.
• RECORD_VERSION_NUMBER – optimistic locking or versioning indicator for concurrent update control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard EBS WHO columns for audit and change tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 – the standard DFF/descriptive flexfield container, enabling client-specific extensions.

Common Use Cases and Queries

Typical usage centers on proposal reporting, abstract retrieval for review workflows, and integration extracts that feed downstream grants systems. A representative query joins the abstract table to its parent to list all abstracts for a given proposal:

• SELECT a.PROPOSAL_ID, a.ABSTRACT_TYPE_CODE, a.PARAGRAPH_TITLE, a.ABSTRACT FROM IGW.IGW_PROP_ABSTRACTS a WHERE a.PROPOSAL_ID = :proposal_id ORDER BY a.ABSTRACT_TYPE_CODE;
• Join to parent for context: SELECT p.PROPOSAL_NUMBER, a.ABSTRACT_TYPE_CODE, a.ABSTRACT FROM IGW.IGW_PROP_ABSTRACTS a, IGW.IGW_PROPOSALS_ALL p WHERE a.PROPOSAL_ID = p.PROPOSAL_ID;
• Identify proposals carrying a specific abstract type: SELECT PROPOSAL_ID FROM IGW.IGW_PROP_ABSTRACTS WHERE ABSTRACT_TYPE_CODE = :type_code;
• Retrieve large abstract content: SELECT ABSTRACT_CLOB FROM IGW.IGW_PROP_ABSTRACTS WHERE PROPOSAL_ID = :proposal_id AND ABSTRACT_TYPE_CODE = :type_code;

Related Objects

The following objects are most significant in relation to IGW_PROP_ABSTRACTS:

• IGW_PROPOSALS_ALL – parent table; joined via IGW_PROP_ABSTRACTS.PROPOSAL_ID = IGW_PROPOSALS_ALL.PROPOSAL_ID, and the referenced table for the documented foreign key.
• IGW_PROP_ABSTRACTS_PK – primary key constraint on (PROPOSAL_ID, ABSTRACT_TYPE_CODE).
• IGW_PROP_ABSTRACTS_U1 – unique index enforcing the same business-key candidate columns.
• IGW abstract type lookup – supplies valid ABSTRACT_TYPE_CODE values.
• IGW proposal query/view objects – read from the table to render Abstract and Paragraph regions in the Grants Proposal forms and self-service pages.
• Concurrent programs and APIs in the Grants module – consume abstract rows when copying or versioning proposals.