Search Results okl_parameters_pub_w




Overview
Explore in AI Chat

Overview

The APPS.OKL_PARAMETERS_PUB_W package is a public API wrapper within the Oracle E-Business Suite (EBS) Enterprise Contracts / Lease Management (OKL) module. It exposes parameter management operations for the OKL domain, allowing callers to create, modify, lock, validate, and remove contract or lease parameter records held in the OKL schema. The object is classified with an API classification of OTHER, indicating it is a supporting public interface rather than a core business document API. In ETRM releases 12.1.1 and 12.2.2, the package is registered as VALID under the APPS schema, which is the standard deployment pattern for EBS public interfaces authenticated through APPS synonyms and grants.

The "_PUB_W" suffix conventionally denotes a PL/SQL public wrapper that mediates between external callers—typically Oracle Forms, concurrent programs, or custom extensions—and the underlying private package logic. This indirection centralizes validation, concurrency control, and error handling, ensuring that direct DML against OKL parameter tables is avoided.

Key Procedures and Functions

The ETRM metadata documents ten procedures or functions associated with this interface. The following five are explicitly named:

  • INSERT_PARAMETERS — Creates new parameter records in the OKL parameter structures, applying standard API validation and defaulting rules prior to persistence.
  • UPDATE_PARAMETERS — Modifies existing parameter records, respecting optimistic locking semantics so that stale data is not overwritten.
  • DELETE_PARAMETERS — Removes parameter records, typically subject to referential and business-rule checks enforced by the package.
  • LOCK_PARAMETERS — Acquires a logical lock on parameter rows to serialize concurrent modification and prevent conflicting updates.
  • VALIDATE_PARAMETERS — Performs pre-write validation of parameter values, returning errors in the standard FND_API message structure.

The remaining documented entries follow the same naming conventions and complete the standard CRUD-plus-validation surface expected of an EBS public API. Because the metadata does not publish parameter lists, callers should consult the package specification in the database or the ETRM technical reference before invocation. No parameter signatures are asserted here.

Tables Accessed

The metadata excerpt does not enumerate specific OKL base tables accessed through APPS synonyms. The dependency listing confirms reliance on FND_API for error-message handling and on the JTF collection types—JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_200, and JTF_VARCHAR2_TABLE_2000. These table types indicate that the procedures accept multi-row (PL/SQL table) input, enabling bulk processing of parameter sets within a single API call. The underlying OKL_PARAMETERS storage object is the presumed target of the insert, update, and delete operations, though its exact name should be verified against the deployed schema.

Usage Notes

Typical invocation occurs from OKL setup and administration forms, from concurrent programs performing bulk parameter maintenance, and from custom PL/SQL extensions that require governed parameter changes. The package is referenced by zero other packages per the documented metadata, meaning it sits at the top of the OKL parameter call stack rather than serving as an internal dependency. Callers are expected to invoke the procedures inside the standard EBS transaction and exception-handling framework, checking the returned API status before committing. Because the package depends on FND_API, error conditions are surfaced through the conventional message stack rather than raw Oracle exceptions.