Results for “igw_prop_persons_v”

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

Overview

IGW_PROP_PERSONS_V is a validity-verified view owned by the APPS schema within the Oracle E-Business Suite Grants Proposal (IGW) module. The view exposes the personnel associated with a grant or contract proposal, joining the base assignment table to people, lookup, and organization data so that consumers receive denormalized, report-ready rows. In ETRM documentation the object is characterized as "10SC Only," indicating it is exposed primarily to support the Oracle Grants Proposal tenancy and the associated self-service and reporting flows rather than being a general-purpose integration interface. Its practical role is to answer the recurring question of who is attached to a given proposal, in what capacity, at what effort level, and for which unit — without requiring the calling application to reassemble four separate tables. Because the view carries both surrogate keys (PROPOSAL_ID, PERSON_ID) and descriptive attributes (FULL_NAME, PROPOSAL_ROLE_DESC, PERSON_UNIT_NAME), it is well suited to both operational pages and ad hoc extracts, and it is a common dependency when building BI Publisher reports, Discoverer worksheets, or custom concurrent program outputs over IGW data.

Underlying Base Objects

The documented definition joins four objects. IGW_PROP_PERSONS is the driving table and supplies every key column except the descriptive attributes; each row represents one person-to-proposal assignment. PER_PEOPLE_X, a datetracked people view, supplies FULL_NAME and is joined on PERSON_ID. FND_LOOKUPS supplies the localized role description, restricted by LOOKUP_TYPE = 'IGW_PROPOSAL_ROLE_TYPES' and matched on LOOKUP_CODE = PROPOSAL_ROLE_CODE. HR_ORGANIZATION_UNITS is joined with an outer (+) operator on ORGANIZATION_ID = PERSON_ORGANIZATION_ID, meaning PERSON_UNIT_NAME is optional and may be null where no unit is recorded. The view exposes ROWIDTOCHAR(PP.ROWID) as ROW_ID to give consumers a unique row identifier. No base objects are separately documented in the ETRM metadata beyond this embedded SQL, so integrators should treat IGW_PROP_PERSONS as the authoritative record and the other three as enrichments.

Key Columns

• ROW_ID / RECORD_VERSION_NUMBER — surrogate identifier and optimistic locking token from the base table.
• PROPOSAL_ID / PERSON_ID — the assignment's proposal and person foreign keys; the natural composite key.
• FULL_NAME — person display name sourced from PER_PEOPLE_X.
• PERSON_SEQUENCE — ordering of persons within the proposal.
• PROPOSAL_ROLE_CODE / PROPOSAL_ROLE_DESC — role code and its translated meaning from FND_LOOKUPS.
• PI_FLAG / KEY_PERSON_FLAG — flags marking the principal investigator and key personnel.
• PERCENT_EFFORT — the effort percentage committed by the person.
• PERSON_ORGANIZATION_ID / PERSON_UNIT_NAME — home organization identifier and name (optional).
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include listing a proposal's personnel roster, identifying principal investigators, reporting effort distribution across units, and feeding interfaces that require recipient names.

SELECT person_id, full_name, proposal_role_desc, percent_effort
FROM apps.igw_prop_persons_v
WHERE proposal_id = :p_proposal_id
ORDER BY person_sequence;

SELECT full_name, person_unit_name, percent_effort
FROM apps.igw_prop_persons_v
WHERE pi_flag = 'Y';

Because the organization join is outer, queries expecting a unit name should tolerate nulls. Filtering on PROPOSAL_ROLE_DESC is safe; filtering on the code is preferable when language independence matters.