Results for “role_code”

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

Overview

IGW_PROP_PERSON_SUPPORT is a table within the Oracle E-Business Suite Grants Proposal (IGW) module, which is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2. The table stores information about other sources of support that are either available or pending for personnel listed on a research proposal. In practice, this supports the "Other Support" section of a grant application, where investigators must disclose current and pending funding that may overlap with the proposal under preparation.

The ETRM documentation records 57 columns owned by the IGW schema and identifies IGW_PROP_PERSON_SUPPORT_PK, defined on PROP_PERSON_SUPPORT_ID, as the primary key. A unique index, IGW_PROP_PERSON_SUPPORT_U1, is also documented on PROP_PERSON_SUPPORT_ID. Notably, the metadata states "Not implemented in this database," indicating the object may be absent in certain installations or superseded by successor data models.

From a Data Vault modeling perspective, the FK structure is classified heuristically as satellite-leaning. The table's principal foreign keys — PROPOSAL_ID and PERSON_ID referencing IGW_PROP_PERSONS, and PROPOSAL_AWARD_ID referencing IGW_AWARDS — suggest a structure that records descriptive attributes in the context of a parent proposal-person relationship, consistent with satellite semantics.

Key Information Stored

The table's most significant columns fall into identification, funding, and timing categories:

• PROP_PERSON_SUPPORT_ID — surrogate primary key and the column underlying both the PK and unique index IGW_PROP_PERSON_SUPPORT_U1.
• PROPOSAL_ID, PERSON_ID — foreign keys linking each support record to a proposal and to the person on that proposal.
• PROPOSAL_AWARD_ID, PROPOSAL_AWARD_NUMBER, PROPOSAL_AWARD_TITLE — identifiers and descriptive details of the award associated with the disclosed support.
• SUPPORT_TYPE — classification of the support (e.g., current versus pending).
• SPONSOR_ID, SPONSOR_NAME, SPONSOR_APPLICATION_NUMBER — the funding sponsor and related application reference.
• PI_PERSON_ID, PI_PARTY_ID, PI_NAME — principal investigator identification.
• START_DATE, END_DATE and the calendar, academic, and summer date pairs — the periods during which support applies.
• PERCENT_EFFORT — the level of effort committed to the disclosed support.
• ANNUAL_DIRECT_COST, TOTAL_COST — financial magnitude of the other support.
• OVERLAP — an indicator of potential overlap with the current proposal.
• PARTY_ID, LOCATION_PARTY_ID, PROJECT_LOCATION — TCA party and location references.
• RECORD_VERSION_NUMBER, AUTOMATIC_FLAG, ROLE_CODE — concurrency, generation, and role metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard flexible attribute columns.

Common Use Cases and Queries

Typical usage centers on reporting other-support disclosures for a proposal or person and on identifying potential overlap between pending and active awards. A representative query joins the table to IGW_PROP_PERSONS by PROPOSAL_ID and PERSON_ID:

• Listing all support records for a proposal: SELECT p.PERSON_ID, s.SUPPORT_TYPE, s.SPONSOR_NAME, s.START_DATE, s.END_DATE, s.PERCENT_EFFORT FROM IGW_PROP_PERSON_SUPPORT s JOIN IGW_PROP_PERSONS p ON s.PERSON_ID = p.PERSON_ID WHERE s.PROPOSAL_ID = :proposal_id;
• Detecting overlap: filtering on OVERLAP = 'Y' and comparing the START_DATE/END_DATE range against the proposal period.
• Aggregating committed effort: SELECT PERSON_ID, SUM(PERCENT_EFFORT) FROM IGW_PROP_PERSON_SUPPORT GROUP BY PERSON_ID;
• Award-related reporting by joining PROPOSAL_AWARD_ID to IGW_AWARDS to reconcile disclosed support with recorded awards.
• Cost summaries using ANNUAL_DIRECT_COST and TOTAL_COST per sponsor or investigator.

Because the object is documented as obsolete and "Not implemented in this database," production queries should first confirm the table's existence in the target instance.

Related Objects

The FK metadata identifies the primary related objects directly:

• IGW_PROP_PERSONS — parent table referenced by PROPOSAL_ID and PERSON_ID.
• IGW_AWARDS — referenced by PROPOSAL_AWARD_ID for award linkage.

In practice, additional integration points include IGW_PROPOSALS for proposal-level context, IGW_PROP_PERSON_*. tables for other personnel-related attributes, and TCA party tables (HZ_PARTIES) implied by PARTY_ID, PI_PARTY_ID, and LOCATION_PARTY_ID. Investigators working with successor or replacement IGW structures should verify which object now carries other-support data in their EBS version.