Results for “attribute_display_name”

50+ results




Overview
Explore in AI Chat

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

Overview

EGO_ITEM_MAIN_ATTRS_V is a seed data dictionary view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the EGO product, Advanced Product Catalog, and its stated purpose is to return the primary (Main) item attributes used by the product catalog and item definition user interfaces. Rather than storing data itself, the view assembles a presentation-oriented list of attribute names, display labels, attribute group identity, and GUI sequencing numbers so that callers do not need to hard-code the composition or order of the Main attribute group.

The view has a direct relationship to the FND_NEW_MESSAGES table, which appears four times in the view text as part of a UNION. Each of those branches supplies the display_name for a specific catalog-related attribute by resolving a message name through the application message repository: EGO_CATALOG_GROUP, EGO_LIFECYCLE, EGO_LIFECYCLE_PHASE, and EGO_APPROVAL_STATUS. Because message text is language dependent, each branch filters on FND_NEW_MESSAGES.LANGUAGE_CODE = USERENV('LANG'), making the view multilingual by design. This is the connection that makes a search for "fnd_new_messages" relevant to an inquiry about EGO_ITEM_MAIN_ATTRS_V.

Underlying Base Objects

The ETRM metadata for 12.2.2 documents the following referenced base objects:

  • FND_NEW_MESSAGES (SYNONYM) — supplies translated display names for the lifecycle, phase, catalog group, and approval status attributes.
  • MTL_ITEM_ATTRIBUTES_V (VIEW) — supplies the attribute group identity, user-facing attribute name, sequence, and attribute name for the Main group.
  • MTL_ITEM_ATTR_APPL_INST_V (VIEW) — supplies the attribute application instance information joined on attribute name.
  • INV_ITEM_UTIL (PACKAGE) — the Inventory utility package referenced by the attribute metadata.

The first branch of the view restricts B.ATTRIBUTE_GROUP_ID_GUI to 20, decoding that identifier to the literal group name 'MAIN'. It joins the two view-based sources on attribute name and excludes three attributes that the catalog UI does not present through this mechanism (MTL_SYSTEM_ITEMS.DUAL_UOM_CONTROL, MTL_SYSTEM_ITEMS.DESC_FLEX, and MTL_SYSTEM_ITEMS.LONG_DESCRIPTION), and it filters on CONTROL_LEVEL IN (1, 2). Subsequent UNION branches append the four message-driven attributes with fixed GUI sequence numbers of 21 through 24.

Key Columns

The attribute group identifier is rendered through TO_CHAR so that the UNION branches produce consistent data types across the two source families.

Common Use Cases and Queries

The view is typically queried to enumerate the Main group attributes for a catalog or item setup screen, to validate that message-based labels resolve correctly in a given language, or to confirm the GUI ordering applied to lifecycle and approval attributes.

Listing the Main attributes in GUI order:

SELECT attribute_name,
       attribute_display_name,
       gui_sequence_num
FROM   apps.ego_item_main_attrs_v
ORDER  BY gui_sequence_num;

Isolating the message-driven attributes that depend on FND_NEW_MESSAGES:

SELECT attribute_name, attribute_display_name
FROM   apps.ego_item_main_attrs_v
WHERE  gui_sequence_num BETWEEN 21 AND 24;

Diagnosing a label resolution issue by comparing the view output against the underlying message rows:

SELECT message_name, message_text, language_code
FROM   fnd_new_messages
WHERE  message_name IN ('EGO_CATALOG_GROUP','EGO_LIFECYCLE',
                        'EGO_LIFECYCLE_PHASE','EGO_APPROVAL_STATUS')
AND    language_code = USERENV('LANG');