Results for “v_t”

10 results




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

Overview

APPS.EGO_VALIDATION_TABLE_INFO_V is a reporting and integration view in Oracle E-Business Suite that exposes the definition of table-validated value sets. A table-validated value set is one whose permitted values are drawn directly from columns of a database table rather than from a static list or an independent value set. The view resolves the metadata describing which table supplies the values, which columns carry the value, the meaning, and the identifier, and how the application layer names the owning application.

The object belongs to the Oracle Application Object Library (FND) flexfield infrastructure and is consumed largely by Oracle Product Information Management and the Trading Community Architecture (EGO schema) components. Because EGO and FND flexibility logic is shared, the view is generally consulted during configuration review, data validation, and integration mapping exercises rather than through direct end-user forms. It presents one row per value set table association, keyed functionally by FLEX_VALUE_SET_ID.

Underlying Base Objects

The view is defined over two documented base objects:

  • FND_FLEX_VALIDATION_TABLES (accessed as a synonym) — the core dictionary table that stores, for each table-validated value set, the application and table name together with the column names, data types, and sizes of the value, meaning, and ID columns, plus any additional WHERE clause fragment used to restrict the returned rows.
  • FND_APPLICATION_TL (accessed as a synonym) — the translated application name table.

The two objects are joined with an outer join on TABLE_APPLICATION_ID = FND_APPLICATION_TL.APPLICATION_ID, filtered by LANGUAGE = USERENV('LANG') so that the application name is returned in the session language. The outer join ensures that a validation table row is returned even when no translated application name exists for the current language.

Key Columns

Common Use Cases and Queries

Typical uses include documenting value set configuration, verifying that a validation table and its columns still exist after an upgrade, and generating mappings for data conversion or integration. A common query lists the validation sources for a specific value set:

SELECT flex_value_set_id, application_table_name, value_column_name,
meaning_column_name, id_column_name, table_application_name
FROM apps.ego_validation_table_info_v
WHERE flex_value_set_id = :p_value_set_id;

To find all value sets drawing from a given table, filter on APPLICATION_TABLE_NAME. To audit additional restrictions, select FLEX_VALUE_SET_ID and ADDITIONAL_WHERE_CLAUSE where the clause is not null. Because the view performs a language-sensitive outer join, results depend on the session NLS language, and integration code should always qualify the view with the APPS schema and observe standard EBS security and synonym conventions when calling it from external programs.