Search Results igw_proposals_all

Overview

The IGW_PROPOSALS_ALL table is the central transactional table within the Oracle E-Business Suite Grants Proposal (IGW) module for versions 12.1.1 and 12.2.2. It serves as the master repository for core information about every proposal created in the system. As a multi-organization table (indicated by the "_ALL" suffix), it stores data for all operating units, enabling a shared services deployment model. The table's primary key (PROPOSAL_ID) is the fundamental identifier for a proposal and is referenced by numerous child tables, establishing it as the anchor point for the entire proposal lifecycle, from creation through submission and eventual award conversion.

Key Information Stored

While the provided metadata does not list specific columns, based on its role as the core proposal table, IGW_PROPOSALS_ALL typically stores high-level attributes that define a proposal's identity, status, and context. Key columns logically include PROPOSAL_ID (primary key), PROPOSAL_NUMBER, TITLE, and STATUS_CODE. It also holds critical organizational foreign keys such as LEAD_ORGANIZATION_ID and SUBMITTING_ORGANIZATION_ID, which link to HR_ALL_ORGANIZATION_UNITS to define the performing and submitting entities. Other essential data points would include dates (creation, submission, start, end), associated PROGRAM_ID, funding amounts, and the AWARD_ID if the proposal has been successfully funded and converted into an award in the IGW_AWARDS table.

Common Use Cases and Queries

This table is fundamental for reporting and data extraction related to the proposal pipeline. Common use cases include generating portfolio summaries, tracking submission statuses, and analyzing lead organization performance. Technical consultants often query this table to integrate proposal data with external systems or to build custom reports. A typical query pattern involves joining to related tables to get a comprehensive proposal view:

• To list active proposals with their lead organization: SELECT p.proposal_number, p.title, hou.name lead_org FROM igw_proposals_all p, hr_all_organization_units hou WHERE p.lead_organization_id = hou.organization_id AND p.status_code = 'ACTIVE';
• To find proposals converted to awards: SELECT p.proposal_number, a.award_number FROM igw_proposals_all p, igw_awards a WHERE p.proposal_id = a.proposal_id;
• To audit proposals by creation date: SELECT TRUNC(creation_date), COUNT(*) FROM igw_proposals_all GROUP BY TRUNC(creation_date) ORDER BY 1 DESC;

Related Objects

As the central hub, IGW_PROPOSALS_ALL has extensive relationships. The documented foreign keys reveal a clear hierarchy. Key parent and child objects include:

• Parent Table: HR_ALL_ORGANIZATION_UNITS (for LEAD_ORGANIZATION_ID, SUBMITTING_ORGANIZATION_ID).
• Major Child Tables: The table is referenced by virtually all other proposal-related entities, including IGW_AWARDS, IGW_BUDGETS, IGW_PROP_PERSONS (investigators), IGW_PROP_ABSTRACTS, IGW_PROP_NARRATIVES, IGW_PROP_SPECIAL_REVIEWS, and IGW_PROP_QUESTIONS. This structure encapsulates all budgetary, personnel, and descriptive components of a proposal.
• Supporting Tables: IGW_PROP_APPROVAL_RUNS, IGW_PROP_CHECKLIST, IGW_PROP_COMMENTS, and IGW_PROP_USERS track workflow, compliance, and collaboration data tied to the master proposal record.