Search Results delete_fnctn_prmtrs

Overview

OKL_FNCTN_PRMTRS_PUB is the public (PUB-classified) PL/SQL API package for maintaining function parameters within the Oracle E-Business Suite Lease and Finance Management (formerly Oracle Lease Management) module, part of the ETRM (Enterprise Contracts and Trade Management) family of applications. The package exposes a thin public wrapper over the corresponding private implementation package, OKL_FPR_PVT, and serves as the supported entry point for creating, modifying, querying, and removing function parameter records held in the underlying schema. Its design conforms to the standard Oracle EBS API conventions: it declares a version attribute, accepts the OKC_API initialization flag, propagates message counts and message data through OUT parameters, and returns standardized return status codes such as FND_API.G_RET_STS_SUCCESS, FND_API.G_RET_STS_ERROR, and FND_API.G_RET_STS_UNEXP_ERROR.

The header information embedded in the package body indicates a maturation level appropriate to the 12.1.1 and 12.2.2 releases, with the source file OKLPFPRB.pls carrying a noship designation, meaning the file is shipped with the product rather than applied through a patch overlay. The package is referenced by three other packages within the ETRM schema, confirming that function parameter maintenance is a dependency for upstream processing logic.

Key Procedures and Functions

The documented API surface comprises eleven procedures and functions, of which the following are the principal public entry points:

• INSERT_FNCTN_PRMTRS — Creates a new function parameter record. It establishes a savepoint named after the procedure, delegates to OKL_FPR_PVT.INSERT_ROW, and rolls back to the savepoint on error. On completion it reassigns the local record from the private API's output record, returning the persisted values to the caller.
• UPDATE_FNCTN_PRMTRS — Modifies an existing function parameter record. This is the procedure referenced by the search term "update_fnctn_prmtrs" and is the routine most commonly invoked by maintenance forms and corrective scripts.
• DELETE_FNCTN_PRMTRS — Removes a function parameter record, applying the same savepoint and error-handling discipline as the insert and update operations.
• LOCK_FNCTN_PRMTRS — Acquires a row-level lock on a function parameter record so that subsequent updates within the same transaction cannot be overwritten by concurrent sessions.
• VALIDATE_FNCTN_PRMTRS — Performs validation of function parameter data without persisting changes, allowing callers to confirm correctness before committing an insert or update.
• ADD_LANGUAGE — Retained as a stub in the documented body; the internal call to OKL_FPR_PVT.ADD_LANGUAGE is commented out and the procedure returns NULL. It exists for compatibility with the multilingual seed data mechanism used across ETRM packages.

Tables Accessed

The only table referenced directly through APPS synonyms in the documented metadata is PLITBLM, the standard Oracle EBS message-and-language table used by the FND message framework. This reference supports the package's message retrieval and translation behavior, particularly the ADD_LANGUAGE stub and the message-counting calls to FND_MSG_PUB. The persistent function parameter data itself is written and read through the private layer, OKL_FPR_PVT, which owns the actual DML against the underlying OKL function parameter tables. Callers of the public package therefore do not interact with the base tables directly.

Usage Notes

OKL_FNCTN_PRMTRS_PUB is typically invoked from the Oracle Lease Management setup and administration forms, from concurrent programs that seed or migrate function parameter configurations, and from custom extensions that need to maintain parameter values programmatically. Because the package is classified PUB, Oracle supports direct calls to its procedures from customer code; the private OKL_FPR_PVT layer should not be called directly. Callers must supply a valid API version, observe the returned X_RETURN_STATUS before proceeding, inspect X_MSG_COUNT and X_MSG_DATA when errors occur, and manage the surrounding transaction boundary themselves, since the package rolls back only to its internal savepoints. For updates, LOCK_FNCTN_PRMTRS should be called first when concurrent modification is possible.