Search Results oe_pc_constraints_admin_pvt




Overview
Explore in AI Chat

Overview

OE_PC_CONSTRAINTS_ADMIN_PVT is the private PL/SQL package body in the APPS schema that implements the internal processing logic for constraint administration within the Oracle Order Management constraint engine. The constraint engine, commonly referred to as Processing Constraints, enforces business rules that govern which operations a user may perform on an order or order line given its current state. The public package OE_PC_CONSTRAINTS_ADMIN_PUB exposes the callable API surface, while OE_PC_CONSTRAINTS_ADMIN_PVT contains the private procedures and functions that perform the underlying validation, metadata maintenance, and caching work. In Oracle EBS 12.1.1 and 12.2.2, this package supports the entity-relationship model in which constraints are defined against entities, conditions, validation templates, and result sets, and are stored in the OE_PC_* tables. The package also generates and manages the dynamically created validation packages recorded in OE_PC_VALIDATION_PKGS, which is central to how the engine executes user-defined validation logic at runtime.

Key Procedures and Functions

The documented program units in this package are five in number:

  • MAKE_VALIDATION_PKG — Constructs the generated validation package associated with a constraint definition, writing the resulting package metadata into OE_PC_VALIDATION_PKGS and supporting the dynamic execution of constraint validation logic.
  • CHECK_ON_INSERT_EXISTS — Verifies whether a constraint definition already exists before insertion, helping to prevent duplicate constraint records in OE_PC_CONSTRAINTS.
  • CLEAR_CACHED_RESULTS — Purges cached validation or constraint results so that subsequent checks reflect current metadata, which is important after constraint definitions are changed.
  • VALIDATE_CONSTRAINT — Performs the core validation of a constraint definition, checking its attributes, conditions, and relationships against the referenced entity, template, and result-set views.
  • IS_OP_CONSTRAINED — Determines whether a given operation is restricted by an applicable constraint, returning the result used by the constraint engine to allow or block the operation.

No parameter signatures are documented here; callers should reference the package specification for exact interfaces.

Tables Accessed

The package reads and writes the core constraint engine tables and their supporting views via APPS synonyms. Constraint definitions are stored in OE_PC_CONSTRAINTS, with assignments in OE_PC_ASSIGNMENTS and exclusions in OE_PC_EXCLUSIONS. Result-set definitions are held in OE_PC_RSETS and OE_PC_RSET_SEL_COLS. Validation templates and their columns reside in OE_PC_VTMPLTS and OE_PC_VTMPLT_COLS, and generated validation packages are recorded in OE_PC_VALIDATION_PKGS. The package also references the descriptive views OE_PC_ATTRIBUTES_V, OE_PC_CONDITIONS_V, OE_PC_ENTITIES_V, OE_PC_FKEY_COLS_V, OE_PC_RENTITIES_V, and OE_PC_UKEY_COLS_V for metadata lookups, as well as OE_AK_OBJECTS_EXT and OE_AK_OBJ_WF_ITEMS for object and workflow item context. DUAL and PLITBLM support standard PL/SQL utility operations.

Usage Notes

Because it is a PVT package, OE_PC_CONSTRAINTS_ADMIN_PVT is not intended for direct invocation by external callers. It is called by OE_PC_CONSTRAINTS_ADMIN_PUB, by OE_CODE_CONTROL, and by other constraint-engine components such as OE_MSG_PUB, OE_DEBUG_PUB, and OE_PC_GLOBALS. The package is referenced by sixteen other packages, confirming its role as an internal workhorse rather than a public API. In practice it is invoked indirectly when users define or maintain processing constraints through the Order Management setup forms, when the constraint engine evaluates an operation during order entry, and when custom code or concurrent processing triggers the public admin API. Developers extending the constraint engine should target the public package and treat this body as internal implementation subject to change between releases.