Results for “okl_kle_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_KLE_PVT is a private PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Enterprise Contracts / Oracle Leasing (OKL) module within the ETRM (Enterprise Transaction and Revenue Management) architecture. The object carries API classification PVT, indicating that it is an internal, private implementation package rather than a public application programming interface. Its primary business purpose is to manage the persistence and versioning of lease and contract line records — specifically the KLE (contract line) entity — within the OKL lease management subsystem. The package encapsulates low-level row operations, validation, locking, and version-control logic against contract lines so that higher-level public APIs can operate on those records consistently. The package is currently VALID, and it is referenced by 65 other database objects, confirming its role as a widely consumed internal utility layer.

Key Procedures and Functions

The documented interface exposes fifteen procedures and functions. The following ten entries are explicitly recorded in the metadata and define the package's core behavior:

• QC — A quality-control / consistency check routine used to verify the integrity of contract line data.
• CHANGE_VERSION — Moves or switches a record to a different version context, supporting the versioning model applied to contract lines.
• API_COPY — Copies contract line data, typically invoked during duplication or template-based creation of contract lines.
• INSERT_ROW — Performs the physical insert of a new contract line row.
• UPDATE_ROW — Performs the physical update of an existing contract line row.
• DELETE_ROW — Performs the physical deletion of a contract line row.
• VALIDATE_ROW — Applies validation rules to a row before it is committed, ensuring business and referential integrity.
• LOCK_ROW — Acquires a row-level lock to serialize concurrent modification of a contract line.
• CREATE_VERSION — Establishes a new version of a contract line within the versioning framework.
• RESTORE_VERSION — Restores a previously created version of a contract line, supporting audit and rollback requirements.

Together these routines implement a complete CRUD-plus-versioning cycle for contract lines. Parameter details are not published in the supplied metadata and should be obtained from the package specification source.

Tables Accessed

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

• OKL_K_LINES — The principal contract/lease line table and the primary target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW operations.
• OKL_K_LINES_H — The history (audit) table for contract lines, populated as part of versioning and change tracking.
• OKC_K_LINES_B — The base contract lines table inherited from the OKC contracts layer, used for shared contract-line attributes.
• OKL_SUBSIDIES_B — Stores subsidy-related data associated with lease lines, accessed during validation or copying.
• PLITBLM — The standard PL/SQL table of character records, used internally for bulk or in-memory processing of row data.

The package itself also appears in its own dependency list, reflecting recursive or internal references typical of private implementation bodies.

Usage Notes

As a PRIVATE-classified package body, OKL_KLE_PVT is not intended to be called directly by external or customer-developed code. It is invoked internally by OKL and OKC layer packages — the metadata notes that it references and is referenced by several standard APIs, including OKL_API, OKC_API, OKC_VERSION_PVT, OKC_P_UTIL, OKC_UTIL, and OKL_DFLEX_UTIL_PVT. These callers include the public lease API surface and the contracts versioning engine, meaning the routines documented above execute during normal lease creation, amendment, copy, and versioning flows driven from the Lease Management forms and related concurrent programs. Because the object is referenced by 65 other packages, any customization or debugging effort touching contract line persistence should treat OKL_KLE_PVT as a foundational internal dependency. Direct invocation by custom code is discouraged; the corresponding public API in the OKL or OKC layer should be used instead to preserve supported upgrade paths across EBS 12.1.1 and 12.2.2.