Search Results okl_setupfunctions_pub




Overview

The APPS.OKL_SETUPFUNCTIONS_PUB package is a public PL/SQL API within the Oracle E-Business Suite Lease Management (formerly Oracle Lease Management, OKL) module. Its principal responsibility is to maintain the setup function records that drive configurable business logic applied during lease origination, quoting, and contract processing. In Oracle Lease Management, "setup functions" are the user-defined processing rules and validations that the application evaluates based on the specific business scenario configured for a lease. This package provides the programmatic interface through which external callers — typically concurrent programs, forms, or custom extensions — can retrieve, create, and modify those setup function definitions.

The package is classified as a PUBLIC API (PUB), meaning it is intended as a supported entry point for external invocation, as opposed to private (PVT) packages reserved for internal use. Its dependency list confirms that it delegates core business logic to the private worker package OKL_SETUPFUNCTIONS_PVT and to the data-source function package OKL_DSF_PVT, while also leveraging OKC_API, the shared Oracle Contracts API used across the EBS contract family.

Key Procedures and Functions

The package exposes three documented entry points:

  • GET_REC — Retrieves a setup function record, returning the configured definition so callers can inspect existing rule metadata before taking further action.
  • INSERT_FUNCTIONS — Creates new setup function records, persisting the business-rule definitions into the underlying data model.
  • UPDATE_FUNCTIONS — Modifies existing setup function records, allowing administrators or upstream processes to change configuration without recreating the record.

Each of these procedures wraps the corresponding logic in OKL_SETUPFUNCTIONS_PVT; the PUBLIC package therefore acts as a thin, stable interface layer that isolates callers from changes in the private implementation. The parameter lists are not enumerated in the available metadata and should be confirmed against the database package specification for the specific release in use.

Tables Accessed

The ETRM metadata does not document the base tables referenced through APPS synonyms for this package. In practice, the setup-functions API persists data in the OKL setup-function configuration tables managed by OKL_SETUPFUNCTIONS_PVT, and it references contract-side structures through OKC_API for integration with the Oracle Contracts framework. Because the PUBLIC package relies on APPS synonyms, table access is indirectly governed by the private package and by the standard OKL DML handling. Consumers should treat the underlying tables as implementation detail and interact exclusively through the documented API procedures to preserve data integrity and upgrade compatibility.

Usage Notes

OKL_SETUPFUNCTIONS_PUB is typically invoked when setup function configuration must be created or adjusted programmatically, rather than through the Oracle Lease Management administration user interface. Representative invocation contexts include:

  • Concurrent programs that seed or migrate setup function definitions across instances or releases.
  • Oracle Forms or OAF pages in the leasing setup flow that call the API to persist changes.
  • Custom PL/SQL extensions and integration interfaces that need to read or transform setup function configuration.

The dependency metadata shows that the package is referenced by OKL_SETUPFUNCTIONS_PUB_W, a wrapper object, and is self-referencing, indicating recursive or iterator-style invocation patterns documented within the ETRM repository. Because the package is a PUBLIC API, it is the supported interface for these operations, and direct manipulation of the underlying tables is not recommended. Callers should commit explicitly where the API does not manage transaction control, and should validate inputs against the private package's expectations to avoid raising unhandled exceptions from OKL_SETUPFUNCTIONS_PVT.