Search Results okl_setupdsfparameters_pvt




Overview
Explore in AI Chat

Overview

The APPS.OKL_FNCTN_PRMTRS_PUB package is a public API within the Oracle E-Business Suite (EBS) Enterprise Contracts (ETRM/OKL) module. Its purpose is to manage function parameters associated with contract functional setups, such as those configured for the Oracle Lease and Finance Management (OLFM) or related contract authoring and setup flows. The package acts as the public-facing interface for creating, modifying, validating, locking, and removing function parameter records that govern how contract functions behave in a given setup configuration.

The package is classified as a PUB (public) API, meaning it is intended for external invocation by other application code, forms, concurrent programs, or custom extensions, rather than being restricted to internal use. It resides in the APPS schema and is validated as of EBS 12.2.2. Notably, the package is heavily referenced by the OKL_SETUPDSFPARAMETERS_PVT and OKL_SETUPFUNCTIONS_PVT private packages, indicating its central role in the setup/configuration wizard flow for contract function parameters. It is also referenced by the OKL_FNCTN_PRMTRS_PUB_W wrapper package and by itself.

Key Procedures and Functions

The documented API exposes 11 procedures/functions, of which the following core operations are explicitly named:

  • ADD_LANGUAGE — Inserts or maintains language-specific translation rows associated with function parameter definitions, ensuring multi-language (MLS) support for parameter descriptions and names.
  • INSERT_FNCTN_PRMTRS — Creates new function parameter records in the underlying schema, establishing the parameter values or definitions tied to a given contract function setup.
  • LOCK_FNCTN_PRMTRS — Acquires a lock on existing function parameter records, typically to prevent concurrent modification during an update or delete transaction within the same session.
  • UPDATE_FNCTN_PRMTRS — Modifies existing function parameter records, allowing changes to parameter values or attributes after creation.
  • DELETE_FNCTN_PRMTRS — Removes function parameter records from the schema when a function parameter configuration is no longer required.
  • VALIDATE_FNCTN_PRMTRS — Performs business-rule validation against function parameter data before it is committed, ensuring the parameter values conform to defined setup constraints.

Collectively, these procedures provide standard CRUD plus validation and locking behavior for function parameter configuration data. The remaining documented procedures follow similar patterns but are not individually described in the available metadata.

Tables Accessed

The package references the table synonym PLITBLM via APPS. This table is used internally, most likely for storing or resolving foreign-key and lookup information needed during validation or insertion. Because the API manipulates function parameter data, it ultimately works with the base OKL setup tables that store function parameter definitions, though the specific underlying table names are not enumerated in the ETRM metadata beyond PLITBLM. Dependencies on APPS.OKC_API and APPS.OKL_FPR_PVT indicate that the package leverages the OKC (Oracle Contracts Core) public API for contract-related operations and the OKL_FPR_PVT private package for internal function-parameter logic.

Usage Notes

OKL_FNCTN_PRMTRS_PUB is typically invoked from the OLFM setup/administration forms and the contract functions configuration UI, where administrators define and maintain parameters for contract functions. It is also called by the private package OKL_SETUPDSFPARAMETERS_PVT, which manages data source function parameters within the setup wizard, and by OKL_SETUPFUNCTIONS_PVT for function-level setup. Custom concurrent programs or extensions that need to programmatically seed, update, or validate function parameter setups should call this public API rather than manipulating base tables directly, preserving validation and locking semantics. The presence of the OKL_FNCTN_PRMTRS_PUB_W wrapper reinforces that callers may invoke it from multiple contexts, including forms and PL/SQL scripts. Because the API is valid and documented in 12.2.2, it is the supported entry point for function parameter maintenance.