Search Results ego_catalog_group

Overview

APPS.EGO_ITEM_MAIN_ATTRS_V is a consolidated reporting view that exposes the set of item attributes classified under the "Main" attribute group in Oracle E-Business Suite. Its primary purpose is to present a user-facing, translated catalog of the core descriptive and lifecycle attributes associated with an item master record, mapping internal column names to their GUI display labels and ordering them for presentation. The view is particularly significant for applications and integrations that need to resolve an attribute_display_name — the localized, message-based label shown to end users — rather than the underlying database column name. It supports the Product Information Management (PIM) and item definition flows, where the "Main" attribute group forms the default set of fields rendered on the item definition page.

Underlying Base Objects

The view is defined over several documented base objects. It joins MTL_ITEM_ATTR_APPL_INST_V and MTL_ITEM_ATTRIBUTES_V to enumerate applicable attributes and their translated user names, filtered to attribute_group_id_gui = 20 (the "Main" group). A series of UNION branches draw localized labels from FND_NEW_MESSAGES (referenced through a synonym), retrieving Message_Text by Message_Name and the session language via userenv('LANG'). The documented dependent objects also include the package INV_ITEM_UTIL. The FND_NEW_MESSAGES branch supplies display names for attributes that are not simple column labels — for example EGO_CATALOG_GROUP, EGO_LIFECYCLE, EGO_LIFECYCLE_PHASE, and EGO_APPROVAL_STATUS — each assigned a fixed GUI sequence number. The view therefore combines structural attribute metadata from the item attribute views with translated presentation text from the application messages table.

Key Columns

• Attribute_Group_id — Character representation of the attribute group identifier; effectively constant at 20 for this view.
• Attribute_Group_Name — Decoded group name, returned as 'Main'.
• Attribute_Name — The internal item attribute identifier, typically in the form MTL_SYSTEM_ITEMS.<COLUMN>.
• Attribute_Display_Name — The translated, user-facing label for the attribute; this is the column most relevant to searches for "attribute_display_name," sourced from user_attribute_name_gui or from FND_NEW_MESSAGES.Message_Text.
• Gui_Sequence_Num — The display order of the attribute within the Main group; note the message-sourced branches use fixed values (21, 22, 23, 24, 25) to position them after the base set.

Excluded attributes include MTL_SYSTEM_ITEMS.DUAL_UOM_CONTROL, MTL_SYSTEM_ITEMS.DESC_FLEX, and MTL_SYSTEM_ITEMS.LONG_DESCRIPTION, and only attributes with control_level in (1, 2) are returned.

Common Use Cases and Queries

A frequent requirement is to obtain the localized display label for a specific attribute. The following query retrieves the display name and ordering for the Main group:

• SELECT attribute_name, attribute_display_name, gui_sequence_num FROM apps.ego_item_main_attrs_v WHERE attribute_name = 'MTL_SYSTEM_ITEMS.LIFECYCLE_ID';
• SELECT attribute_display_name, gui_sequence_num FROM apps.ego_item_main_attrs_v ORDER BY gui_sequence_num; — reconstructs the ordered field list rendered on the Main item attribute page.
• SELECT attribute_name FROM apps.ego_item_main_attrs_v WHERE attribute_display_name LIKE :label; — reverse lookup from a displayed label back to its internal attribute name, useful in personalization and integration mapping.

These patterns are commonly used when building item interfaces, reports, or LOVs that must mirror the field labels and ordering presented in the PIM user interface, ensuring consistency between backend data processing and front-end terminology.