Search Results igwbv_grant_proposal_pers_asgn

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

Overview

IGWBV_GRANT_PROPOSAL_PERS_ASGN is a read-only database view belonging to the IGW — Grants Proposal module, which is classified as obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes personnel assignment information attached to grant proposals, joining proposal header records to their associated person assignments and decoding the assignment role through the IGW lookup table. Its purpose is to present a denormalized, report-friendly projection of the IGW_PROP_PERSONS entity, enriched with the parent proposal number and the human-readable meaning of the proposal role code.

Because the view is defined with a WITH READ ONLY clause, it is intended exclusively for query and reporting access, not for data maintenance. It plays a supporting role in Grants Proposal reporting and in integration extracts where proposal team composition, key person designation, principal investigator flags, and percent effort must be presented together with the proposal identifier and the descriptive role text. As the parent product module is obsolete, the view may not exist in all environments; the ETRM metadata explicitly notes "Not implemented in this database" for the documented instance, so availability should be confirmed against each target instance before it is referenced in custom code.

Underlying Base Objects

The view is defined over three referenced objects, as documented in the view text:

• IGW_PROP_PERSONS (aliased PER) — the primary driving table containing one row per person assignment on a proposal, including the role code, key person flag, principal investigator flag, percent effort, and the person_organization_id reference. This is the object that satisfies the user's search for "person_organization_id".
• IGW_PROPOSALS_ALL (aliased PR) — the proposal header entity, supplying PROPOSAL_ID and PROPOSAL_NUMBER. It is joined to IGW_PROP_PERSONS on PROPOSAL_ID.
• IGW_LOOKUPS_V (aliased LKUP1) — the Grants Proposal lookup view, used to translate PROPOSAL_ROLE_CODE into a display meaning. The join is constrained to LOOKUP_TYPE = 'IGW_PROPOSAL_ROLE_TYPES' and matched on LOOKUP_CODE = PER.PROPOSAL_ROLE_CODE.

No additional base objects are documented in the ETRM metadata beyond these three. The joins are inner joins, so a person assignment is only returned when its parent proposal exists and its role code resolves to a valid lookup value for the proposal role type.

Key Columns

• PROPOSAL_NUMBER — the user-facing proposal identifier from IGW_PROPOSALS_ALL.
• PROPOSAL_ID — the internal primary key linking assignment rows to the proposal header.
• PERSON_ID — the identifier of the assigned person.
• PERSON_ORGANIZATION_ID — the person-organization identifier for the assignment, the column directly relevant to the user's search term.
• PERSON_SEQUENCE — the ordering sequence of the person within the proposal's assignment list.
• PROPOSAL_ROLE — the decoded role meaning derived from IGW_LOOKUPS_V for lookup type IGW_PROPOSAL_ROLE_TYPES.
• KEY_PERSON_FLAG — indicates whether the individual is designated a key person on the proposal.
• PI_FLAG — indicates whether the individual is the principal investigator.
• EFFORT_PERCENT — the percent effort committed by the person, sourced from PER.PERCENT_EFFORT.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY provide standard EBS who-column auditing.

Common Use Cases and Queries

Typical usage centers on reporting proposal team composition and extracting personnel assignment data for downstream systems.

• Listing all persons on a proposal with their roles: SELECT proposal_number, person_id, proposal_role, key_person_flag, effort_percent FROM igwbv_grant_proposal_pers_asgn WHERE proposal_number = :p_number ORDER BY person_sequence;
• Retrieving the person_organization_id for assignments: SELECT proposal_id, person_id, person_organization_id FROM igwbv_grant_proposal_pers_asgn WHERE person_id = :p_person;
• Identifying principal investigators: SELECT proposal_number, person_id, effort_percent FROM igwbv_grant_proposal_pers_asgn WHERE pi_flag = 'Y';
• Extracting key personnel with decoded roles for integration: SELECT proposal_number, person_id, proposal_role, person_organization_id FROM igwbv_grant_proposal_pers_asgn WHERE key_person_flag = 'Y';

Because the underlying IGW Grants Proposal module is obsolete and the view is read-only, consumers should verify object existence in each instance and avoid DML against it. Any dependent custom reporting should be reassessed against the supported replacement functionality in current EBS releases.