Search Results update_functions

Overview

OKL_SETUPFUNCTIONS_PUB is the public API package for the Oracle Lease and Finance Management (OLFM/OKL) setup functions framework. It exposes the "data source function" configuration that drives how select setup entities retrieve their values during lease transaction processing. In Oracle EBS 12.1.1 and 12.2.2, this package acts as the public wrapper layer over the private implementation package OKL_SETUPFUNCTIONS_PVT, providing standardized, FND_API-compliant entry points for querying and maintaining setup function definitions stored in the OKL_DATA_SRC_FNCTNS_V view and its underlying base tables. The public/private split isolates calling modules — Forms, concurrent programs, and other OLFM APIs — from the internal data model, ensuring that validation, error handling, and debug logging are applied consistently.

Key Procedures and Functions

The package exposes three documented procedures:

• GET_REC — Single-record query interface for the OKL_DATA_SRC_FNCTNS_V view. The public procedure accepts an incoming record structure, delegates to okl_setupfunctions_pvt.get_rec, and returns the populated record along with the standard FND_API return status, message data, and a no-data-found flag. This is the fetch routine used by Forms when populating a setup functions block.
• INSERT_FUNCTIONS — Insert interface for creating new setup function definitions. It performs the same public-to-private delegation pattern, applying the domain validation, WHO-column population, and error-signalling logic implemented in the private package.
• UPDATE_FUNCTIONS — Update interface for modifying existing setup function definitions. This is the procedure most commonly located by developers searching for "update_functions," since it is the supported entry point for changing data source function attributes through code rather than through the Setup Functions form.

Each procedure follows the OLFM API convention of returning x_return_status and x_msg_data, allowing callers to inspect success, unexpected error, or expected error conditions without raising unhandled exceptions.

Tables Accessed

The metadata does not enumerate physical base tables, but the documented record type dsfv_rec_type is bound to the OKL_DATA_SRC_FNCTNS_V view, whose underlying table stores data source function assignments for lease setup entities. The public body reads this view in GET_REC and writes to the corresponding base table in INSERT_FUNCTIONS and UPDATE_FUNCTIONS via the private package. No additional tables are documented as being referenced directly through APPS synonyms in this public layer, consistent with the delegation model in which DML is concentrated in OKL_SETUPFUNCTIONS_PVT.

Usage Notes

OKL_SETUPFUNCTIONS_PUB is a server-side API, not a form-bound package; it is invoked by the Setup Functions maintenance form, by concurrent setup programs, and by custom or extension code that must create or modify data source functions programmatically. Because it is a PUB-classified API, callers should always use these public procedures rather than calling OKL_SETUPFUNCTIONS_PVT directly, so that return-status handling and debug logging (controlled through OKL_DEBUG_PUB and the LEASE.SETUP.FUNCTIONS module) remain consistent. The metadata records that the package is referenced by one other package, confirming its role as a dependency within the OLFM setup API stack. When invoking UPDATE_FUNCTIONS from custom code, always initialize the record structure, pass the correct primary key, and check x_return_status against FND_API.G_RET_STS_SUCCESS before committing, since the API signals expected business errors through the message stack rather than exceptions.