Search Results exist_code_ass_not_node

Overview

HZ_CLASS_VALIDATE_V2PUB is a public (PUB classification) PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Trading Community Architecture (TCA) classification module. Its documented purpose, as reflected in the header comment ("Component for every entities in classification module"), is to centralize existence, cardinality, and date-effectiveness validations for classification entities. The package operates against the HZ_CLASS_CATEGORIES, HZ_CLASS_CATEGORY_USES, HZ_CLASS_CODE_RELATIONS, and HZ_CODE_ASSIGNMENTS tables, which together model hierarchical class categories, the class codes they contain, the relations between those codes, and the assignment of codes to entities such as customers, contacts, and organizations. The functions return status indicators (typically 'Y'/'N' or a return status string) that calling forms and concurrent programs use to gate inserts, updates, and deletes against invalid classification data. The package is referenced by one other package and exposes 45 documented procedures and functions, several of which are internal validation helpers.

Key Procedures and Functions

• CHECK_EXISTENCE_CLASS_CATEGORY — Verifies that a given class category exists.
• IS_VALID_DELIMITER — Returns whether a supplied delimiter is valid for a given class category.
• IS_VALID_CLASS_CODE_MEANING — Validates the meaning associated with a class code within a category.
• RESULT_CALLER — Documented but commented out in the source; a generic result-handling utility.
• CHECK_ERR — Documented but commented out (referenced by Bug 3962783); an error-checking helper.
• CHECK_START_END_ACTIVE_DATES — Validates that the start and end active dates are consistent and correctly ordered.
• EXIST_CODE_ASS_NOT_NODE — Answers whether a category has one or more non-leaf-node class codes associated with instances of entities active as of a given date. This is the object the user searched for.
• EXIST_REVERSE_RELATION — Checks for the existence of a reverse relation between class codes.
• IS_ALL_CODE_ONE_PARENT_ONLY — Determines whether all codes within a category resolve to a single parent only.
• IS_ALL_INST_LESS_ONE_CODE — Determines whether all instances carry fewer than one code.
• EXIST_CLASS_CATEGORY — Additional existence check for a class category.
• VALIDATE_CLASS_CATEGORY — Performs the principal validation of a class category record.
• EXISTENCE_COUPLE_CLACAT_OWNTAB — Validates the existence of a class-category/owner-table combination.
• VALIDATE_CLASS_CATEGORY_USE — Validates a class category usage record.
• DATE_BETW_VALUE_DATES — Determines whether a date falls between value dates.
• INSTANCE_ALREADY_ASSIGNED — Detects whether an instance is already assigned a code.
• IS_LEAF_NODE_CATEGORY — Determines whether a category is a leaf node.
• IS_CATEG_MULTI_ASSIG — Determines whether a category permits multiple assignments.
• IS_ASSIG_RECORD_ID_VALID — Validates an assignment record identifier.
• SQL_VALID — Runs an internal validation using dynamic SQL.

Tables Accessed

All tables are referenced through APPS synonyms. HZ_CLASS_CATEGORIES stores the class category definitions examined by the existence and category validation routines. HZ_CLASS_CATEGORY_USES records category usage information validated by VALIDATE_CLASS_CATEGORY_USE and EXISTENCE_COUPLE_CLACAT_OWNTAB. HZ_CODE_ASSIGNMENTS holds code-to-entity assignments checked by INSTANCE_ALREADY_ASSIGNED and EXIST_CODE_ASS_NOT_NODE. HZ_CLASS_CODE_RELATIONS stores parent/child relationships used by EXIST_REVERSE_RELATION, IS_ALL_CODE_ONE_PARENT_ONLY, and IS_LEAF_NODE_CATEGORY. FND_LOOKUP_TYPES and FND_LOOKUP_VALUES supply lookup validation, FND_OBJECTS supports object metadata lookup for the classification framework, DBMS_SQL supports dynamic validation (SQL_VALID), and PLITBLM is the standard PL/SQL table/buffer utility package.

Usage Notes

HZ_CLASS_VALIDATE_V2PUB is an API-layer package invoked by TCA classification forms (such as the class category and code assignment setups) and by concurrent programs that mass-validate or load classification data. Custom extensions integrating with the classification model should call this package rather than duplicating validation logic, because it encapsulates the referential, hierarchy, and date-effectiveness rules for HZ_CLASS_CATEGORIES, HZ_CLASS_CODE_RELATIONS, and HZ_CODE_ASSIGNMENTS. Public (PUB) classification indicates the interfaces are supported for external and cross-module invocation, but callers must still respect the returned status and exception conventions. Because the package dates to the 12.1.1 source line (ARH2CLVS.pls, 2007) and remains documented in 12.2.2, behavior is consistent across both releases; nevertheless, validation should always be exercised against the target release's TCA data before promotion.