Results for “ego_attr_groups_v”

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

Overview

EGO_ATTR_GROUPS_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the EGO product family, Advanced Product Catalog, which underpins the extensible attribute framework used across Oracle's product information management and order capture flows. The view exposes metadata describing User-Defined Attribute Groups. In the EGO data model, an attribute group corresponds to a descriptive flexfield context: a named, application-scoped container that groups a set of user-defined attributes (segments) for a particular entity, such as an item, a category, or a business object.

Rather than storing attribute group definitions in a bespoke EGO table, the view presents a denormalized, reporting-friendly projection of the Oracle Flexfields engine. It joins the descriptive flexfield context definition, an EGO-specific extension table, the context translation table, and three lookup value rows that resolve coded flags into their display meanings. The result is a single row per attribute group, enriched with translated names and human-readable status values.

The view serves reporting, integration, and diagnostics. Because it returns context names, display names, descriptions, security settings, and multi-row indicators in one pass, it is commonly used by technical consultants building extracts, by integration developers mapping EGO attributes to external systems, and by DBAs auditing descriptive flexfield configuration.

Underlying Base Objects

The view text joins four documented base objects, surfaced in APPS through synonyms:

• FND_DESCR_FLEX_CONTEXTS (FL_CTX) — the canonical descriptive flexfield context definition. Supplies APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME (exposed as ATTR_GROUP_TYPE), DESCRIPTIVE_FLEX_CONTEXT_CODE (exposed as ATTR_GROUP_NAME), and ENABLED_FLAG.
• EGO_FND_DSC_FLX_CTX_EXT (FL_CTX_EXT) — an EGO extension table keyed by the same flexfield context identity. It adds ATTR_GROUP_ID, OWNING_PARTY_ID, MULTI_ROW, SECURITY_TYPE, VIEW_PRIVILEGE_ID, EDIT_PRIVILEGE_ID, AGV_NAME, REGION_CODE, BUSINESS_EVENT_FLAG, PRE_BUSINESS_EVENT_FLAG, VARIANT, NUM_OF_COLS, and NUM_OF_ROWS.
• FND_DESCR_FLEX_CONTEXTS_TL (TL) — the translation table, supplying DESCRIPTIVE_FLEX_CONTEXT_NAME and DESCRIPTION for the session language (USERENV('LANG')).
• FND_LOOKUP_VALUES (L1, L2, L3) — three aliases of the same lookup table, each filtered to LOOKUP_TYPE and the session language, resolving ENABLED_FLAG, MULTI_ROW, and SECURITY_TYPE into their MEANING values.

Joins are performed on the composite key of APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DESCRIPTIVE_FLEX_CONTEXT_CODE.

Key Columns

• ATTR_GROUP_ID — surrogate identifier for the attribute group.
• APPLICATION_ID — owning application of the flexfield.
• ATTR_GROUP_TYPE — the descriptive flexfield name.
• ATTR_GROUP_NAME — the flexfield context code.
• ATTR_GROUP_DISP_NAME / DESCRIPTION — translated context name and description.
• ENABLED_CODE / ENABLED_MEANING — coded and decoded enabled status.
• MULTI_ROW_CODE / MULTI_ROW_MEANING — whether the group supports multiple rows.
• SECURITY_CODE / SECURITY_MEANING — group security classification.
• VIEW_PRIVILEGE_ID / EDIT_PRIVILEGE_ID — privilege identifiers governing read and edit access.
• OWNING_PARTY_ID, AGV_NAME, REGION_CODE, VARIANT, NUM_OF_COLS, NUM_OF_ROWS, BUSINESS_EVENT_FLAG, PRE_BUSINESS_EVENT_FLAG — implementation attributes controlling rendering, layout, and event behavior.

Common Use Cases and Queries

Typical use cases include enumerating all attribute groups for an application, identifying enabled versus disabled groups, and extracting group metadata for integration mappings.

• List enabled attribute groups: SELECT attr_group_name, attr_group_disp_name FROM ego_attr_groups_v WHERE enabled_code = 'Y' ORDER BY attr_group_disp_name;
• Report multi-row groups: SELECT attr_group_id, attr_group_disp_name, multi_row_meaning FROM ego_attr_groups_v WHERE multi_row_code = 'Y';
• Filter by flexfield: SELECT attr_group_name, description FROM ego_attr_groups_v WHERE attr_group_type = :flexfield_name;
• Integration extract: SELECT attr_group_id, application_id, attr_group_type, attr_group_name, security_code, view_privilege_id, edit_privilege_id FROM ego_attr_groups_v;

Because the view is language-dependent, results vary by the session language, and it should always be queried through APPS rather than the underlying tables directly.