Search Results validate_class_category_use

Overview

HZ_CLASS_VALIDATE_V2PUB is a public PL/SQL validation package in the Oracle EBS Trading Community Architecture (TCA) / Customer Relationship Management classification module. Its role is to enforce the business rules governing class categories, class codes, class code relations, and the assignment of class codes to entity instances. In practice, it is the server-side gatekeeper for the classification hierarchy: whenever a class category is defined, used, or assigned, this package determines whether the operation is structurally and semantically valid.

The package is owned by APPS and is classified as PUB, meaning it is callable from external APIs and custom code. Its documented header comment describes it as the "component for every entity in the classification module," confirming its broad scope across HZ_CLASS_CATEGORIES, HZ_CLASS_CATEGORY_USES, HZ_CLASS_CODE_RELATIONS, and HZ_CODE_ASSIGNMENTS. It is referenced by one other package, indicating that higher-level classification or party APIs delegate validation to this component rather than duplicating the logic.

Key Procedures and Functions

• CHECK_EXISTENCE_CLASS_CATEGORY — verifies that a supplied class category exists and returns status accordingly.
• IS_VALID_DELIMITER — checks whether a delimiter is valid for a class category.
• IS_VALID_CLASS_CODE_MEANING — validates that a meaning is acceptable for a class code within a category.
• CHECK_START_END_ACTIVE_DATES — validates the date range supplied for a classification record.
• EXIST_CODE_ASS_NOT_NODE — returns 'Y' when a category has non-leaf-node class codes assigned to entity instances active as of a given date.
• EXIST_REVERSE_RELATION — detects whether a reverse class code relation already exists, preventing circular or conflicting hierarchy definitions.
• IS_ALL_CODE_ONE_PARENT_ONLY — determines whether all codes in a category conform to the single-parent rule.
• IS_ALL_INST_LESS_ONE_CODE — checks whether all instances carry fewer than one class code.
• EXIST_CLASS_CATEGORY / VALIDATE_CLASS_CATEGORY — existence and full validation entry points for a class category.
• EXISTENCE_COUPLE_CLACAT_OWNTAB — verifies the pairing of a class category with its owning entity/table.
• VALIDATE_CLASS_CATEGORY_USE — validates use of a class category by an entity.
• DATE_BETW_VALUE_DATES — confirms a date falls within the valid value-date window.
• INSTANCE_ALREADY_ASSIGNED — detects duplicate assignment of a class code to an instance.
• IS_LEAF_NODE_CATEGORY — determines whether a category is a leaf node in the hierarchy.
• IS_CATEG_MULTI_ASSIG — indicates whether a category permits multiple assignments.
• IS_ASSIG_RECORD_ID_VALID / SQL_VALID — validate assignment record identifiers and dynamic SQL safety.
• RESULT_CALLER / CHECK_ERR — utility routines for returning and interpreting validation status; both appear commented out in the source.

Tables Accessed

• HZ_CLASS_CATEGORIES — the primary category definition table, read for existence and structural checks.
• HZ_CLASS_CATEGORY_USES — records which entities may use which categories.
• HZ_CLASS_CODE_RELATIONS — the code hierarchy; central to EXIST_REVERSE_RELATION and parent/leaf checks.
• HZ_CODE_ASSIGNMENTS — instance-to-code assignments; central to duplicate and non-leaf assignment checks.
• FND_LOOKUP_TYPES / FND_LOOKUP_VALUES — lookup validation.
• FND_OBJECTS — resolves entity/object identifiers.
• DBMS_SQL / PLITBLM — dynamic SQL and index-by-table utilities used internally.

Usage Notes

This package is normally invoked indirectly. TCA classification forms and the higher-level classification APIs call it before committing category or code changes, and it is referenced by one dependent package that wraps its validations. Custom integrations that insert into HZ_CLASS_CATEGORIES or HZ_CODE_ASSIGNMENTS should call the appropriate validation routine (for example, EXIST_REVERSE_RELATION before creating a code relation) and honor the returned x_return_status. Because the package performs committed-consistent existence and date checks, it should be called within the same transaction that performs the DML, before commit.