Search Results igw_lookups_v




Overview
Explore in AI Chat

Overview

IGW_LOOKUPS_V is a database view owned by the APPS schema within the Oracle E-Business Suite environment. It is associated with the IGW product, which corresponds to the Grants Proposal module. The ETRM documentation classifies this object with a status of VALID and describes it as "10SC Only," indicating that the view is restricted to a specific 10SC configuration or deployment context rather than being a general-purpose object across all EBS installations. This is a meaningful qualification, because it means the view exists to serve a narrowly scoped functional requirement tied to the Grants Proposal product rather than to provide a broadly reusable lookup abstraction.

The view exposes lookup data drawn from the Oracle Applications common lookup infrastructure. Its role in reporting and integration is that of a filtered, presentation-ready source of enabled lookup values, allowing consumers to query active lookup codes without having to apply the enablement and effective-dating predicates themselves. Because it presents a simplified four-column projection of lookup content, it is well suited to concurrent programs, Oracle Reports, and integrations that require a stable, pre-filtered set of lookup values for a given lookup type.

Underlying Base Objects

The documented base object for this view is FND_LOOKUPS, the standard Oracle Applications lookup values table maintained by the Application Object Library. The view text is defined as:

The ETRM metadata records no additional referenced base objects beyond FND_LOOKUPS. The view therefore functions as a thin filtering layer over that single table, applying three conditions: the lookup must be enabled, it must have reached its active start date, and it must either have no end date or have an end date that has not yet passed. Notably, the view retains the LOOKUP_TYPE column, so it returns values across all lookup types rather than constraining the result to a single type.

Key Columns

  • LOOKUP_TYPE — Identifies the lookup category to which the row belongs. This is the primary discriminator when filtering the view for a specific set of values.
  • LOOKUP_CODE — The internal code stored in transactional data. This is the value typically referenced by database columns elsewhere in the schema.
  • MEANING — The user-facing, translated display text corresponding to the lookup code.
  • DESCRIPTION — Additional descriptive text for the lookup value, where maintained. It is optional and frequently null.

The projection deliberately omits administrative columns such as ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE, and the attribute columns, presenting only the four columns relevant to consumption.

Common Use Cases and Queries

The most common use is retrieving the valid values for a single lookup type within Grants Proposal processing, for example to populate a list of values or to resolve a code to its meaning during reporting. A typical query takes the following form:

  • SELECT LOOKUP_CODE, MEANING FROM APPS.IGW_LOOKUPS_V WHERE LOOKUP_TYPE = 'IGW_PROPOSAL_STATUS' ORDER BY MEANING;
  • SELECT LOOKUP_CODE, MEANING, DESCRIPTION FROM APPS.IGW_LOOKUPS_V WHERE LOOKUP_TYPE = :p_lookup_type;

Because the view applies the effective-date and enablement predicates internally, callers obtain only currently valid values, which reduces the risk of an integration referencing a retired or not-yet-active code. A related pattern is joining the view to transactional tables to translate stored codes into meanings for report output. Consumers should note the "10SC Only" restriction documented in the ETRM metadata and confirm availability within their specific installation before depending on the view. Where the view is unavailable or where a broader lookup source is required, the same result can be achieved by querying FND_LOOKUPS directly with equivalent filtering conditions.