Search Results okc_cle_pvt




Overview
Explore in AI Chat

Overview

OKC_CLE_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Contracts (OKC) module and supports the CLE subsystem, which governs contract line elements and line-level attribute manipulation within the Contracts Core architecture. As a PVT-classified package, it is not intended for direct invocation by external consumers; it provides the internal implementation layer consumed by the OKC public APIs, most notably OKC_API and OKC_OLE_PVT, which expose contract line handling to forms, concurrent programs, and integration code.

The package encapsulates the data manipulation and validation logic required to insert, update, delete, and version contract line records. It centralizes row-level locking, multi-language translation handling, class-operation validation, and version control operations so that higher-level public APIs remain thin wrappers. The body reports a VALID status and references a broad set of FND and OKC utilities, including FND_API for the standard API return-status conventions, FND_GLOBAL for session context, OKC_DEBUG for diagnostic tracing, and OKX and QP objects for list and price list integration.

Key Procedures and Functions

The documented interface exposes eighteen procedures and functions. Their names and purposes are as follows:

  • QC — quality-control helper, typically used to assert internal consistency of line data or call parameters before persistence.
  • CHANGE_VERSION — coordinates a change of the version context for a contract line, driving the versioning workflow.
  • API_COPY — copies line data from a source record to a target, commonly used during contract duplication or line propagation.
  • ADD_LANGUAGE — inserts translated descriptive columns for an additional language.
  • INSERT_ROW — creates a new contract line record.
  • LOCK_ROW — acquires a row-level lock for the identified line prior to modification.
  • UPDATE_ROW — modifies an existing contract line record.
  • DELETE_ROW — removes a contract line record subject to standard validation.
  • FORCE_DELETE_ROW — performs an unconditional delete, bypassing standard referential checks for administrative cleanup.
  • VALIDATE_ROW — executes business-rule validation against a line before insert or update.
  • INSERT_ROW_UPG — a variant of insert used during upgrade or data-migration processing.
  • CREATE_VERSION — establishes a new version of the contract line, writing history records.
  • RESTORE_VERSION — reinstates a prior version of the line.

All routines follow the FND_API calling convention, returning status codes and error message stacks to the caller rather than raising unhandled exceptions across the API boundary.

Tables Accessed

The package reads and writes the principal Contracts line tables. OKC_K_LINES_B, OKC_K_LINES_BH, OKC_K_LINES_TL, and OKC_K_LINES_TLH hold the base, history, translated, and translation-history rows for contract lines; OKC_K_LINES_V supplies the joined view used for validation. OKC_K_HEADERS_ALL_B provides the parent contract header context. OKC_CLASS_OPERATIONS and OKC_OPERATION_INSTANCES/OKC_OPERATION_LINES support class-operation rules applied to lines. OKC_STATUSES_B supplies status lookups. FND_LANGUAGES, FND_LOOKUPS, and FND_CURRENCIES_VL provide reference data, while QP_LIST_HEADERS_B, QP_LIST_LINES, OKX_LIST_HEADERS_V, and OKX_QP_LIST_LINES_V link lines to price lists and list headers. DUAL and PLITBLM are utility references.

Usage Notes

OKC_CLE_PVT is invoked indirectly through OKC_API and OKC_OLE_PVT. Contract entry forms, the contract versioning concurrent programs, and upgrade scripts call those public wrappers, which in turn delegate to this body. Because it is a PVT package and is referenced by roughly fifty other packages, customizations should avoid direct calls and instead use the supported public OKC APIs. Developers performing data migration or diagnostics may query the underlying tables directly, but any DML should be routed through the API layer to preserve validation, versioning, and language handling.