Results for “ego_functions_v”

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

Overview

EGO_FUNCTIONS_V is a reporting view owned by the APPS schema within the EGO (Advanced Product Catalog) product module of Oracle E-Business Suite. It exposes metadata about User-Defined Functions that are registered and used by the Advanced Product Catalog extensibility framework. These functions represent configurable extension points that allow organizations to invoke custom PL/SQL logic, lookups, or validation routines during catalog operations such as item creation, attribute validation, and change management.

The view is read-only and is intended as a denormalized, language-aware presentation layer over the base configuration tables. Because it joins the base table to its translation table and to a lookup, it delivers a single record per function with both the internal identifier and the human-readable display text resolved for the current session language. This makes it suitable for reporting, integration extracts, and diagnostic queries without requiring the caller to resolve translation and lookup joins independently.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms from APPS:

• EGO_FUNCTIONS_B — the base (non-translated) table holding the function definition, including the function identifier, internal name, function type, and the two generic function-info columns.
• EGO_FUNCTIONS_TL — the translation table providing the display name and description, joined on FUNCTION_ID and filtered to the session language.
• FND_LOOKUP_VALUES — the standard Oracle lookups view, joined on lookup type EGO_EF_FUNCTION_TYPE to translate the internal function type code into its meaning.

All three are joined through the FUNCTION_ID key, with the lookup restricted by VIEW_APPLICATION_ID = 0 and LANGUAGE equal to USERENV('LANG'), ensuring both translation and lookup values are returned in the user's active language.

Key Columns

• FUNCTION_ID — the primary surrogate key identifying each user-defined function.
• INTERNAL_NAME — the developer-facing system name of the function, sourced from EGO_FUNCTIONS_B. This is the column most commonly targeted in configuration and integration lookups.
• DISPLAY_NAME — the translated, user-facing label for the function.
• DESCRIPTION — the translated description explaining the function's purpose.
• FUNC_TYPE_CODE — the raw function type code (aliased from FUNCTION_TYPE).
• FUNC_TYPE_MEANING — the lookup meaning for the function type, providing a readable category.
• FUNCTION_INFO_1 and FUNCTION_INFO_2 — generic parameter columns holding function-specific configuration values.

Common Use Cases and Queries

A frequent scenario is locating a specific extension by its internal name, which is why "internal_name" is a common search term. The following query retrieves a function by internal name along with its readable type and description:

• SELECT function_id, internal_name, display_name, func_type_code, func_type_meaning, description FROM ego_functions_v WHERE internal_name = :p_internal_name;
• SELECT internal_name, display_name, func_type_meaning FROM ego_functions_v WHERE func_type_code = :p_type ORDER BY display_name;

These queries support troubleshooting of catalog extensibility setup, validation of which functions are registered for a given type, and building integration extracts that reference functions by their stable internal name rather than the translatable display name.