Search Results igw_prop_persons




Overview
Explore in AI Chat

Overview

The table IGW_PROP_PERSONS is a core data object within the Oracle E-Business Suite (EBS) Grants Proposal module (IGW), specifically for versions 12.1.1 and 12.2.2. Its primary function is to store a detailed record of all personnel associated with a specific grant proposal, such as principal investigators, co-investigators, and other key project staff. This table is essential for linking individuals, identified by their party ID from the Trading Community Architecture (TCA), to a proposal defined in the IGW_PROPOSALS_ALL table. It is critical to note that the IGW module is marked as "Obsolete" in the provided ETRM documentation, indicating it is a legacy component that may not be actively developed or recommended for new implementations. Furthermore, the metadata explicitly states "Not implemented in this database" for the Implementation/DBA Data section, which suggests that while the table structure is defined, it may not be populated or actively used in a standard deployment, or it may be subject to specific implementation conditions.

Key Information Stored

The table's structure centers on the unique identification of a person within a specific proposal. The primary key is a composite of PROPOSAL_ID and PERSON_PARTY_ID, enforcing that each person is uniquely recorded per proposal. Key columns include PROPOSAL_ID, which links to the IGW_PROPOSALS_ALL table to identify the parent grant proposal, and PERSON_PARTY_ID, which stores the unique identifier for the individual from the TCA registry. Another significant column is PERSON_ORGANIZATION_ID, a foreign key to HR_ALL_ORGANIZATION_UNITS, which stores the organization or department with which the person is affiliated at the time of the proposal. This allows for reporting and validation based on organizational hierarchy. Additional columns, while not listed in the excerpt, would typically capture details like the person's role on the proposal (e.g., Principal Investigator), commitment percentage, and associated costs or support details.

Common Use Cases and Queries

The primary use case for IGW_PROP_PERSONS is to generate personnel reports for a grant proposal, which are often required by funding agencies. This includes listing all team members, their roles, and their affiliated departments. A common query would join this table with TCA party tables to retrieve person names and with HR tables to get organization details. For example, to list all personnel for a specific proposal, one might use: SELECT pp.person_party_id, pp.person_organization_id, hou.name org_name FROM igw_prop_persons pp, hr_organization_units hou WHERE pp.proposal_id = :p_prop_id AND pp.person_organization_id = hou.organization_id; Another critical use case is budget validation and integration, as this table is a parent to IGW_BUDGET_PERSONS, ensuring personnel costs in the budget are tied to approved proposal personnel. Data from this table is also fundamental for creating internal compliance and effort reporting.

Related Objects

IGW_PROP_PERSONS sits at the center of a network of related objects within the Grants Proposal schema. It is a child table of IGW_PROPOSALS_ALL, inheriting the proposal context via the PROPOSAL_ID foreign key. It is also a parent table to two key entities: IGW_BUDGET_PERSONS, which holds detailed budget figures for each person, and IGW_PROP_PERSON_SUPPORT, which likely stores justification or supplementary information for the personnel inclusion. The PERSON_ORGANIZATION_ID foreign key establishes a critical link to HR_ALL_ORGANIZATION_UNITS, integrating proposal data with the enterprise's HR organizational structure. This web of relationships ensures data integrity across the proposal, budgeting, and organizational dimensions of the grants management process.