Results for “hz_class_category_uses”

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

Overview

HZ_CLASS_CATEGORY_USES is a reference metadata table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Usage of class categories by owner tables." The table records which registries, entities, or owner tables within the Oracle Trading Community Architecture (TCA) model are permitted to use a given class category, and it further defines the physical column and optional filtering clause by which that classification is applied. In effect, it acts as the configuration bridge between the abstract class category definitions maintained in HZ_CLASS_CATEGORIES and the concrete owner tables that store classification codes.

The metadata classifies this object, on a heuristic basis, as satellite-leaning. In a Data Vault modeling interpretation, this suggests HZ_CLASS_CATEGORY_USES behaves as a descriptive satellite attached to the class category hub rather than as an independent hub or a pure link table. Its identifying attributes (class category plus owner table) qualify the parent category, describing how and where that category may be consumed.

Key Information Stored

The table is documented with 13 columns. The most significant are:

• CLASS_CATEGORY — The class category code being described. This is the foreign key referencing HZ_CLASS_CATEGORIES.CLASS_CATEGORY and forms part of the primary key.
• OWNER_TABLE — The name of the owner (consumer) table that is allowed to use the referenced class category. It completes the primary key.
• COLUMN_NAME — The specific column within the owner table where the classification value is physically stored.
• ADDITIONAL_WHERE_CLAUSE — An optional predicate that further narrows the applicable rows within the owner table.
• APPLICATION_ID — Identifies the Oracle application that owns the usage registration.
• CREATED_BY_MODULE — Indicates the module that inserted the row, useful for provenance tracing.
• OBJECT_VERSION_NUMBER — The optimistic locking column used for concurrent update control.
• ZD_EDITION_NAME — The editioning column supporting EBS 12.2 online patching and edition-based redefinition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns capturing audit and last-modification context.

The documented primary key is HZ_CLASS_CATEGORY_USES_PK (CLASS_CATEGORY, OWNER_TABLE). The unique index HZ_CLASS_CATEGORY_USES_U1 (CLASS_CATEGORY, OWNER_TABLE, ZD_EDITION_NAME) is the business-key candidate, extending the PK with the editioning column to preserve uniqueness across patch editions. The PK itself does not rely on a generated surrogate identifier; the business attributes serve as the natural key.

Common Use Cases and Queries

Because this table governs where class categories may be applied, it is consulted whenever classification behavior must be validated or reported. Typical scenarios include reconciling which tables carry a given classification, generating impact analyses before retiring a class category, and dynamically discovering the storage column for a category during integration or migration work.

A representative query lists all usages for a category:

• SELECT owner_table, column_name, additional_where_clause FROM hz_class_category_uses WHERE class_category = :p_category;

To enumerate every category applicable to a target owner table:

• SELECT c.class_category, c.class_category_name FROM hz_class_categories c, hz_class_category_uses u WHERE u.owner_table = :p_table AND u.class_category = c.class_category;

Edition-aware reporting on 12.2.x should include ZD_EDITION_NAME to avoid harvesting rows from multiple editions.

Related Objects

The most significant relationships center on the class category definition and the owner tables that consume it:

• HZ_CLASS_CATEGORIES — Parent definition table; joined via HZ_CLASS_CATEGORY_USES.CLASS_CATEGORY = HZ_CLASS_CATEGORIES.CLASS_CATEGORY. This is the documented foreign key.
• HZ_CODE_ASSIGNMENTS — Stores the actual classification codes assigned to entities; used together with this table to resolve where and how a code applies.
• HZ_CLASS_CODE_DENORM — Denormalized classification storage frequently populated using the column mappings defined here.
• HZ_CLASS_CATEGORY_USES consumers such as Customer, Contact, and Party entity tables that appear as OWNER_TABLE values.
• TCA APIs (for example, HZ_CLASSIFICATION_V2PUB in the public TCA packages) — Validate classifications at runtime by consulting the usage registrations held here.

Together these objects form the metadata backbone that allows TCA classifications to remain flexible across many owner tables in EBS 12.1.1 and 12.2.2.