Search Results group_start_date




Overview
Explore in AI Chat

Overview

HZ_CLASS_CATEGORY_GROUPINGS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered under the Receivables (AR) product family and shared with the Trading Community / Customer Relationship Management (HZ) data model. It exposes the relationship between classification category groupings and the individual categories that belong to them. A category grouping in the HZ model corresponds to a class category such as a customer classification or a party classification structure, while the member categories represent the individual lookup values permitted under that grouping.

The view is primarily used to resolve human-readable meanings for classification metadata. This is why the view is commonly located through searches for the term category_meaning: the CATEGORY_MEANING column returns the display meaning of a classification category, while CATEGORY_GROUP_MEANING returns the meaning of its parent grouping. Reporting layers, concurrent programs, and integration interfaces that must translate low-level classification codes into descriptive labels rely on this view rather than joining the base lookup tables directly.

The view is a non-key-preserved, read-only construct. Because it joins dynamic lookup views and applies effective-dating filters against SYSDATE, its result set changes automatically as classification groupings and categories are end-dated or re-activated. It is valid and available in both 12.1.1 and 12.2.2, and Oracle publishes it as proprietary and confidential ETRM metadata.

Underlying Base Objects

The view is defined over four documented base objects:

  • HZ_CLASS_CATEGORIES (synonym) — provides the member classification categories, their flags, delimiter, version number, and frozen status.
  • HZ_CODE_ASSIGNMENTS (synonym) — supplies the assignment records that link each category grouping code to a class category, along with the grouping's active dates.
  • FND_LOOKUP_TYPES_VL (view) — supplies the descriptive text for the class category itself, resolved through the lookup type derived from the assignment.
  • FND_LOOKUP_VALUES_VL (view) — supplies the descriptive text for the category grouping code.

The defining join is driven by HZ_CODE_ASSIGNMENTS, which is constrained to rows where CLASS_CATEGORY equals 'CLASS_CATEGORY_GROUP' and OWNER_TABLE_NAME equals 'HZ_CLASS_CATEGORIES'. The assignment's owner table key links to HZ_CLASS_CATEGORIES, while its class code links to the CLASS_CATEGORY_GROUP lookup values, and its owner key links to the corresponding lookup type. Effective-dating predicates using NVL on the lookup start and end dates, combined with the assignment active dates, ensure that only currently valid rows are returned.

Key Columns

Common Use Cases and Queries

Typical scenarios include generating classification reference listings, validating that a category belongs to the expected grouping before assignment, and enriching downstream extracts with descriptive category text.

List all active groupings with their member categories:

SELECT category_group_code, category_group_meaning, class_category, category_meaning FROM hz_class_category_groupings_v ORDER BY category_group_code, category_meaning;

Resolve the meaning of a specific category:

SELECT category_group_meaning, category_meaning FROM hz_class_category_groupings_v WHERE class_category = :p_class_category;

Identify groupings that permit only leaf-node assignment, which is useful when building hierarchical classification interfaces:

SELECT DISTINCT category_group_code, category_group_meaning FROM hz_class_category_groupings_v WHERE allow_leaf_node_only_flag = 'Y';

Because the view enforces SYSDATE-based effective dating, queries executed at different points in time may return different rows for the same classification structure; reports that require historical visibility should query the underlying base tables instead.