Search Results c_create

Overview

HZ_CLASS_VALIDATE_V2PUB is a public PL/SQL API package in the Oracle E-Business Suite Trading Community Architecture (TCA) schema, owned by APPS. It provides the server-side validation logic used by the TCA party and classification model to verify the integrity of classification categories, class codes, and code assignments before records are committed to the HZ_CLASS_CATEGORIES, HZ_CODE_ASSIGNMENTS, and related tables. The package belongs to the "V2PUB" generation of TCA APIs, which expose a public (PUB) interface intended for external callers, and it operates in conjunction with the class validation and category-use routines that govern how classifications are structured within the customer and party data model.

In Oracle EBS 12.1.1 and 12.2.2, the package appears in the APPS schema as a compiled body, with the header line indicating a controlled release (ARH2CLVB.pls). It is referenced by one other package, confirming its role as a reusable validation component rather than a standalone business transaction processor.

Key Procedures and Functions

The documented interface exposes 45 procedures and functions. The principal entries include:

• CHECK_EXISTENCE_CLASS_CATEGORY / EXIST_CLASS_CATEGORY — Verify that a given class category exists before dependent validation proceeds.
• VALIDATE_CLASS_CATEGORY / VALIDATE_CLASS_CATEGORY_USE — Confirm that a class category and its usage definition are correctly formed and permitted.
• IS_VALID_CLASS_CODE_MEANING — Validate that a class code carries an acceptable meaning.
• IS_VALID_DELIMITER — Check that delimiter characters used in class code construction are permitted.
• CHECK_START_END_ACTIVE_DATES / DATE_BETW_VALUE_DATES — Ensure the effective date range of a classification falls within permitted value dates.
• EXIST_CODE_ASS_NOT_NODE / EXIST_REVERSE_RELATION — Confirm code-assignment and reverse-relation consistency for hierarchical class codes.
• IS_ALL_CODE_ONE_PARENT_ONLY / IS_ALL_INST_LESS_ONE_CODE — Enforce the tree rules that each code has at most one parent and that each instance resolves to a single code.
• IS_LEAF_NODE_CATEGORY / IS_CATEG_MULTI_ASSIG — Determine leaf-node status and whether a category permits multiple assignments.
• INSTANCE_ALREADY_ASSIGNED / IS_ASSIG_RECORD_ID_VALID — Detect duplicate instance assignments and validate assignment record identifiers.
• EXISTENCE_COUPLE_CLACAT_OWNTAB — Validate the coupling between a class category and its owning table.
• SQL_VALID — Confirm that dynamically constructed SQL used in validation is syntactically valid.
• RESULT_CALLER / CHECK_ERR — Invoke the caller's result handling and evaluate return status.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• HZ_CLASS_CATEGORIES, HZ_CLASS_CATEGORY_USES, HZ_CLASS_CODE_RELATIONS, HZ_CODE_ASSIGNMENTS — the core TCA classification and assignment structures validated by the package.
• FND_LOOKUP_TYPES, FND_LOOKUP_VALUES — reference validation against lookup codes.
• FND_OBJECTS — object definition resolution for category ownership.
• DBMS_SQL, PLITBLM — dynamic SQL construction and PL/SQL table utilities used internally.

Usage Notes

HZ_CLASS_VALIDATE_V2PUB is typically invoked from TCA classification forms, concurrent validation programs, and custom PL/SQL that creates or updates class categories and code assignments. Callers should invoke validation before DML and inspect the return status, since failures set FND_API.G_RET_STS_ERROR and populate the FND message stack. The package is intended to be called by the TCA framework rather than directly by end users, and any custom integration should respect the V2PUB calling conventions and the documented table dependencies.