Results for “hz_class_code_relations”

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

Overview

HZ_CLASS_CODE_RELATIONS is a Receivables (AR) module table that stores the relationships between classification codes in Oracle E-Business Suite 12.1.1 and 12.2.2. Classification codes are the building blocks of the Trading Community Architecture (TCA) model, used to categorize parties, customers, and other entities through hierarchical taxonomies such as customer classes, industry codes, and geographic groupings. This table defines how one classification code relates to a sub-classification code within a given class category, effectively mapping parent-to-child (or code-to-sub-code) associations across the classification hierarchy.

The object resides in the AR schema and is documented as VALID. The documented physical schema records 14 columns and a unique business-key index, HZ_CLASS_CODE_RELATIONS_U1, over (CLASS_CATEGORY, CLASS_CODE, SUB_CLASS_CODE, START_DATE_ACTIVE, ZD_EDITION_NAME). From a Data Vault modeling perspective, the metadata heuristically classifies this table as satellite-leaning: it captures descriptive, time-bounded attributes describing relationships between classification code entities rather than serving as a standalone hub of core business keys.

Key Information Stored

The table's principal business columns define the classification relationship itself:

• CLASS_CATEGORY — the category that groups related classification codes; also the foreign key to HZ_CLASS_CATEGORIES and the leading column of the primary key.
• CLASS_CODE — the parent classification code participating in the relationship.
• SUB_CLASS_CODE — the subordinate classification code related to the parent within the same category.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the date range during which the relationship is active, enabling time-based validity of the hierarchy.

The primary key, HZ_CLASS_CODE_RELATIONS_PK, is composed of CLASS_CATEGORY, CLASS_CODE, SUB_CLASS_CODE, and START_DATE_ACTIVE. Because the PK combines business-meaningful columns, there is no separate standalone surrogate key; the business key and the primary key coincide. The unique index HZ_CLASS_CODE_RELATIONS_U1 adds ZD_EDITION_NAME to this same column set, supporting edition-based redefinition (EBR) in 12.2.2. The remaining documented columns are standard TCA/WHO audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER (optimistic locking), CREATED_BY_MODULE, and APPLICATION_ID, plus ZD_EDITION_NAME for EBR.

Common Use Cases and Queries

Typical uses include validating that a sub-class code is legitimately assignable under a parent class code, reporting on classification hierarchies, and joining classification assignments back to their category definitions.

• Hierarchy navigation: retrieve all sub-codes for a parent code with a filter on CLASS_CATEGORY and CLASS_CODE.
• Active-relationship reporting: restrict results to rows where SYSDATE falls between START_DATE_ACTIVE and END_DATE_ACTIVE (or END_DATE_ACTIVE IS NULL for open-ended rows).
• Category validation: join to HZ_CLASS_CATEGORIES on CLASS_CATEGORY to confirm the category exists and is enabled.
• Integration lookups: resolve the valid sub-class set when populating customer or party classification assignments during data conversion or inbound interfaces.

A representative query pattern is:

• SELECT class_category, class_code, sub_class_code, start_date_active, end_date_active FROM hz_class_code_relations WHERE class_category = :p_category AND class_code = :p_class AND (end_date_active IS NULL OR end_date_active > SYSDATE);

Related Objects

The most significant dependencies center on the classification framework and TCA:

• HZ_CLASS_CATEGORIES — joined on HZ_CLASS_CODE_RELATIONS.CLASS_CATEGORY = HZ_CLASS_CATEGORIES.CLASS_CATEGORY; the FK target for the category column.
• HZ_CLASS_CODES / class code definitions — the source of valid CLASS_CODE and SUB_CLASS_CODE values referenced by this table's business keys.
• HZ_CODE_ASSIGNMENTS — stores actual classification assignments to parties and accounts, cross-referenced against valid class/sub-class combinations.
• HZ_PARTIES and HZ_CUST_ACCOUNTS — the TCA entities whose classifications ultimately depend on the relationships defined here.
• HZ_CLASS_CODE_RELATIONS_PK / _U1 — the primary key constraint and unique index governing row uniqueness and EBR.
• TCA APIs (e.g., HZ_CUST_ACCOUNT_V2PUB / HZ_PARTY_V2PUB) — public interfaces that validate classification relationships during customer and party creation.