Results for “abstract_type”

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

Overview

The IGWFV_GRANT_PRPSL_SUPPRT_TEXT view is a read-only reporting object owned by the APPS schema within the IGW - Grants Proposal product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary function is to present the free-form text supporting documentation associated with grant proposals, specifically proposal abstracts, in a denormalized and user-readable form. Rather than requiring report developers and integration specialists to join the base proposals table, the abstracts table, and the lookup table manually, the view encapsulates that logic and exposes a single flattened record set.

The object is marked VALID in the ETRM data dictionary, indicating that the database has successfully compiled the view definition and that its dependencies on the referenced tables are satisfied. The presence of the WITH READ ONLY clause confirms that the view is intended exclusively for query, reporting, and integration consumption. Direct DML against this view is not supported.

Underlying Base Objects

The view is defined over three referenced objects from the IGW schema:

• IGW_PROPOSALS_ALL — the primary proposals entity, aliased as PR, supplying proposal identifiers and numbers.
• IGW_PROP_ABSTRACTS — the abstracts table, aliased as AB, which stores the abstract text and its descriptive flexfield context.
• IGW_LOOKUPS_V — the lookups view, aliased as LKUP1, which translates the stored code values into meaningful display text.

The join conditions establish that an abstract is attached to a proposal via AB.PROPOSAL_ID = PR.PROPOSAL_ID, and that the lookup is resolved through a dual-key condition where LKUP1.LOOKUP_TYPE = AB.ABSTRACT_TYPE and AB.ABSTRACT_TYPE_CODE = LKUP1.LOOKUP_CODE. This dual-key join ensures that the meaning returned corresponds to the correct lookup classification for the abstract.

Key Columns

• PROPOSAL_NUMBER / PROPOSAL_ID — the human-readable proposal number and the internal surrogate key from the proposals table.
• ABSTRACT_TYPE_CODE — the stored lookup code identifying the type or category of the abstract record.
• MEANING — the decoded display value returned by the lookup view, corresponding to the abstract type code.
• ABSTRACT_TYPE — the lookup type under which the abstract category is classified.
• ABSTRACT — the full abstract text content associated with the proposal.
• ABSTRACT_CATEGORY — exposed as a documented column and referenced directly by the term "abstract_category." In practice this column surfaces the categorization of the abstract, aligning with the abstract type classification resolved through the lookup join.
• "_DF" — a literal marker ('_DF:IGW:IGW_PROP_ABSTRACTS_DESC_FLEX:AB') that identifies the descriptive flexfield context for the abstracts entity, enabling Flexfield-aware reporting tools to locate the appropriate descriptive flexfield definition.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY provide the standard WHO column set for change tracking.

Common Use Cases and Queries

The most frequent use of this view is retrieving abstract text for a given proposal or filtering proposals by abstract category. A typical query selecting abstract content for a specific proposal is:

• SELECT proposal_number, abstract_category, meaning, abstract FROM igwfv_grant_prpsl_supprt_text WHERE proposal_number = :p_proposal_number;

Reports that require all proposals carrying a particular abstract category can filter on the category or meaning column:

• SELECT proposal_number, meaning, abstract FROM igwfv_grant_prpsl_supprt_text WHERE abstract_category = :p_category ORDER BY proposal_number;

Because the underlying query is read-only and performs the lookup translation at the database layer, the view is well suited to OBIEE, BI Publisher, and custom concurrent program reporting where consistent interpretation of abstract category codes is essential.