Search Results biosketch_type_name

Overview

IGW_BIOSKETCH_TYPES_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema that exposes the set of valid biographic sketch (biosketch) type codes and their user-facing names. It is a lookup-backed view defined entirely over the Oracle Application Object Library (FND) lookup infrastructure rather than over a dedicated base table. The view presents one row per lookup code belonging to the lookup type IGW_BIOSKETCH_TYPES, translating the internal code into a descriptive meaning suitable for display.

In Oracle EBS 12.1.1 and 12.2.2, this view belongs to the Grants/Proposal (IGW) product family, which supports sponsored research and proposal management functionality. Its role in reporting and integration is to provide a stable, human-readable reference for biosketch classification values without requiring report authors or integration developers to filter and decode the underlying FND_LOOKUPS table themselves. The view is deliberately narrow: it standardizes the join and predicate required to retrieve the biosketch type list, ensuring consistent behavior across forms, reports, and external interfaces that need to present or validate biosketch types.

Underlying Base Objects

According to the documented view text, IGW_BIOSKETCH_TYPES_V is defined as a single-table selection over FND_LOOKUPS:

• FND_LOOKUPS — the FND lookup table that stores lookup codes, meanings, descriptions, and associated attributes across all lookup types in the EBS instance. The view restricts rows with the predicate WHERE LOOKUP_TYPE = 'IGW_BIOSKETCH_TYPES'.

No other base tables, synonyms, or additional referenced objects are documented for this view. Because the view is not a simple projection of a dedicated IGW table, it inherits the standard characteristics of lookup-driven data: the content is maintained through the application's lookup maintenance forms or concurrent loader programs, and it reflects whatever enabled or disabled lookup codes exist for the IGW_BIOSKETCH_TYPES type in the current instance. No filtering on enabled status is embedded in the documented view text, so rows are returned for all matching lookup rows in FND_LOOKUPS for that type.

Key Columns

The view exposes exactly two columns, both sourced from FND_LOOKUPS:

• BIOSKETCH_TYPE — mapped from LOOKUP_CODE. This is the stored code value for a biosketch type. It is the value typically persisted on related transactional records and used programmatically for validation and joins.
• BIOSKETCH_TYPE_NAME — mapped from MEANING. This is the display name corresponding to the code, intended for presentation in forms, reports, and user-facing output. This is the column most commonly searched when users look for a readable biosketch type description.

No additional descriptive, date, or status columns are exposed by the documented view text; any further attributes would need to be obtained directly from FND_LOOKUPS.

Common Use Cases and Queries

The view is used wherever a list of biosketch types or the display name for a given type is required. Typical scenarios include value-list population, report parameter derivation, and lookup of a friendly name from a stored code.

Retrieve all available biosketch types for a list of values:

• SELECT biosketch_type, biosketch_type_name FROM apps.igw_biosketch_types_v ORDER BY biosketch_type_name;

Resolve the display name for a specific stored code:

• SELECT biosketch_type_name FROM apps.igw_biosketch_types_v WHERE biosketch_type = :p_biosketch_type;

Join to transactional data using the code as the key:

• SELECT t.biosketch_id, v.biosketch_type_name FROM igw_biosketches t, apps.igw_biosketch_types_v v WHERE t.biosketch_type = v.biosketch_type;

Because the view does not restrict on enabled status, consumers requiring only active values should join to FND_LOOKUPS directly to apply the appropriate enabled flag criteria, or validate the returned set against the current lookup configuration. This distinction matters when the same view is used across environments with differing lookup maintenance histories.