Search Results nls_session_parameters

Overview

APPS.EGO_VALUE_SET_VALUES_V is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the values belonging to Oracle E-Business Suite flex value sets, together with descriptive attributes required for presentation and validation. It is owned by the APPS schema and is populated wholly through a join across flexfield value set, flexfield value, lookup, and EGO framework objects. Because the view resolves display sequencing and formatting metadata, it is the preferred source for external systems and concurrent programs that need a consumer-friendly rendering of value set contents rather than raw flexfield storage.

Notably, the view text references NLS_SESSION_PARAMETERS — the object matching the user search term. This synonym is queried in two scalar subqueries to obtain the session's decimal separator from NLS_NUMERIC_CHARACTERS, which is used to normalize numeric flex values.

Underlying Base Objects

The documented metadata lists eight referenced base objects: EGO_VS_DISPLAY_CODES_V, EGO_VS_FORMAT_CODES_V, EGO_VS_VALIDATION_CODES_V (all EGO framework views), EGO_VS_VALUES_DISP_ORDER (synonym over the display-order table), FND_FLEX_VALUES_VL (the multilingually-enabled flex values view), FND_FLEX_VALUE_SETS (synonym to the value set definition table), FND_LOOKUP_VALUES (synonym to the lookup values table), and NLS_SESSION_PARAMETERS (synonym exposing session NLS settings).

FND_FLEX_VALUE_SETS is joined to FND_FLEX_VALUES_VL on FLEX_VALUE_SET_ID, establishing the value set-to-value relationship. The EGO_VS_DISPLAY_CODES_V, EGO_VS_FORMAT_CODES_V, and EGO_VS_VALIDATION_CODES_V views are joined on FORMAT_TYPE, LONGLIST_FLAG, and VALIDATION_TYPE respectively, acting as code-to-meaning lookups that filter the value set to supported formats. FND_LOOKUP_VALUES supplies the enabled/disabled meaning from the YES_NO lookup, restricted to LANGUAGE = USERENV('LANG') and VIEW_APPLICATION_ID = 0. EGO_VS_VALUES_DISP_ORDER is outer-joined on both VALUE_SET_VALUE_ID and VALUE_SET_ID, supplying an optional display sequence.

Key Columns

• VALUE_SET_ID / VALUE_SET_NAME — identifier and name of the parent flex value set.
• FORMAT_TYPE / VALIDATION_TYPE — the value set's format (for example 'N' for number) and validation type (for example 'I' for independent).
• FLEX_VALUE_ID — unique identifier of an individual flex value.
• INTERNAL_NAME / DISPLAY_NAME — the stored value and its meaning. When FORMAT_TYPE = 'N' and VALIDATION_TYPE = 'I', the decimal point character is replaced with the first character of NLS_NUMERIC_CHARACTERS derived from the session.
• DESCRIPTION — free-text description of the value.
• ENABLED_CODE / ENABLED_MEANING — the enabled flag and its decoded YES_NO meaning.
• SEQUENCE — NVL of the configured display sequence and the flex value ID, guaranteeing a stable sort key.
• START_DATE / END_DATE — effective date range of the value.

Common Use Cases and Queries

The view is typically queried by integration layers to enumerate the valid values of a named value set, by reporting tools requiring display ordering, and by localization testing that exercises NLS numeric handling. A representative query filters a single value set:

SELECT flex_value_id, internal_name, display_name, enabled_meaning, sequence
FROM   apps.ego_value_set_values_v
WHERE  value_set_name = :p_value_set_name
ORDER  BY sequence;

For localization validation, the following isolates numeric independent value sets where session-driven substitution occurs:

SELECT value_set_name, internal_name, display_name
FROM   apps.ego_value_set_values_v
WHERE  format_type = 'N' AND validation_type = 'I';

Administrators should note that the NLS-dependent REPLACE applies only to numeric independent value sets, so results can vary with the session's NLS_NUMERIC_CHARACTERS setting. Absent an EGO_VS_VALUES_DISP_ORDER row, SEQUENCE falls back to FLEX_VALUE_ID, which may not match business ordering.