Results for “ego_itmattr_appl_usgs_v”

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

Overview

The EGO_ITMATTR_APPL_USGS_V view is a reporting and integration object owned by the APPS schema within the Advanced Product Catalog (EGO) module of Oracle E-Business Suite. Its documented purpose is to expose all Attribute Groups that are enabled for a given application. In the EGO data model, attribute groups provide the grouping mechanism through which item attributes, catalog attributes, and other extensible attributes are organized and presented to end users. Because attribute groups may be defined centrally but consumed by one or more applications, the relationship between a group and its using application is a many-to-many usage relationship rather than a simple ownership relationship.

The view resolves that many-to-many relationship into a flat, denormalized result set suitable for direct consumption by reports, concurrent programs, Oracle Discoverer queries, BPEL integrations, and custom PL/SQL. It is read-only by definition and reflects the current state of attribute group usage enablement via the ENABLED_FLAG column. Since the view joins against FND_APPLICATION_VL, each row also carries the human-readable application name and short name, eliminating the need for downstream joins against the application registry. The view is marked VALID in ETRM 12.2.2 and is present in both 12.1.1 and 12.2.2 environments, making it a stable target for cross-release customizations.

Underlying Base Objects

The view is defined over three referenced objects. EGO_ITMATTR_APPL_USGS_B is documented as a synonym in the ETRM metadata and represents the base usage table that stores the attribute-group-to-application assignments and their enablement state. EGO_ATTRS_V is a view that supplies attribute and attribute group definitions, including names, display names, and group types. FND_APPLICATION_VL is the standard Oracle Applications view over FND_APPLICATION that provides translatable application names and short names.

The join predicates are straightforward: ATTRS.ATTR_ID = USGS.ATTR_ID links each usage record to its attribute definition, and APPS.APPLICATION_ID = USGS.APPLICATION_ID links each usage record to the application that consumes the attribute group. Note that the view distinguishes two application identifiers: the application that owns the attribute group definition and the application that uses (consumes) the attribute group. This distinction is central to interpreting the result set correctly.

Key Columns

• ATTR_GROUP_ID — The identifier of the attribute group to which the attribute belongs.
• ATTR_GROUP_APPLICATION_ID — The application that owns or defines the attribute group. This is the column most commonly aliased or searched as the attribute group application.
• ATTR_GROUP_TYPE — The classification of the attribute group.
• ATTR_GROUP_NAME — The internal name of the attribute group.
• ATTR_ID, ATTR_NAME, ATTR_DISPLAY_NAME — The attribute identifier, internal name, and user-facing display name.
• USAGE_APPLICATION_ID — The application that consumes the attribute group.
• APPLICATION_SHORT_NAME, APPLICATION_NAME — The short name and descriptive name of the using application, sourced from FND_APPLICATION_VL.
• ENABLED_FLAG — Indicates whether the attribute group usage is enabled for that application.

Common Use Cases and Queries

Typical scenarios include listing all enabled attribute groups for a specific application, auditing which attributes belong to which group, and reconciling usage assignments before a catalog or item attribute configuration change.

SELECT ATTR_GROUP_NAME, ATTR_NAME, ATTR_DISPLAY_NAME,
       APPLICATION_SHORT_NAME, ENABLED_FLAG
  FROM APPS.EGO_ITMATTR_APPL_USGS_V
 WHERE USAGE_APPLICATION_ID = &application_id
   AND ENABLED_FLAG = 'Y'
 ORDER BY ATTR_GROUP_NAME, ATTR_NAME;

To identify all applications consuming a particular attribute group, filter on ATTR_GROUP_ID or ATTR_GROUP_APPLICATION_ID. To find attributes shared across applications, group by ATTR_ID and count distinct USAGE_APPLICATION_ID values. Because the view already joins FND_APPLICATION_VL, no additional application lookup is required.