Search Results class_category_group




Overview
Explore in AI Chat

Overview

APPS.HZ_CLASS_CATEGORY_GROUPINGS_V is a reporting and integration view within the Oracle E-Business Suite Trading Community Architecture (TCA) data model. It presents the classification category groupings that are defined against the HZ_CLASS_CATEGORIES entity — that is, the set of category groups (such as Customer Class, Industry, or similar classification schemes) that a given class category is permitted to use. The view joins the class category definition to its code assignments and to the underlying lookup metadata, producing a flattened, human-readable result that exposes both the internal code values and their translated meanings and descriptions.

Because the view resolves foreign keys to FND_LOOKUP_VALUES_VL and FND_LOOKUP_TYPES_VL, consumers do not need to perform separate lookup joins to obtain display values. It also applies effective-dating filters, returning only those groupings and groups that are currently active as of the system date. This makes it suitable for operational reporting, concurrent programs, and interface extracts where only currently valid configuration is relevant.

Underlying Base Objects

The view is defined over four documented base objects. HZ_CLASS_CATEGORIES is the driving entity and supplies the category definition itself. HZ_CODE_ASSIGNMENTS provides the association between a class category and the lookup codes that represent permitted groupings, restricted by the predicate CLASS_CATEGORY = 'CLASS_CATEGORY_GROUP'. FND_LOOKUP_VALUES_VL supplies the meaning and description of each grouping code, while FND_LOOKUP_TYPES_VL supplies the meaning and description of the class category lookup type. The join conditions link the code assignment to the class category via OWNER_TABLE_NAME and OWNER_TABLE_KEY_1, and to the lookup values via LOOKUP_TYPE and LOOKUP_CODE. In 12.1.1 and 12.2.2 the HZ objects are referenced through APPS synonyms resolving to the HZ schema, and the FND objects are public synonyms to the same-named views.

Key Columns

Common Use Cases and Queries

A typical requirement is to list all currently active groups for a given class category. The view already filters effective dates, so a simple predicate suffices:

  • SELECT category_group_code, category_group_meaning FROM apps.hz_class_category_groupings_v WHERE class_category = 'CUSTOMER_CLASS' ORDER BY category_group_meaning;
  • Reporting on configuration for migration or audit, joining the view to other TCA entities via CLASS_CATEGORY.
  • Investigating whether a group has expired, by selecting GROUPING_END_DATE and GROUP_END_DATE to distinguish assignment-level expiry from lookup-level expiry.
  • Integration extracts feeding downstream systems that require both code and meaning without additional lookup resolution.

Because the view hard-codes SYSDATE comparisons, historical ("as of") queries cannot be satisfied directly; users needing point-in-time results must query HZ_CODE_ASSIGNMENTS and FND_LOOKUP_VALUES_VL directly. For all current-state reporting, however, the view remains the most convenient access path.