Results for “allow_multi_assign_flag”

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

Overview

HZ_CLASS_CATEGORIES is a classification reference table in the Oracle E-Business Suite Trading Community Architecture (TCA) model, owned by the AR (Receivables) schema and exposed through the Oracle Receivables product. Its documented description is "classification categories for classifying parties and related entities." In practice, the table defines the controlled vocabulary of category types — such as Industry, Customer Class, or a customer-defined classification category — against which parties, party sites, and other TCA entities are tagged with codes. Each row establishes a category, its owner, and the behavioral rules that govern how codes in that category may be assigned.

The table is a prerequisite object for the broader classification subsystem. Without an active, non-frozen category row, no code assignment can occur, because HZ_CODE_ASSIGNMENTS and HZ_CLASS_CODE_RELATIONS both enforce foreign keys back to CLASS_CATEGORY. The object behaves as a hub-leaning entity in Data Vault terms: it is a stable, relatively low-volume reference set keyed by a clean business key, and it anchors multiple downstream relationships rather than representing a transactional event. Modeling it as a hub with links to the assignment and code-relation tables is therefore a reasonable suggestion.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• CLASS_CATEGORY — the primary key and the sole column in HZ_CLASS_CATEGORIES_PK. It is the business identifier for the category and is also the parent column referenced by all downstream foreign keys.
• CLASS_OWNER_ID — identifies the owning entity for the category, supporting owner-scoped visibility and category reuse.
• APPLICATION_ID — indicates the application context to which the category belongs, allowing categories to be partitioned by EBS application.
• ALLOW_MULTI_PARENT_FLAG — controls whether a code in the category may be assigned to more than one parent, governing hierarchy breadth.
• ALLOW_MULTI_ASSIGN_FLAG — determines whether a single party may receive multiple codes from the category simultaneously.
• ALLOW_LEAF_NODE_ONLY_FLAG — restricts assignment to leaf nodes in a hierarchical code structure.
• DELIMITER — the character used to separate code levels in hierarchical classifications.
• FROZEN_FLAG — marks a category as frozen, preventing further modification or new assignments.
• OBJECT_VERSION_NUMBER — the optimistic locking token used by the TCA APIs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns populated by the TCA framework.
• CREATED_BY_MODULE — records the module that inserted the row, useful for diagnosing data-origination issues.
• ZD_EDITION_NAME — participates with CLASS_CATEGORY in the unique index HZ_CLASS_CATEGORIES_U1, supporting editioning of classification data.

The surrogate primary key is CLASS_CATEGORY; the business-key candidate is the composite of CLASS_CATEGORY and ZD_EDITION_NAME, as documented in HZ_CLASS_CATEGORIES_U1.

Common Use Cases and Queries

Typical usage covers lookup rendering in the Customer Standard and party entry forms, code-assignment validation, and reporting on how parties are segmented. A common query retrieves the active, non-frozen categories and their behavioral rules:

• SELECT class_category, class_owner_id, application_id, frozen_flag, allow_multi_assign_flag FROM hz_class_categories WHERE frozen_flag = 'N';
• Joining to assignments to count parties per category: SELECT c.class_category, COUNT(a.class_category) FROM hz_class_categories c, hz_code_assignments a WHERE c.class_category = a.class_category GROUP BY c.class_category;
• Listing all codes available within a category via HZ_CLASS_CODE_RELATIONS for category maintenance and validation screens.
• Auditing categories created by a specific module using CREATED_BY_MODULE.

Because the table is a reference set, reporting queries generally join outward to assignment tables rather than aggregating within it.

Related Objects

The documented foreign key relationships identify the following dependent objects:

• HZ_CLASS_CATEGORY_USES — references HZ_CLASS_CATEGORIES via CLASS_CATEGORY; defines where each category may be applied.
• HZ_CLASS_CODE_RELATIONS — references HZ_CLASS_CATEGORIES via CLASS_CATEGORY; maps hierarchical relationships between codes.
• HZ_CODE_ASSIGNMENTS — references HZ_CLASS_CATEGORIES via CLASS_CATEGORY; the primary table holding actual party-level code assignments.
• ZX_FC_TYPES_B — references HZ_CLASS_CATEGORIES via OWNER_ID_CHAR; links fiscal classification types to party classification categories.

Together these tables form the classification spine of the TCA model, with HZ_CLASS_CATEGORIES acting as the controlling hub that governs their content.