Results for “maximum_size”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EGO_VALUE_SETS_V is a seeded APPS-owned view in Oracle E-Business Suite that exposes the value sets supported by the EGO (Advanced Product Catalog) application. It is defined over the Flexfields foundation table FND_FLEX_VALUE_SETS together with the EGO-specific extension table EGO_VALUE_SET_EXT and a set of decode views. Its principal function is to deliver a flattened, presentation-ready catalogue of value sets — covering format, size, validation, and range constraints — so that Advanced Product Catalog functionality and downstream reporting can query this information without joining the raw flexfield and EGO extension objects directly.

The view is a key integration point for value set driven behavior within EGO, most notably for attribute groups, item catalog attributes, and standardized lists. Because it converts stored lookup codes into their meanings, it is well suited to operational reporting and to integrations that need human-readable descriptions alongside the underlying identifiers. Unlike base tables, the view is read-only and carries no data of its own; it is a structural projection of the objects beneath it.

Underlying Base Objects

The ETRM metadata documents the following referenced objects:

• FND_FLEX_VALUE_SETS (referenced via synonym) — the core source of value set identity, name, format type, maximum size, description, longlist flag, minimum value, maximum value, and validation type.
• EGO_VALUE_SET_EXT (referenced via synonym) — holds the EGO-specific extension attribute, notably the parent value set identifier, joined with an outer join on FLEX_VALUE_SET_ID.
• EGO_VS_FORMAT_CODES_V — supplies the meaning for the format type (FORMAT_MEANING).
• EGO_VS_DISPLAY_CODES_V — supplies the meaning for the longlist/display flag (LONGLIST_FLAG_MEANING).
• EGO_VS_VALIDATION_CODES_V — supplies the validation code and its meaning (VALIDATION_MEANING).

The joins are equijoins on the lookup codes between FND_FLEX_VALUE_SETS and each decode view, with the extension table attached via a non-enforced outer join. This ensures value sets without a corresponding EGO extension record still appear in the result set.

Key Columns

• VALUE_SET_ID — the unique flex value set identifier (FLEX_VALUE_SET_ID), the primary join key.
• VALUE_SET_NAME — the user-visible name of the value set.
• FORMAT_CODE / FORMAT_MEANING — the stored format type code and its translated meaning.
• MAXIMUM_SIZE — the maximum length of values permitted in the set.
• DESCRIPTION — descriptive text for the value set.
• LONGLIST_FLAG / LONGLIST_FLAG_MEANING — whether the set is presented as a longlist, with its meaning.
• VALIDATION_CODE / VALIDATION_MEANING — the value validation code; note it is decoded so a stored 'X' is presented as 'I', and the associated meaning.
• MINIMUM_VALUE / MAXIMUM_VALUE — the numeric bounds applied to values in the set. MAXIMUM_VALUE is the column surfaced to users searching for range limits.
• VALIDATION_CODE_ADMIN — the raw validation type retained for administrative purposes.
• PARENT_VALUE_SET_ID — the parent value set from the EGO extension, where applicable.

Common Use Cases and Queries

Typical uses include auditing which value sets are exposed to Advanced Product Catalog, comparing minimum and maximum bounds, and identifying value sets by validation or display behavior. A representative query listing value sets with their range limits is:

SELECT value_set_id,
       value_set_name,
       format_meaning,
       maximum_size,
       minimum_value,
       maximum_value,
       validation_meaning
  FROM apps.ego_value_sets_v
 WHERE maximum_value IS NOT NULL
 ORDER BY value_set_name;

To locate parent-child relationships, filter on PARENT_VALUE_SET_ID; to inspect descending sets. Because the view is read-only and consolidated, it is the preferred access path for EGO value set metadata in both custom reports and integration extracts.