Search Results ego_vs_values_disp_order




Overview
Explore in AI Chat

Overview

The EGO_VS_VALUES_DISP_ORDER table resides in the EGO schema, the database owner for the Advanced Product Catalog (APC) module in Oracle E-Business Suite. Its documented purpose is to store the display order for value set values — that is, the sequence in which individual values belonging to a value set are presented to users within the product catalog and related value set administration interfaces. This ordering capability allows organizations to control the presentation of pick lists, LOVs (lists of values), and attribute-driven value prompts so that the most relevant or commonly used entries appear first, rather than in arbitrary alphabetical or insertion order.

From a data-modeling perspective, the mined Data Vault classification for this object is standalone. This heuristic suggests the table functions as an independent reference or configuration store rather than a transactional link or a descriptive satellite attached to a parent hub. Practitioners modeling the EGO schema should treat it as a configuration table whose rows carry a business rule (ordering) rather than auditable transactional history, though the presence of standard EBS audit columns means row-level change tracking is available.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • VALUE_SET_VALUE_ID — Identifies the individual value within a value set whose display position is being recorded. Together with VALUE_SET_ID, this forms part of the business key.
  • VALUE_SET_ID — Foreign key to FRM_PART_VALUE_SETS, identifying the parent value set that owns the values being ordered.
  • DISP_SEQUENCE — The numeric ordering value that determines the relative display position of the associated value set value. This is the operational payload of the table.
  • ZD_EDITION_NAME — Part of the unique business key, supporting edition-based (ZD) multi-versioning semantics used by APC seeded data.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS who-columns providing audit and concurrency information.

The unique index EGO_VS_VALUES_DISP_ORDER_U1 covers (VALUE_SET_ID, VALUE_SET_VALUE_ID, ZD_EDITION_NAME), establishing the business-key candidate. The physical surrogate primary key is not separately documented beyond this unique constraint.

Common Use Cases and Queries

Typical scenarios include verifying the configured display sequence of a value set, diagnosing why catalog values appear in an unexpected order, and reporting on value set configuration for governance reviews. A representative query joining to the parent value set table is:

SELECT v.value_set_id, v.value_set_value_id, v.disp_sequence
FROM   ego.ego_vs_values_disp_order v
WHERE  v.value_set_id = :value_set_id
ORDER BY v.disp_sequence;

To detect values missing an explicit ordering entry, an outer join against the value set values table can be used. For audit purposes, filtering on LAST_UPDATE_DATE supports change tracking across configuration freezes. Reporting extracts commonly feed catalog administration dashboards where sequence violations indicate misconfiguration.

Related Objects

  • FRM_PART_VALUE_SETS — Referenced via EGO_VS_VALUES_DISP_ORDER.VALUE_SET_ID; the parent value set definition.
  • EGO_VS_VALUES_VL / EGO_VS_VALUES_TL — Value set value definitions keyed by VALUE_SET_VALUE_ID, joined to retrieve value text.
  • EGO_VS_VALUE_SETS_VL — Value set header information for catalog attribute prompts.
  • Advanced Product Catalog value set administration UI and concurrent programs that consume display order.
  • Standard EBS audit views and the APC setup migration utilities that load display sequences.