Search Results ego_attrs_v




Overview
Explore in AI Chat

Overview

EGO_ATTRS_V is a public view owned by the APPS schema within the EGO – Advanced Product Catalog product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose, per the ETRM repository, is to expose metadata information about User-Defined Attributes (UDAs) defined against descriptive flexfields used by Advanced Product Catalog.

In practice, the view acts as a denormalized metadata dictionary. Rather than requiring report developers to join the descriptive flexfield definition tables, the extended attribute registration table, value sets, and multiple lookup tables independently, EGO_ATTRS_V presents a single, joined row per user-defined attribute. Each row carries the technical binding (application, flexfield name, context, column name), the presentation attributes (prompt, description, display name), the validation characteristics (value set, format, range, longlist flag), and the behavioral flags controlling enablement, required entry, searchability, and hierarchy behavior. This makes it a convenient source for metadata-driven reporting, integration mapping, and configuration auditing, where consumers need to know what attributes exist and how they are constrained without querying the underlying flexfield infrastructure directly.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

  • FND_DESCR_FLEX_COLUMN_USAGES – the core descriptive flexfield column usage definition, supplying application, flexfield name, context code, segment column, sequence, value set, prompt flags, and required/enabled/display flags.
  • FND_DESCR_FLEX_COL_USAGE_TL – the translated (language) table for column usage, contributing the form-left prompt and description text.
  • EGO_FND_DF_COL_USGS_EXT – the Advanced Product Catalog extension table that augments the standard flexfield usage with UDA-specific attributes such as data type, unique key flag, search flag, control level, UOM class, attribute code, and hierarchy view/edit codes.
  • FND_FLEX_VALUE_SETS – supplies value set name, format type, maximum size, validation type, minimum and maximum values, and longlist flag.
  • FND_LOOKUP_VALUES – joined four times (aliases L1 through L4) to decode the enabled, required, search, and display flags into readable lookup meanings.

The joins link column usages to their translations on application, flexfield name, and context code, and to the EGO extension, value set, and lookup records, producing one coherent metadata row per attribute.

Key Columns

Common Use Cases and Queries

Typical uses include inventorying all UDAs for a given flexfield or context, auditing required or searchable attributes, and generating dynamic integration mappings from ATTR_NAME to DATABASE_COLUMN.

  • List attributes for a context: 
    SELECT attr_name, attr_display_name, data_type_code,
       required_meaning, search_meaning
FROM   apps.ego_attrs_v
WHERE  attr_group_type = :flexfield_name
AND    attr_group_name = :context_code
AND    enabled_flag = 'Y'
ORDER  BY sequence;
  • Find all searchable attributes: 
    SELECT attr_group_type, attr_group_name, attr_name
FROM   apps.ego_attrs_v
WHERE  search_flag = 'Y';
  • Retrieve value set validation details: 
    SELECT attr_name, value_set_name, validation_code_vs,
       minimum_value, maximum_value, longlist_flag
FROM   apps.ego_attrs_v
WHERE  value_set_id IS NOT NULL;