Search Results igw_prpo_org_types_v




Overview
Explore in AI Chat

Overview

IGW_PRPO_ORG_TYPES_V is a reporting view shipped within the IGW – Grants Proposal module of Oracle E-Business Suite. Its documented purpose is to display the type of organization associated with a grant proposal. The view joins proposal records to the organization types assigned to the submitting organization, resolving the stored organization type code against the IGW lookup set to produce a human-readable organization type name.

The IGW product line is flagged as obsolete in the ETRM metadata. In the 12.1.1 and 12.2.2 release documentation the view is listed with the note "Not implemented in this database," meaning no seeded or deployed instance of the object exists in the reference environment. This is consistent with the retirement of the Grants Proposal (IGW) application, whose functional footprint was superseded by later-generation grants and proposals solutions. Consequently, the view should be treated as a legacy reporting artifact rather than an active integration point. Its relevance today is primarily for upgrade analysis, historical data extraction, and understanding the structure of migrated IGW data.

Underlying Base Objects

The view is defined over three sources, as shown in its view text:

The join logic connects IGW_PROPOSALS.SUBMITTING_ORGANIZATION_ID to IGW_ORG_TYPES.ORGANIZATION_ID, and then matches IGW_ORG_TYPES.ORGANIZATION_TYPE_CODE to IGW_LOOKUPS_V.LOOKUP_CODE filtered by LOOKUP_TYPE = 'IGW_ORGANIZATION_TYPES'. The metadata documents no owner and no separately registered base objects, so dependencies are established purely through this defining query. Because IGW_LOOKUPS_V is itself a lookup view, the effective lineage extends into the FND lookup infrastructure.

Key Columns

  • PROPOSAL_ID — Identifier of the grant proposal from IGW_PROPOSALS. This is the principal correlation key for reporting at proposal grain.
  • ORGANIZATION_ID — Identifier of the organization (typically the submitting organization) to which the organization type applies.
  • ORG_TYPE_CODE (listed in the column header set) — The stored organization type code sourced from IGW_ORG_TYPES.ORGANIZATION_TYPE_CODE, matching the code returned by LOOKUP_CODE.
  • ORG_TYPE (listed in the column header set) — The descriptive organization type value, corresponding to LKUP.MEANING in the view text.

The view text additionally selects LOOKUP_CODE and MEANING explicitly, which map to the ORG_TYPE_CODE and ORG_TYPE columns reported in the documentation. The column metadata names do not perfectly mirror the SELECT aliases, a common inconsistency in legacy IGW views, so consumers should verify actual column names against the deployed object rather than relying solely on the documented header.

Common Use Cases and Queries

Typical uses include listing the organization types tied to each proposal, filtering proposals by submitting organization type, and reconciling migrated IGW data during upgrades. A representative query follows:

SELECT proposal_id, organization_id, org_type_code, org_type FROM igw_prpo_org_types_v WHERE proposal_id = :p_proposal_id;

To aggregate proposal counts by organization type:

SELECT org_type, COUNT(DISTINCT proposal_id) FROM igw_prpo_org_types_v GROUP BY org_type ORDER BY 2 DESC;

Because the object is obsolete and reports as not implemented, these statements should be validated against the target instance before reliance. Where the view is absent, equivalent logic can be reproduced directly from IGW_PROPOSALS, IGW_ORG_TYPES, and the IGW_ORGANIZATION_TYPES lookup.