Search Results okc_conditions_pub




Overview
Explore in AI Chat

Overview

OKC_AAL_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle Contracts (OKC) module, specifically the Conditions and Action-Attribute framework within Oracle E-Business Suite. The suffix "PVT" classifies this object as a private implementation package rather than a public API; it is not intended to be called directly by customer code. Its functional role is to support the Action Attribute Link (AAL) mechanism, which governs how attributes are associated with conditions, actions, and their lookups during contract authoring, evaluation, and copy operations. The package encapsulates the low-level row-level operations—insert, update, delete, lock, validation, and versioning—that higher-layer public packages rely upon, thereby centralising data integrity logic for the AAL-related structures.

Key Procedures and Functions

The ETRM metadata documents thirteen procedures and functions in this package. The following are the named entry points:

  • QC — A quality-control/consistency routine that performs internal checks against AAL data before or after other operations.
  • CHANGE_VERSION — Manages version changes for AAL records, ensuring that modifications respect the versioning model used by the Contracts conditions framework.
  • API_COPY — Copies AAL-related rows, typically invoked during contract duplication or template instantiation where condition and action attribute links must be replicated.
  • INSERT_ROW — Creates a new AAL record, applying defaulting and mandatory-attribute rules.
  • LOCK_ROW — Obtains a pessimistic lock on an AAL row to prevent concurrent modification during a transaction.
  • UPDATE_ROW — Modifies an existing AAL record with validation and audit handling.
  • DELETE_ROW — Removes an AAL record, subject to referential and validation checks.
  • VALIDATE_ROW — Performs attribute-level validation on AAL data prior to persistence.

Parameters are not enumerated in the metadata, and no parameter lists should be assumed. Collectively, these routines form a standard "row-handler" pattern common to ETRM private packages, providing a controlled gateway to the underlying tables.

Tables Accessed

The package references the following tables (via APPS synonyms):

  • OKC_ACTION_ATT_LOOKUPS — The primary table storing action attribute lookup definitions. It also references the view OKC_ACTION_ATT_LOOKUPS_V. This table drives the set of legal attribute values that AAL rows may bind to.
  • PLITBLM — The PL/SQL integer table (index-by table) used as an in-memory structure for bulk operations, list handling, and parameter marshalling within the package.

The dependency list additionally shows references to FND_API (the Oracle Application Object Library standard API utility package) and STANDARD (the EBS standard PL/SQL library), indicating that error handling, message stacking, and standard validations follow Oracle's documented API conventions.

Usage Notes

OKC_AAL_PVT is invoked indirectly. It is referenced by OKC_CONDITIONS_PUB and OKC_CONDITIONS_PVT (the user-facing and private Conditions APIs), by OKC_CONDITION_EVAL_PUB/PVT, and by OKC_INST_CND_PUB/PVT. It is also self-referenced, meaning some procedures call other routines within the same package. This package is therefore reached whenever contract conditions are authored, evaluated, copied, or instantiated—whether through the Contracts forms, concurrent programs that generate or refresh condition data, or public API calls such as OKC_CONDITIONS_PUB. Custom code should never invoke OKC_AAL_PVT directly; the supported integration route is through the corresponding _PUB packages. Because it is a PVT object, its signature may change across patch levels, so any direct dependency (for example, in a custom trigger or wrapper) is unsupported and vulnerable to invalidation on upgrade from 12.1.1 to 12.2.2.