Results for “default_template_name”

10 results




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

Overview

EGO_CATALOG_GROUPS_V is an APPS-owned database view in Oracle E-Business Suite that supports the Advanced Product Catalog (EGO) module. It exposes Item Catalog Categories — the hierarchical classification structure used to organize items in the item master — in a flattened, report-friendly form. The view consolidates the catalog group's key flexfield segments, its concatenated display value, parent-child hierarchical relationships, item creation control flags, and default item template assignments into a single queryable object.

Because it joins the key flexfield view (MTL_ITEM_CATALOG_GROUPS_KFV) and resolves both the current catalog group and its parent to concatenated segment values, the view is the standard access point for reports and integrations that must present catalog categories with human-readable identifiers rather than raw numeric IDs. It is validated and shipped with the EGO product schema.

Underlying Base Objects

The ETRM metadata documents five referenced base objects, all accessed through APPS synonyms:

  • MTL_ITEM_CATALOG_GROUPS — the primary base table holding each catalog group's numeric identifier, parent identifier, individual SEGMENT1 through SEGMENT20 values, description, item creation flag, and inactive date.
  • MTL_ITEM_CATALOG_GROUPS_KFV — the key flexfield view supplying CONCATENATED_SEGMENTS for the catalog group (alias CGV) and for its parent (alias CGPV), plus descriptive flexfield attribute columns.
  • EGO_CAT_GRP_TEMPLATES — the association table linking catalog groups to item templates; the join is outer and restricted to rows where DEFAULT_FLAG = 'Y'.
  • MTL_ITEM_TEMPLATES — supplies the default template identifier and name.
  • FND_LOOKUP_VALUES — resolves the ITEM_CREATION_ALLOWED_FLAG into a translated MEANING.

The parent join to MTL_ITEM_CATALOG_GROUPS_KFV is an outer join, so top-level categories return a null parent value rather than being excluded. Template and lookup joins are likewise outer, preserving catalog groups that have no template or unresolvable lookup code.

Key Columns

Common Use Cases and Queries

The view is widely used for catalog category reporting, hierarchy validation, default template auditing, and inbound item interfaces that must translate category names to IDs. A typical listing of active categories follows:

SELECT catalog_group_id, catalog_group, parent_catalog_group, creation_allowed_meaning
FROM apps.ego_catalog_groups_v
WHERE end_date IS NULL
ORDER BY catalog_group;

To locate the segments behind a specific category:

SELECT catalog_group, segment1, segment2, segment3
FROM apps.ego_catalog_groups_v
WHERE catalog_group = 'ELECTRONICS.COMPONENTS';

To identify categories permitting direct item creation along with their default template:

SELECT catalog_group, default_template_name, creation_allowed_meaning
FROM apps.ego_catalog_groups_v
WHERE creation_allowed = 'Y' AND end_date IS NULL;

Because the remote join to the key flexfield view can be costly on large hierarchies, queries should filter on catalog_group_id or segment values wherever possible, and restrict against END_DATE when only active categories are required.