Search Results okl_indices_pub




Overview

OKL_INDICES_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Lease and Finance Management (OKL) product family and is classified as a PVT (private) API, indicating that it is intended to be called by other packages rather than directly by external integrators. The package encapsulates the business logic for creating, maintaining, validating, and deleting lease indices and their associated index values. Indices in the leasing domain typically represent benchmark rates or reference values, such as interest rate indices, that drive lease rate calculations and periodic revaluation of lease contracts. OKL_INDICES_PVT serves as the core processing layer beneath the public package OKL_INDICES_PUB, which is the documented public entry point exposed to callers. The metadata records 23 procedures and functions in total, with ten principal operations documented. Dependencies include OKC_API, OKL_IDX_PVT, and OKL_IVE_PVT, and the package is referenced by OKL_INDICES_PUB, a second instance of OKL_INDICES_PUB, OKL_INDICES_PVT itself, and the worker package OKL_INDICES_PVT_W.

Key Procedures and Functions

The documented procedures fall into two logical groups: those operating on the index header and those operating on index values.

  • CREATE_INDICES — Inserts a new index definition into the repository.
  • UPDATE_INDICES — Modifies the attributes of an existing index definition.
  • VALIDATE_INDICES — Performs business validation on index data before commit, confirming required attributes and consistency rules.
  • LOCK_INDICES — Acquires a lock on the index record to preserve data integrity during concurrent update processing.
  • DELETE_INDICES — Removes an index definition, subject to the package's internal referential and status checks.
  • CREATE_INDEX_VALUES — Inserts new dated index values belonging to an index.
  • LOCK_INDEX_VALUES — Locks index value rows to protect them during modification.
  • UPDATE_INDEX_VALUES — Updates existing index value records.
  • DELETE_INDEX_VALUES — Deletes index value records that are no longer required.
  • VALIDATE_INDEX_VALUES — Validates index value data, including effective date and value consistency, prior to persistence.

Tables Accessed

According to the documented dependency information, the package references the OKL_INDEX_VALUES table through APPS synonyms, which stores the individual dated values associated with each index definition and is the primary data store manipulated by the value-level procedures. It also references PLITBLM, an Oracle Application Object Library table used in attribute and value-set processing, reflecting the package's participation in the standard EBS validation framework. The OKC_API dependency indicates that the package participates in the Oracle Contracts core API framework for validating and processing contract-related data.

Usage Notes

Because OKL_INDICES_PVT is a private package, it is not intended to be invoked directly from external custom code. Callers should use OKL_INDICES_PUB, which is the documented public interface that wraps the private layer. Typical invocation paths include the Oracle Leasing forms that manage index definitions and index values, concurrent programs that import or refresh index values, and internal lease processing that consumes index data during rate calculation. The presence of the OKL_INDICES_PVT_W worker package indicates that some operations are executed asynchronously through the standard EBS concurrent request mechanism. Customizations that must interact with index data should call OKL_INDICES_PUB and should not depend on the private package, whose signature and internal dependencies may change during patching. The package should always be invoked within a properly initialized EBS session, since it relies on APPS synonyms, FND security context, and the standard OKC_API error handling stack. Developers troubleshooting index-related issues should confirm that OKL_INDICES_PVT and its dependents are compiled VALID, as an invalid state in the private layer will propagate failures to the public API.