Search Results related_category_description




Overview
Explore in AI Chat

Overview

The Oracle E-Business Suite view APPS.ICX_RELATED_CATEGORIES_VAL_V is a validation-oriented database object owned by the APPS schema. It is registered in Oracle's ETRM metadata with a status of VALID and is classified as an internal view (View Type: Internal). The view exposes valid category-to-related-category relationships, drawing on Oracle iProcurement (ICX) category relationship data combined with key flexfield (KFF) category attributes. In the context of Oracle EBS 12.1.1 and 12.2.2, this view functions primarily as a validation and lookup source for applications that need to resolve the descriptive and naming attributes of categories that are linked to a primary category through a defined relationship type.

The object is flagged with Oracle's standard "Oracle Internal Use Only" notice, meaning that Oracle does not formally support direct access to this data except through standard Oracle Applications programs. Nevertheless, it is a documented view, and its structure and dependencies are published in the ETRM. It is valuable for developers and analysts who need to understand how iProcurement resolves related category descriptions, particularly in the context of the RELATED_CATEGORY_DESCRIPTION attribute that connects related category identifiers to human-readable descriptions.

Underlying Base Objects

According to the documented dependencies, APPS.ICX_RELATED_CATEGORIES_VAL_V references the following base objects:

  • ICX_RELATED_CATEGORIES (referenced as a SYNONYM) — the core iProcurement table that stores the defined relationships between a category and its related categories, including the relationship type.
  • MTL_CATEGORIES_KFV (referenced as a SYNONYM) — the key flexfield (KFF) view over the category key flexfield in Oracle Inventory. It supplies the concatenated category name (and description where enabled) for the related category.

The view is itself referenced by at least one downstream object, APPS.ICX_REQ_CATEGORIES, confirming its role in the iProcurement requisition category pipeline. The use of KFV views means the descriptive text is flexfield-driven and may reflect the enabled segments and value-set definitions configured in the Inventory category flexfield.

Key Columns

The view exposes six columns, all of which are identified in the ETRM column listing:

  • CATEGORY_SET_ID (NUMBER) — identifier of the category set (flexfield structure) to which the category belongs.
  • CATEGORY_ID (NUMBER) — the primary category from which the relationship originates.
  • RELATED_CATEGORY_ID (NUMBER) — the identifier of the related category.
  • RELATED_CATEGORY_NAME (VARCHAR2, 163) — the concatenated flexfield name of the related category, typically derived from MTL_CATEGORIES_KFV.
  • RELATED_CATEGORY_DESCRIPTION (VARCHAR2, 240) — the descriptive text for the related category, and the specific column of interest for users searching on related_category_description.
  • RELATIONSHIP_TYPE (VARCHAR2, 30) — the code classifying the nature of the relationship between the category and its related category.

Common Use Cases and Queries

This view is most often queried when the objective is to retrieve the human-readable name and description of a category related to another category, for example to display related item categories during requisition entry or to build validation lists. A basic query is straightforward:

  • SELECT category_set_id, category_id, related_category_id, related_category_name, related_category_description, relationship_type FROM apps.icx_related_categories_val_v;
  • To filter by a primary category: SELECT related_category_name, related_category_description FROM apps.icx_related_categories_val_v WHERE category_id = :category_id;
  • To resolve a related category's description by identifier: SELECT related_category_description FROM apps.icx_related_categories_val_v WHERE related_category_id = :related_category_id;

These patterns support reporting, custom validation, and integration routines where the related category description is required without joining to the underlying Inventory flexfield view directly. Because the object carries Oracle's internal-use warning, custom code should prefer supported APIs and standard programs where equivalent functionality is available.