Search Results key_person_flag




Overview
Explore in AI Chat

Overview

IGW_PRPO_PROP_PERSONS_V is a reporting view within the Oracle E-Business Suite IGW — Grants Proposal module. The IGW product line is documented in ETRM as Obsolete, meaning it is retained for backward compatibility and historical reporting but is not enhanced in EBS 12.1.1 or 12.2.2. The view consolidates biographical, demographic, and contact information for persons associated with a grant proposal, presenting a single denormalized row per proposal/person combination. Its primary purpose is to feed proposal-related reports and integrations that require a flattened view of investigator and key-person data, including government identifiers, addresses, phone numbers, and role designations.

The view is significant for users searching on person_govt_id, because the column PERSON_GOVT_ID is derived through a call to IGW_EXTENSION_PKG.PERSON_GOVT_ID rather than from a stored column on a base table. This means the government identifier (for example, a Social Security Number or national identifier) is resolved at query time by custom extension logic layered over seeded EBS person data.

Underlying Base Objects

The ETRM metadata documents no formal base-object registrations for this view; it is marked in the metadata excerpt as Not implemented in this database, which typically indicates that the view definition exists in the source system but the deployment flag or registration was not captured. The view text, however, identifies the driving tables unambiguously:

  • IGW_PROP_PERSONS (aliased PPP) — the proposal/person association, holding PROPOSAL_ID, PERSON_ID, role codes, key-person and principal-investigator flags, sequence, and percent effort.
  • PER_PEOPLE_X (PPX, and HP in the UNION branch) — the HR/person biographical source supplying name components, title, sex, date of birth, email, and NATIONAL_IDENTIFIER.
  • PER_ADDRESSES (AD) — outer-joined on PERSON_ID with PRIMARY_FLAG = 'Y' and DATE_TO IS NULL, supplying address lines, city, region, postal code, and country.
  • FND_LOOKUP_VALUES (LKUP1, LKUP2) — outer-joined lookup tables resolving NATIONALITY and US_ETHNIC_GROUP meanings, filtered by language, enabled flag, and effective dates.

Person-level derivations are provided by IGW_REPORT_PROCESSING.GET_PROPOSAL_ROLE, IGW_REPORT_PROCESSING.GET_JOB_NAME, and IGW_REPORT_PROCESSING.GET_PHONE_NUMBER, while IGW_EXTENSION_PKG.PERSON_GOVT_ID supplies the government identifier.

Key Columns

Common Use Cases and Queries

Typical use cases include proposal personnel rosters, effort-percentage reports, and compliance extracts requiring government identifiers.

  • Retrieve proposal personnel with government IDs: SELECT proposal_id, person_id, full_name, person_govt_id, ssn FROM igw_prpo_prop_persons_v WHERE proposal_id = :p_proposal;
  • Search by government identifier: SELECT proposal_id, full_name, person_govt_id FROM igw_prpo_prop_persons_v WHERE person_govt_id = :p_govt_id;
  • List key persons and their effort: SELECT full_name, percent_effort FROM igw_prpo_prop_persons_v WHERE proposal_id = :p_proposal AND key_person_flag = 'Y';
  • Extract contact details: SELECT full_name, email_address, town_or_city, country FROM igw_prpo_prop_persons_v WHERE proposal_id = :p_proposal;

Because PERSON_GOVT_ID is computed dynamically, queries filtering on it cannot use a standard index and may perform slowly on large proposal populations.