Results for “abstract_category”

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

Overview

IGWBV_GRANT_PRPSL_SUPPRT_TEXT is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Grants Proposal (IGW) module. It presents proposal abstract and supporting descriptive text data, joining proposals to their associated abstracts and decoding the abstract type into a user-readable meaning. The view consolidates information stored across the Grants Proposal schema into a single, denormalized result set, which is the typical pattern for IGW "BV" (business view) objects. Such views exist primarily to support Oracle Forms-based inquiry, OAF pages, reporting, and downstream integration extracts rather than to store data themselves. It exposes the proposal number and identifier alongside the abstract text, the abstract type code, the decoded lookup meaning, and standard Who-column audit attributes. The "_DF" column returned by the view carries a descriptive flexfield reference token ('_DF:IGW:IGW_PROP_ABSTRACTS_DESC_FLEX:AB'), signaling that the underlying abstract record participates in the IGW_PROP_ABSTRACTS_DESC_FLEX descriptive flexfield. The view is declared WITH READ ONLY, so no DML may be issued against it. Its status is VALID against the ETRM 12.1.1 / 12.2.2 metadata.

Underlying Base Objects

The view is defined over three base objects via an inner-join query:

• IGW_PROPOSALS_ALL — aliased PR; supplies PROPOSAL_NUMBER and PROPOSAL_ID.
• IGW_PROP_ABSTRACTS — aliased AB; supplies the abstract content, abstract type code, abstract type, and audit columns, and is joined on PROPOSAL_ID = PR.PROPOSAL_ID.
• IGW_LOOKUPS_V — aliased LKUP1; supplies the decoded MEANING, joined where LOOKUP_TYPE = AB.ABSTRACT_TYPE and LOOKUP_CODE = AB.ABSTRACT_TYPE_CODE.

The documented ETRM metadata lists no separately registered referenced base objects, but the view text confirms the three tables above. Because the join key between abstracts and proposals is the surrogate PROPOSAL_ID, and the lookup join is on the abstract type, the result is one row per qualifying abstract record whose type matches a valid lookup entry. Rows in IGW_PROP_ABSTRACTS lacking a matching lookup row are excluded by the inner join.

Key Columns

• PROPOSAL_NUMBER / PROPOSAL_ID — the human-readable proposal identifier and its numeric primary key.
• ABSTRACT_TYPE_CODE — the code classifying the abstract record.
• MEANING — the decoded lookup meaning for the abstract type, providing the user-facing label.
• ABSTRACT — the free-text abstract or supporting text itself.
• ABSTRACT_TYPE — the lookup type used to resolve MEANING.
• ABSTRACT_CATEGORY / ABSTRACT_CODE — column aliases exposed by the view for the abstract classification fields.
• _DF — descriptive flexfield context token pointing at IGW_PROP_ABSTRACTS_DESC_FLEX.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns inherited from the abstract record.

Common Use Cases and Queries

Typical uses include retrieving all supporting text for a proposal, producing abstracts with decoded type labels for reports, and feeding grant proposal content into external systems. A representative query:

• SELECT proposal_number, meaning, abstract FROM igwbv_grant_prpsl_supprt_text WHERE proposal_number = :p_number ORDER BY abstract_type_code;
• SELECT proposal_id, abstract_type_code, COUNT(*) FROM igwbv_grant_prpsl_supprt_text GROUP BY proposal_id, abstract_type_code;
• SELECT proposal_number, abstract FROM igwbv_grant_prpsl_supprt_text WHERE UPPER(abstract) LIKE '%GOAL%';

Because the view is read-only and predicated on inner joins, it is best suited to read/report workloads; inserts or updates must target the base IGW tables directly.