Search Results sub_class_code

Overview

The HZ_CLASS_CODE_RELATIONS table is a core data object within the Oracle E-Business Suite (EBS) Trading Community Architecture (TCA) framework, specifically under the AR (Receivables) product schema. It serves as a master repository for defining hierarchical and associative relationships between classification codes. Classification codes are a fundamental TCA construct used to categorize and segment parties, customer accounts, and locations based on attributes like industry, geography, or credit rating. This table enables the establishment of parent-child, peer-to-peer, or other logical linkages between these codes, providing a structured taxonomy that supports sophisticated data analysis, segmentation, reporting, and business rule enforcement across the EBS suite, particularly in modules leveraging TCA data such as Order Management and Receivables.

Key Information Stored

The table stores the essential components that define a valid relationship between two classification codes within a specific category. Its primary key underscores the uniqueness of each relationship record. Key columns include:

• CLASS_CATEGORY: The classification category (e.g., INDUSTRY_TYPE, CUSTOMER_CATEGORY) to which the related codes belong. This column is a foreign key to HZ_CLASS_CATEGORIES.
• CLASS_CODE: The primary or parent classification code within the relationship.
• SUB_CLASS_CODE: The secondary, child, or related classification code.
• START_DATE_ACTIVE: The date from which the relationship becomes effective, allowing for temporal management of these hierarchies.

Common Use Cases and Queries

A primary use case is generating hierarchical reports, such as rolling up individual industry codes into broader sectors for consolidated financial analysis. For instance, a query might retrieve all sub-codes for a given parent code to validate data entry or to drive dynamic lists of values in applications. Data integrity checks are another critical use; scripts often validate that codes assigned to customer profiles have valid, active relationships defined in this table. A typical query pattern involves joining to HZ_CLASS_CATEGORIES for descriptive names and filtering by CLASS_CATEGORY and effective dates:

SELECT rel.class_code, rel.sub_class_code, cat.name
FROM hz_class_code_relations rel, hz_class_categories cat
WHERE rel.class_category = cat.class_category
AND cat.class_category = 'INDUSTRY_TYPE'
AND SYSDATE BETWEEN rel.start_date_active AND NVL(rel.end_date_active, SYSDATE)
ORDER BY rel.class_code;

Related Objects

The table is centrally linked to other TCA classification master tables through its documented foreign key relationship. The primary dependency is:

• HZ_CLASS_CATEGORIES: The table references HZ_CLASS_CATEGORIES via the foreign key on the CLASS_CATEGORY column. This ensures that every relationship is defined within a valid, existing classification category.

While not listed in the provided metadata, this table is also conceptually related to core TCA entities like HZ_PARTIES and HZ_CUST_ACCOUNTS, which store the actual CLASS_CATEGORY and CLASS_CODE assignments for business entities. Data from HZ_CLASS_CODE_RELATIONS is typically accessed through public TCA views or APIs (e.g., HZ_CLASSIFICATION_V2PUB) for application development.