Results for “ego_validation_table_info_v”

28 results




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

Overview

The EGO_VALIDATION_TABLE_INFO_V view is a reporting and integration object in the Oracle E-Business Suite Advanced Product Catalog (EGO) module. It is owned by the APPS schema and resides in a VALID state on both Oracle EBS 12.1.1 and 12.2.2. The view exposes information about the value sets that are defined for "table" type validation, presenting the physical table and column metadata that underpins a table-validated value set. In the context of EGO, this information is used by the product catalog to resolve how a value set draws its list of valid values from a database table rather than from a static list.

The view is a denormalized, read-only projection. Rather than storing data itself, it joins the flexfield validation table definitions to the application name, giving consumers a single queryable source for table-based value set metadata. This makes it valuable for reporting on catalog and flexfield configuration, for data migration or integration scripts that must understand how validation tables are structured, and for diagnostics when a value set fails to return expected values.

Underlying Base Objects

The view is defined over two documented base objects in the APPS schema, both referenced through synonyms:

  • FND_FLEX_VALIDATION_TABLES — the core Oracle Application Object Library (FND) table that stores, for each table-validated flex value set, the identity of the validation table and its value, meaning, and ID columns along with their data types and sizes.
  • FND_APPLICATION_TL — the translated (language-specific) application definitions table, used to resolve TABLE_APPLICATION_ID into a readable application name.

The relationship is expressed as an outer join: F_A.APPLICATION_ID (+) = V_T.TABLE_APPLICATION_ID AND F_A.LANGUAGE (+) = USERENV('LANG'). The outer join ensures that rows from FND_FLEX_VALIDATION_TABLES are still returned even when no matching application translation exists, and the language predicate restricts the application name to the session language.

Key Columns

The view exposes the following important columns:

Common Use Cases and Queries

Typical scenarios include auditing table-validated value sets, tracing which application and table back a given value set, and driving integration code that must build dynamic lookup queries. A representative query listing value sets for a specific application table:

SELECT flex_value_set_id,
       table_application_name,
       application_table_name,
       value_column_name,
       meaning_column_name,
       additional_where_clause
FROM   apps.ego_validation_table_info_v
WHERE  application_table_name = :p_table_name;

To enumerate all value sets resolved against a given application:

SELECT flex_value_set_id, application_table_name, value_column_name
FROM   apps.ego_validation_table_info_v
WHERE  table_application_name = :p_app_name
ORDER  BY flex_value_set_id;

Because FLEX_VALUE_SET_ID is the join key, the view is frequently combined with FND_FLEX_VALUE_SETS to produce a complete picture of a value set's definition and its underlying table metadata.