Search Results person_full_name




Overview
Explore in AI Chat

Overview

APPS.IGWFV_GRNT_PRPSL_PERS_BIOSKTCH is a Business Intelligence System (BIS) view owned by the APPS schema within the Oracle E-Business Suite Grants Management (IGW) product family. The "FV" prefix identifies it as a formatted, presentation-oriented view designed for reporting and inquiry rather than for transactional data entry. Its purpose is to expose grant proposal personnel biographical sketch data — narrative descriptions of investigators, key personnel, and consultants associated with a grant proposal — in a structure suited to reporting tools, listings, and integration extracts.

The view is registered under FND Design Data as IGW.IGWFV_GRNT_PRPSL_PERS_BIOSKTCH and carries a status of VALID. It is not referenced by any other database object, confirming its role as a terminal, read-only reporting artifact. Because the object name includes PERSON_FULL_NAME — the column surfaced as the first attribute in the documented query text — it is frequently located by implementers searching for a person-level descriptive name within grants reporting rather than within the standard HR person directory.

Underlying Base Objects

The view is defined over four documented dependency objects: IGW_PERSON_BIOSKETCH, PER_ALL_PEOPLE_F, IGW_LOOKUPS_V, and FND_GLOBAL. IGW_PERSON_BIOSKETCH is the primary transactional base and supplies the biographical sketch record itself, including the biosketch identifier, type, sequence, and line text. PER_ALL_PEOPLE_F supplies person identity and the derived person full name, which accounts for the PERSON_FULL_NAME column at its documented VARCHAR2(240) length. IGW_LOOKUPS_V resolves coded lookup values into their display meanings, and FND_GLOBAL is referenced for runtime context such as the current user, responsibility, and application. The metadata explicitly notes that the view references these objects but is referenced by none, reinforcing that it is a leaf-level reporting construct.

Key Columns

  • PERSON_FULL_NAME (VARCHAR2(240)) — the formatted full name of the person to whom the biographical sketch belongs; the attribute most commonly searched for.
  • BIOSKETCH_TYPE (VARCHAR2(80)) — the category of biographical sketch, typically resolved through lookup values.
  • BIOSKETCH_LINE_SEQUENCE (NUMBER) — the ordering sequence used to reconstruct the narrative from its individual lines.
  • BIOSKETCH_LINE (VARCHAR2(500)) — each stored line of the biographical narrative; a single biosketch spans multiple rows that must be assembled in sequence.
  • ENABLE_FLAG (VARCHAR2) — indicates whether the biosketch or line is active for display.
  • PERSON_BIOSKETCH_ID (NUMBER(10)) and PERSON_ID (NUMBER(15)) — the unique identifiers for the biosketch record and the underlying person respectively.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — the standard EBS audit columns.

Common Use Cases and Queries

Typical uses include producing personnel biosketch listings for grant proposals, extracting narrative content for sponsor submissions, and joining biosketch data to person records for reporting. Because the narrative is line-based, queries usually order by sequence and aggregate accordingly.

SELECT PERSON_FULL_NAME,
       BIOSKETCH_TYPE,
       BIOSKETCH_LINE_SEQUENCE,
       BIOSKETCH_LINE
FROM   APPS.IGWFV_GRNT_PRPSL_PERS_BIOSKTCH
WHERE  PERSON_ID = :person_id
AND    ENABLE_FLAG = 'Y'
ORDER  BY BIOSKETCH_LINE_SEQUENCE;

For a consolidated narrative per person, the line column can be aggregated with LISTAGG or an equivalent string function. A simpler inquiry returns all rows directly:

SELECT PERSON_FULL_NAME
     , BIOSKETCH_TYPE
     , BIOSKETCH_LINE_SEQUENCE
     , BIOSKETCH_LINE
     , ENABLE_FLAG
     , PERSON_BIOSKETCH_ID
     , PERSON_ID
     , LAST_UPDATE_DATE
     , LAST_UPDATED_BY
     , CREATION_DATE
     , CREATED_BY
FROM   APPS.IGWFV_GRNT_PRPSL_PERS_BIOSKTCH;

Because the view is read-only and not referenced by other objects, it may be used freely in custom reports, discoverer workbooks, and BI Publisher data templates without affecting Grants Management transaction processing.