Search Results validate_indices

Overview

OKL_INDICES_PUB is the public application programming interface for the Oracle Lease and Finance Management (OLFM) indices subsystem within Oracle E-Business Suite Release 12.1.1 and 12.2.2. The package exposes the business logic that governs lease indices and their associated index values, allowing external callers — Oracle Forms, concurrent programs, and custom PL/SQL — to create, maintain, validate, lock, and delete index records without accessing the underlying private package (OKL_INDICES_PVT) directly. The public body follows the standard EBS API architecture: it establishes a SAVEPOINT, delegates to the complex entity API in the private layer, inspects the returned status, and rolls back to the savepoint when the private call reports an error or an unexpected error. Standard FND_API message handling (FND_MSG_PUB.Count_and_get) is used to propagate messages back to the caller. The package is owned by APPS, is classified as a PUB API, and is referenced by three other packages, confirming its role as a shared entry point rather than a terminal consumer.

Key Procedures and Functions

The documented interface comprises twenty-three procedures and functions organized around two primary entities: indices and index values. The principal index-level routines are:

• CREATE_INDICES — creates a new lease index definition. The body source confirms it accepts a standard API version and initialization flag, an idxv_rec_type record, and an ivev_tbl_type table, and returns the same structures in its OUT parameters alongside the standard return status, message count, and message data.
• UPDATE_INDICES — the routine associated with the search term "update_indices". It modifies an existing index definition, applying the validated changes to the index record and its related index values.
• VALIDATE_INDICES — performs validation of index data without persisting changes, allowing callers to detect errors before committing.
• LOCK_INDICES — acquires a pessimistic lock on an index record, typically used in a multi-user editing flow.
• DELETE_INDICES — removes an index definition from the system.

The corresponding index-value-level routines follow the same pattern: CREATE_INDEX_VALUES, UPDATE_INDEX_VALUES, VALIDATE_INDEX_VALUES, LOCK_INDEX_VALUES, and DELETE_INDEX_VALUES. Each is designed to operate on the value rows that belong to a parent index, providing a complete maintenance surface for the indices entity.

Tables Accessed

The documented metadata lists a single table accessed via an APPS synonym: PLITBLM. This is a standard EBS message-handling table used by FND_MSG_PUB, consistent with the Count_and_get calls observed in the source body. The persistent index and index-value tables themselves are not enumerated in the excerpt; their access is performed indirectly through OKL_INDICES_PVT, which encapsulates the actual DML against the OLFM indices schema. Callers interacting through this public package therefore do not need direct object privileges on the underlying index tables.

Usage Notes

OKL_INDICES_PUB is invoked whenever lease index data must be created or maintained through a supported interface. Typical callers include OLFM setup forms and concurrent programs that refresh or adjust index rates, as well as custom extensions that need to update index definitions programmatically. Because the package is a PUB API, custom code should call it rather than the private package, and callers must respect the standard EBS API conventions: supply p_api_version and p_init_msg_list, check x_return_status against FND_API.G_RET_STS_SUCCESS, and inspect x_msg_count and x_msg_data when errors are returned. UPDATE_INDICES in particular should be preceded by LOCK_INDICES in concurrent editing scenarios; the private layer will return an error status that the public body converts into a rollback to savepoint and a G_RET_STS_ERROR result.