Search Results insert_options

Overview

The APPS.OKL_SETUPOPTIONS_PUB package body is a public API within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. It exposes the setup options that govern global configuration behavior for the leasing application, and it provides the entry point through which other application components and custom code read and maintain the records held in the options view OKL_OPTIONS_V. The package functions as a thin public wrapper over the private implementation package OKL_SETUPOPTIONS_PVT, which contains the substantive business logic. The _PUB layer standardizes the calling convention by enforcing the Oracle Application Object Library (AOL) API framework, including consistent return status codes (FND_API.G_RET_STS_SUCCESS, FND_API.G_RET_STS_UNEXP_ERROR), message handling through FND_MESSAGE, and structured exception propagation. In the 12.1.1 and 12.2.2 releases this package remains classified as a public API (PUB) owned by APPS, meaning it is intended for supported external invocation. Because lease setup options drive downstream processing — such as accounting generation, contract defaults, and streamline behavior — the package occupies an important position in the OKL configuration layer.

Key Procedures and Functions

The documented API surface of this package consists of three procedures:

• GET_REC — Retrieves a setup options record from the options view. It accepts a record of type optv_rec_type, delegates the actual query to okl_setupoptions_pvt.get_rec, and returns the populated record together with a return status, message data, and a x_no_data_found flag. If the private layer signals an unexpected error, the procedure raises FND_API.G_EXC_UNEXPECTED_ERROR.
• INSERT_OPTIONS — Public wrapper for the insert options process API. It carries the standard API envelope parameters (p_api_version, p_init_msg_list, return status, message count, and message data) alongside the options record, providing a supported means of creating setup option records.
• UPDATE_OPTIONS — The procedure most relevant to the search term "update_options." It is the public wrapper for the update options process API, allowing an existing setup options record to be modified. Like the insert wrapper, it operates under the standard AOL API messaging and validation conventions and delegates processing to the private package.

All three procedures follow the consistent _PUB design pattern: parameter normalization, delegation to OKL_SETUPOPTIONS_PVT, and translation of private-layer results into the standard public API contract.

Tables Accessed

The ETRM metadata does not enumerate direct table references through APPS synonyms. Functionally, the package operates against the setup options view OKL_OPTIONS_V, which underlies the optv_rec_type record structure manipulated by all three procedures. Because the public body delegates all data access to okl_setupoptions_pvt, the physical table reads and writes are performed in the private layer; the public package reads and writes setup options through that delegation rather than through direct DML. Consumers should treat OKL_OPTIONS_V as the logical data object being maintained.

Usage Notes

Because the package is classified as a public API and is referenced by one other package, it is intended for invocation from dependent OKL components, custom PL/SQL, and integration code rather than solely from internal private routines. Typical scenarios include reading current leasing configuration during contract creation or accounting derivation (via GET_REC) and programmatically maintaining setup values during implementation or data migration (via INSERT_OPTIONS and UPDATE_OPTIONS). Callers must supply a valid p_api_version, honor the standard message-list parameters, and inspect x_return_status and x_msg_data before proceeding. Direct DML against the underlying options tables should be avoided in favor of these supported entry points to ensure validation and message handling remain intact.