Search Results ego_attr_group_types_v




Overview
Explore in AI Chat

Overview

EGO_ATTR_GROUP_TYPES_V is a bilingual metadata view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It belongs to the EGO product family (Advanced Product Catalog) and exposes descriptive information about User-Defined Attribute Group Types, which are the descriptive flexfield definitions used to organize and store user-defined attributes on catalog entities such as items, change orders, and other objects managed by the Product Catalog. The view carries a status of VALID in the documented environment.

The view serves as a single, language-aware entry point into the flexfield registration metadata that drives attribute group behavior. Rather than joining the descriptive flexfield definition tables and the EGO extension table independently, consumers of this view obtain the flexfield identity, the physical extension table names, localized titles and descriptions, and the business-event and hierarchy integration points in one row per attribute group type.

Underlying Base Objects

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

The view performs an inner join between FND_DESCRIPTIVE_FLEXS and FND_DESCRIPTIVE_FLEXS_TL on APPLICATION_ID and DESCRIPTIVE_FLEXFIELD_NAME, and an outer join (marked with the (+) operator) to EGO_FND_DESC_FLEXS_EXT, so attribute group types remain visible even when no EGO extension row exists. The synonym resolution ultimately points to FND_DESCRIPTIVE_FLEXS_B and EGO_FND_DESC_FLEXS_EXT in their respective base tables.

Key Columns

  • APPLICATION_ID — the application owning the descriptive flexfield; participates in the join key to all three base objects.
  • ATTR_GROUP_TYPE — the descriptive flexfield name that uniquely identifies the attribute group type within its application.
  • EXT_TABLE_NAME — the application table where the flexfield's attribute values are stored (from FLEX.APPLICATION_TABLE_NAME).
  • EXT_TL_TABLE_NAME — the corresponding translation table name, if defined.
  • EXT_VL_NAME — the name of the associated view, where one exists.
  • ATTR_GROUP_TYPE_TITLE — the language-specific display title for the attribute group type.
  • DESCRIPTION — the language-specific description of the group type.
  • BUSINESS_EVENT_NAME — the Oracle Workflow business event raised when the attribute group is involved in a catalog operation.
  • HIERARCHY_NODE_QUERY and HIERARCHY_PROPAGATION_API — the query and PL/SQL API used to resolve hierarchy nodes and propagate attribute values through them.
  • PRE_BUSINESS_EVENT_NAME — the business event raised prior to the main attribute group event, supporting pre-processing logic.

Common Use Cases and Queries

The view is typically queried to enumerate the attribute group types available for a given application or to retrieve the physical table and event metadata associated with a specific group type. A typical lookup by title or application resembles:

  • SELECT application_id, attr_group_type, attr_group_type_title FROM ego_attr_group_types_v WHERE application_id = :app_id ORDER BY attr_group_type_title;
  • SELECT attr_group_type, ext_table_name, business_event_name FROM ego_attr_group_types_v WHERE attr_group_type = :group_type;
  • SELECT attr_group_type, hierarchy_node_query, hierarchy_propagation_api FROM ego_attr_group_types_v WHERE hierarchy_propagation_api IS NOT NULL;

Because titles and descriptions are translation-driven, queries executed under a non-English session automatically return the localized text, which is useful for building multilingual catalog setup and validation reports.