Search Results ego_value_set_values_v




Overview
Explore in AI Chat

Overview

The EGO_VALUE_SET_VALUES_V view resides in the APPS schema and belongs to the EGO — Advanced Product Catalog product family. It exposes the value set values available within the EGO application, presenting a flattened, reporting-friendly representation of Oracle Flexfields value set data. In Oracle EBS 12.1.1 and 12.2.2, value sets underpin the validation of descriptive flexfield segments, key flexfields, and numerous attribute groups used by Advanced Product Catalog and adjacent modules. Rather than requiring developers and analysts to join FND_FLEX_VALUE_SETS, FND_FLEX_VALUES_VL, and several EGO-specific display-ordering and lookup views manually, EGO_VALUE_SET_VALUES_V delivers this information pre-joined and decoded. This makes it a convenient integration and reporting surface for extracting valid catalog attribute values, driving pick lists, and reconciling value set definitions during implementation or data migration efforts.

Underlying Base Objects

The view is defined over both standard Oracle Application Object Library (FLEX) objects and EGO-specific objects. Per the documented metadata, the referenced base objects are:

  • FND_FLEX_VALUE_SETS (SYNONYM) — provides the value set header, including the value set name, format type, and validation type.
  • FND_FLEX_VALUES_VL (VIEW) — the translated flex values, supplying the internal value, meaning, description, enabled flag, and active date ranges.
  • EGO_VS_VALUES_DISP_ORDER (SYNONYM) — holds display sequencing overrides for values within a value set.
  • EGO_VS_FORMAT_CODES_V, EGO_VS_DISPLAY_CODES_V, and EGO_VS_VALIDATION_CODES_V (VIEWs) — lookup sources used to validate and decode the format, longlist/display, and validation attributes.
  • FND_LOOKUP_VALUES (SYNONYM) — resolves the YES_NO lookup that translates the enabled flag into a meaningful label.
  • NLS_SESSION_PARAMETERS (SYNONYM) — supplies the session language via USERENV('LANG') for translation and lookup filtering.

These sources are joined on FLEX_VALUE_SET_ID and, where applicable, on lookup codes, ensuring the returned rows are restricted to values that belong to a defined value set and to the caller's language context.

Key Columns

The view exposes thirteen columns that describe each value set value:

  • VALUE_SET_ID / VALUE_SET_NAME — the identifier and name of the parent value set.
  • FORMAT_TYPE / VALIDATION_TYPE — the format (e.g., character, number) and validation method defined on the value set.
  • FLEX_VALUE_ID — the unique identifier of the individual flex value.
  • INTERNAL_NAME — the stored flex value, i.e., the code used in validation.
  • DISPLAY_NAME — the flex value meaning, or translated display text.
  • DESCRIPTION — the descriptive text attached to the value.
  • ENABLED_CODE / ENABLED_MEANING — the raw enabled flag and its decoded YES_NO meaning.
  • SEQUENCE — the display sequence, defaulting to FLEX_VALUE_ID where no EGO_VS_VALUES_DISP_ORDER row exists (via NVL).
  • START_DATE / END_DATE — the active date range of the flex value.

Common Use Cases and Queries

Typical scenarios include listing all values for a named value set, retrieving only enabled values ordered by display sequence, and joining the view to catalog attribute definitions to reconcile allowed values. A representative query follows:

  • SELECT value_set_name, internal_name, display_name, enabled_meaning, sequence
  • FROM   ego_value_set_values_v
  • WHERE  value_set_name = :p_value_set_name
  • AND    enabled_code = 'Y'
  • AND    SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1)
  • ORDER BY sequence, display_name;

The view can also be used to audit sequencing overrides by comparing SEQUENCE against FLEX_VALUE_ID, or to populate external systems with valid catalog attribute values during integration. Because it is a view over supported FLEX and EGO dictionary objects, it remains consistent across 12.1.1 and 12.2.2 releases.