Search Results prop_person_support_id

Overview

The IGW_PROP_PERSON_SUPPORT table is a core data object within the Oracle E-Business Suite Grants Proposal (IGW) module. It functions as a detailed repository for tracking all other sources of financial support—either already secured or pending—for personnel listed on a research proposal. This information is critical for proposal integrity and compliance, ensuring that funding agencies have a complete picture of a researcher's total support, which can affect budget justifications, effort commitments, and conflict-of-interest assessments. The table's existence underscores the module's capability to manage complex proposal requirements by maintaining a granular audit trail of personnel funding outside the immediate proposal.

Key Information Stored

The table's primary purpose is to record details about alternative support for proposal personnel. While the full column list is not detailed in the provided metadata, its structure is defined by its primary and foreign keys. The central identifier is the PROP_PERSON_SUPPORT_ID, which serves as the table's unique primary key. Each record is fundamentally linked to a specific person on a specific proposal through the foreign key columns PROPOSAL_ID and PERSON_ID. Typical data stored would include the source organization providing the other support, the amount of funding, the time period of the support, the status (e.g., 'Available', 'Pending'), and the type of support. This allows the system to answer key questions about a researcher's total funded effort.

Common Use Cases and Queries

This table is primarily accessed during proposal development, submission, and audit processes. A common operational use case is generating a report for a Principal Investigator showing all other support for every team member to be included in a proposal's biographical sketch or current and pending support document. Administrators may query it to ensure no cost-sharing commitments are duplicated across multiple grants. A typical reporting query would join this table to the personnel master to list support details:

• SELECT pps.*, ip.full_name FROM igw_prop_person_support pps JOIN igw_prop_persons ip ON pps.proposal_id = ip.proposal_id AND pps.person_id = ip.person_id WHERE pps.proposal_id = :p_prop_id;

Another critical use is validation, where the total effort from this table and the primary proposal must be checked to ensure it does not exceed 100% for any individual.

Related Objects

The IGW_PROP_PERSON_SUPPORT table has a direct and essential relationship with the core personnel assignment table, as documented by its foreign key constraints. It is a child table to IGW_PROP_PERSONS. This relationship enforces referential integrity, meaning a support record cannot exist without a corresponding personnel record on a proposal. The join is performed using the composite key of PROPOSAL_ID and PERSON_ID. This design ensures that all support information is correctly scoped to a specific individual within a specific proposal context. Other related objects would likely include the main proposal header table (IGW_PROPOSALS_ALL) and various IGW workflow and approval entities that reference personnel data.