Search Results igw_organization_types

Overview

IGW_PRPO_ORG_TYPES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined in the context of the Grants Management (IGW) product family. The name reflects its intended purpose: it exposes the set of organization types associated with a proposal, combining proposal identification with the organization responsible for submission and the corresponding lookup code and meaning. In practice, the view serves as a denormalized, read-only projection that joins proposal, organization type, and lookup information into a single result set, allowing reporting tools, concurrent programs, and integration layers to resolve organization type attributes for a proposal without requiring them to reconstruct the underlying multi-table relationship manually.

The view is relevant to both Oracle EBS 12.1.1 and 12.2.2. It is commonly surfaced when searching under the term "igw_organization_types," since the underlying lookup type referenced by the view is IGW_ORGANIZATION_TYPES. Users searching that string are typically attempting to identify where organization type values originate, how they are attached to proposals, and which object to query to retrieve them.

Underlying Base Objects

The view is defined over three objects: IGW_ORG_TYPES, IGW_LOOKUPS_V, and IGW_PROPOSALS. The documented ETRM metadata lists no separately documented base tables, so the definition itself is the authoritative source.

• IGW_ORG_TYPES (alias ORGTYP) — holds the association between an organization and its organization type code, keyed by organization_id.
• IGW_LOOKUPS_V (alias LKUP) — supplies the lookup code and meaning, restricted to lookup_type = 'IGW_ORGANIZATION_TYPES'.
• IGW_PROPOSALS (alias PROP) — supplies the proposal_id and the submitting_organization_id used to link the proposal to its organization.

The join is driven by two equality conditions: LKUP.lookup_code = ORGTYP.organization_type_code and PROP.submitting_organization_id = ORGTYP.organization_id. This means a row is returned only where the proposal's submitting organization has a matching organization type entry and that entry's code resolves in the IGW_ORGANIZATION_TYPES lookup.

Key Columns

• PROPOSAL_ID — identifier of the proposal from IGW_PROPOSALS, allowing the result row to be tied back to a specific proposal record.
• ORGANIZATION_ID — the organization associated with the proposal through its submitting_organization_id, sourced from IGW_ORG_TYPES.
• LOOKUP_CODE — the organization type code defined under the IGW_ORGANIZATION_TYPES lookup type, as stored on the organization type record.
• MEANING — the user-facing, translatable display value corresponding to the lookup code, suitable for reports and list displays.

Because the lookup table is a view (IGW_LOOKUPS_V), the MEANING column inherits whatever language or territory behavior is configured for lookups in the environment.

Common Use Cases and Queries

Typical scenarios include validating that each proposal's submitting organization carries an expected organization type, displaying organization type descriptions alongside proposals in custom reports, and enforcing or auditing classification rules during proposal processing.

The following query retrieves the organization type details for a specific proposal:

• SELECT proposal_id, organization_id, lookup_code, meaning FROM apps.igw_prpo_org_types_v WHERE proposal_id = :p_proposal_id;

To find all proposals associated with a given organization type meaning:

• SELECT proposal_id, organization_id, lookup_code FROM apps.igw_prpo_org_types_v WHERE meaning = :p_meaning;

For auditing coverage, a query that identifies proposals lacking a resolvable organization type can be constructed by comparing IGW_PROPOSALS against this view using the proposal_id returned here, since inner-join semantics exclude unmatched rows. All access should be performed through the APPS schema with appropriate privileges, and results should be treated as read-only, as the view is not designed for direct DML.