Search Results attr_group_application_id

Overview

APPS.EGO_ITMATTR_APPL_USGS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Extensible Attribute / Item Attributes framework, owned by the APPS schema. It presents a denormalized, human-readable join of item attribute usages against application registrations, resolving the internal numeric identifiers used across the EGO (Engineering/Extensible Attributes) schema into their descriptive equivalents from FND_APPLICATION_VL and EGO_ATTRS_V.

In EBS 12.1.1 and 12.2.2 the EGO schema underpins flexfield and extensible attribute functionality used by Inventory, Order Management, Purchasing, and related modules. The view is commonly consulted when administrators and technical consultants need to answer which applications consume a given item attribute group or attribute, and under which display names. The identifier ATTR_GROUP_APPLICATION_ID is the owning application of the attribute group and is frequently the search term that surfaces this view. Because it resolves both attribute-group application context and per-usage application context into a single row, it is well suited to ad-hoc SQL, BI Publisher data templates, and outbound integration extracts.

Underlying Base Objects

The documentation records three referenced base objects, combined through an inner-join structure in the underlying view text:

• EGO_ITMATTR_APPL_USGS_B (SYNONYM) — the usage table supplying ATTR_GROUP_ID, ATTR_ID, APPLICATION_ID, and ENABLED_FLAG. This is the driving object that records which applications use which attributes within an attribute group.
• EGO_ATTRS_V (VIEW) — supplies the attribute-group and attribute descriptive columns, including APPLICATION_ID, ATTR_GROUP_TYPE, ATTR_GROUP_NAME, ATTR_NAME, and ATTR_DISPLAY_NAME.
• FND_APPLICATION_VL (VIEW) — the application lookup, providing APPLICATION_SHORT_NAME and APPLICATION_NAME.

The two join predicates in the view text are attrs.ATTR_ID = usgs.ATTR_ID and apps.APPLICATION_ID = usgs.APPLICATION_ID. Note that the attribute-group application context flows from EGO_ATTRS_V, while the usage application context flows from the usage table, so the view deliberately exposes two distinct application dimensions in one row.

Key Columns

• ATTR_GROUP_ID — surrogate identifier of the attribute group.
• ATTR_GROUP_APPLICATION_ID — the application that owns the attribute group, sourced from EGO_ATTRS_V.APPLICATION_ID. This is the column most closely matching the search term "attr_group_application_id."
• ATTR_GROUP_TYPE and ATTR_GROUP_NAME — classification and user-facing name of the attribute group.
• ATTR_ID — surrogate identifier of the individual attribute.
• ATTR_NAME and ATTR_DISPLAY_NAME — internal and user-facing names of the attribute.
• USAGE_APPLICATION_ID, APPLICATION_SHORT_NAME, APPLICATION_NAME — the application that consumes the attribute, with short and full names resolved via FND_APPLICATION_VL.
• ENABLED_FLAG — indicates whether the attribute usage is currently active for that application.

Common Use Cases and Queries

A typical scenario is auditing which applications consume a particular item attribute group, filtering on the owning application or on enabled usages only:

• SELECT attr_group_name, attr_name, attr_display_name, application_short_name, enabled_flag FROM apps.ego_itmattr_appl_usgs_v WHERE attr_group_application_id = :app_id;
• SELECT attr_group_name, attr_name, application_name FROM apps.ego_itmattr_appl_usgs_v WHERE enabled_flag = 'Y' ORDER BY attr_group_name, attr_name;
• Identifying an application's ID from a short name prior to filtering: SELECT application_id FROM fnd_application_vl WHERE application_short_name = 'INV';

These queries support attribute-usage audits, migration checks between 12.1.1 and 12.2.2, and extracts feeding external catalogs or integration endpoints. Because the view resolves identifiers to names, it is preferred over querying the base synonym directly.