Search Results make_validation_pkg




Overview
Explore in AI Chat

Overview

APPS.OE_PC_CONSTRAINTS_ADMIN_PVT is a private PL/SQL package within the Oracle Order Management (OM) constraint engine. Its role is to administer the metadata that drives Order Management's Processing Constraints framework — the rules that determine whether an order, order line, or return may be created, modified, cancelled, or deleted in a given state, responsibility, or workflow context. The package is the "administrator" companion to the constraint-validation packages: it does not itself evaluate whether a business rule is satisfied at runtime, but rather constructs, caches, and manages the dynamically generated validation PL/SQL units and control-table SQL used by the validation layer.

The object is classified as PVT, meaning it is an internal helper package formally documented in ETRM but not intended as a public, supported API. External developers should treat it as implementation detail of the Processing Constraints framework. Its header ($Header: OEXVPCAS.pls 120.1 2006/03/29) indicates it has been stable since the earlier point-release line and is carried forward largely unchanged in EBS 12.1.1 and 12.2.2.

A caller searching on "validation_entity" has correctly identified the central concern of this package: constraints are defined against an owning entity (for example, an order line) and optionally against a validation entity, the related entity used to check the primary entity's state. The procedure parameters and cache keys of this package are built around the pair p_entity_id / p_validation_entity_id, and the CLEAR_CACHED_RESULTS routine uses the validation entity id as its selective key.

Key Procedures and Functions

  • MAKE_VALIDATION_PKG — The core generator. Given the owning entity and the validation entity (each identified by id, short name, and database object name), the validation template, the record set, and a global record name, it emits the name of the generated package together with its specification and body source, the control-table SQL, and standard return status/message outputs. This is the routine that materializes a constraint definition into executable validation code.
  • CHECK_ON_INSERT_EXISTS — Returns a Boolean indicating whether any attribute-specific constraints for the entity have check-on-insert enabled, evaluated for a supplied responsibility and optionally an application. Introduced under Bug 1755817 to let callers avoid unnecessary validation work on insert.
  • CLEAR_CACHED_RESULTS — Purges cached validation results. When a validation_entity_id is supplied, only entries for that validation entity are removed; otherwise the entire cache is cleared, allowing a targeted refresh after constraint metadata changes.
  • VALIDATE_CONSTRAINT — Executes or routes constraint validation for a given entity/constraint combination.
  • IS_OP_CONSTRAINED — Determines whether an operation is subject to one or more processing constraints, used by forms and business logic to decide whether to invoke full validation.

Tables Accessed

The package operates almost entirely on the OE_PC_* constraint metadata tables. OE_PC_CONSTRAINTS and OE_PC_VTMPLTS (with OE_PC_VTMPLT_COLS) define the constraints and validation templates; OE_PC_ASSIGNMENTS maps constraints to the entities and operations they govern; OE_PC_EXCLUSIONS records exceptions; OE_PC_RSETS and OE_PC_RSET_SEL_COLS describe record sets and their selected columns; and OE_PC_VALIDATION_PKGS stores the generated validation package definitions. OE_AK_OBJECTS_EXT and OE_AK_OBJ_WF_ITEMS supply entity and workflow-item metadata from the extensibility layer, while DUAL and PLITBLM are used for trivial expression evaluation and index-by-table PL/SQL constructs respectively.

Usage Notes

This package is invoked indirectly through the Order Management Processing Constraints engine — typically triggered from the Order Management and Shipping Execution forms, the constraint maintenance UI, and internal OM APIs whenever constraints are saved, regenerated, or evaluated. Because it is a PVT package referenced by sixteen other packages, direct invocation from custom code is discouraged; customers should use supported OM public APIs or the constraint setup forms. When customizations do call it, callers must pass complete entity and validation-entity metadata, honor the x_return_status/x_msg_count contract, and clear cached results after any metadata change to avoid stale validation behavior.