Search Results seg_val_types




Overview
Explore in AI Chat

Overview

APPS.EGO_VS_VALIDATION_CODES_V is a reporting view in Oracle E-Business Suite that exposes the set of value-set validation types available to the Oracle Product Information Management (PIM) / EGO schema, most notably to the value set and attribute validation framework used by Oracle Fusion-style descriptive flexfields and item attributes within EBS. The view is not a transactional object; it is a convenience, denormalized lookup source that surfaces a curated subset of the generic FND_LOOKUP_VALUES table.

Its practical role is to answer the question "which validation types can be assigned to a value set?" by restricting the generic FND lookup to a single lookup type, 'SEG_VAL_TYPES', and to the specific lookup codes that the EGO value set engine understands. This is why the view is frequently implicated when a user or report searches on "seg_val_types" — that string is the FND_LOOKUP_TYPE that drives the validation-type picklist used throughout the value set definition screens.

Because the view filters by VIEW_APPLICATION_ID = 0 and LANGUAGE = USERENV('LANG'), it presents the base application's language-specific, non-application-scoped lookup rows. This makes it suitable for direct use in BI Publisher data models, Oracle Reports, and custom SQL that must present the same validation-type list a user sees on the form.

Underlying Base Objects

Per the documented view definition, the only referenced base object is FND_LOOKUP_VALUES, accessed through its SYNONYM. The view performs no joins and no aggregation; it is a single-table projection with a WHERE clause. The definition is:

FND_LOOKUP_VALUES is the standard Oracle Application Object Library table that stores all extensible lookup codes, their meanings, enabled flags, and effective date ranges. By filtering on VIEW_APPLICATION_ID = 0, the view selects the shared (non-application-specific) rows, and by filtering on USERENV('LANG'), it returns only the rows matching the session language, preventing duplicate rows across installed languages.

Key Columns

  • LOOKUP_CODE — The validation type identifier. Documented values are 'F', 'I', 'N', and 'X', corresponding respectively to the validation types commonly rendered as Format, Independent/Table, None, and Special/Translatable-style checks in the EGO value set framework.
  • MEANING — The user-facing display name for the validation type, shown on value set definition forms and in reports.
  • ENABLED_FLAG — Indicates whether the lookup row is currently active ('Y') or disabled ('N'); reports generally filter to 'Y'.
  • START_DATE — Alias of START_DATE_ACTIVE; the date from which the validation type is effective.
  • END_DATE — Alias of END_DATE_ACTIVE; the date on which the validation type expires, or NULL for open-ended entries.

Common Use Cases and Queries

The view is typically queried to populate a validation-type picklist, to validate a stored value set definition during reconciliation, or to drive conditional formatting in a report that depends on the validation type used.

Listing all currently enabled validation types for the session language:

  • SELECT LOOKUP_CODE, MEANING FROM APPS.EGO_VS_VALIDATION_CODES_V WHERE ENABLED_FLAG = 'Y' ORDER BY MEANING;

Resolving the display meaning for a value set whose validation type is stored as a code:

  • SELECT v.LOOKUP_CODE, v.MEANING FROM APPS.EGO_VS_VALIDATION_CODES_V v WHERE v.LOOKUP_CODE = :p_validation_type;

Reporting against the effective window of a validation type:

  • SELECT LOOKUP_CODE, MEANING, START_DATE, END_DATE FROM APPS.EGO_VS_VALIDATION_CODES_V WHERE SYSDATE BETWEEN NVL(START_DATE, SYSDATE) AND NVL(END_DATE, SYSDATE + 1);

Because the view is a simple filtered projection over FND_LOOKUP_VALUES, it inherits that table's performance characteristics and requires no special privileges beyond SELECT on the APPS schema objects. Customizations should not modify the underlying lookup type, since 'SEG_VAL_TYPES' is seeded and maintained by Oracle.